APRS Packet Errors for EAXXXX (last 168 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
20261030182520EAXXXX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EAXXXX-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 438.1750 MHz
20261030185547EAXXXX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EAXXXX-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 438.1750 MHz
20261030192616EAXXXX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EAXXXX-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 438.1750 MHz
20261030195644EAXXXX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EAXXXX-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 438.1750 MHz
20261030202712EAXXXX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EAXXXX-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 438.1750 MHz
20261030205737EAXXXX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EAXXXX-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 438.1750 MHz
20261030212804EAXXXX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EAXXXX-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 438.1750 MHz
20261030215831EAXXXX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EAXXXX-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 438.1750 MHz
20261030222858EAXXXX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EAXXXX-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 438.1750 MHz