APRS Packet Errors for EA3HVF (last 6 hours)

This table contains packets in which findU has detected an error. This is an automated system, no manual checking of these packets has been done. Most common cause of this is mistakes in entering the latitude/longitude into hard-coded digis, or positions of 0/0. If packets of yours appear here, and you have looked at it carefully and cannot find the error, look again. I've been watching these error messages in my log, and believe my parser is reasonably correct. Go get the APRS spec to be sure. If you have done that, and are CERTAIN the packet is a legal APRS packet, then it is possible that there is an error in my my parser. Only email me if you are absolutely, positively certain...ask yourself, would I bet $100!

time (UTC)Packet
20261019090921EA3HVF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3HVF-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20261019091342EA3HVF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3HVF-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20261019093959EA3HVF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3HVF-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20261019094404EA3HVF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3HVF-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20261019101050EA3HVF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3HVF-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20261019101426EA3HVF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3HVF-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20261019104128EA3HVF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3HVF-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20261019104448EA3HVF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3HVF-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20261019111218EA3HVF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3HVF-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20261019111510EA3HVF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3HVF-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20261019114302EA3HVF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3HVF-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20261019114533EA3HVF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3HVF-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20261019121356EA3HVF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3HVF-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20261019121557EA3HVF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3HVF-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20261019124439EA3HVF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3HVF-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20261019124619EA3HVF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3HVF-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20261019131521EA3HVF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3HVF-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20261019131643EA3HVF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3HVF-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20261019134556EA3HVF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3HVF-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20261019134705EA3HVF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3HVF-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20261019141639EA3HVF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3HVF-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20261019141728EA3HVF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3HVF-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz
20261019144724EA3HVF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3HVF-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 436.0000@-0.0 MHz
20261019144752EA3HVF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3HVF-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000@-0.0 MHz