APRS Packet Errors for EA5ERA (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
20250916130956	EA5ERA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5ERA-DP!99900.00N/99900.00rRNG0034 IPSC2-EA-Hotspot MMDVM 433.6000 MHz
20250916134027	EA5ERA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5ERA-DP!99900.00N/99900.00rRNG0034 IPSC2-EA-Hotspot MMDVM 433.6000 MHz
20250916141100	EA5ERA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5ERA-DP!99900.00N/99900.00rRNG0034 IPSC2-EA-Hotspot MMDVM 433.6000 MHz
20250916144129	EA5ERA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5ERA-DP!99900.00N/99900.00rRNG0034 IPSC2-EA-Hotspot MMDVM 433.6000 MHz
20250916151200	EA5ERA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5ERA-DP!99900.00N/99900.00rRNG0034 IPSC2-EA-Hotspot MMDVM 433.6000 MHz
20250916154230	EA5ERA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5ERA-DP!99900.00N/99900.00rRNG0034 IPSC2-EA-Hotspot MMDVM 433.6000 MHz
20250916161301	EA5ERA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5ERA-DP!99900.00N/99900.00rRNG0034 IPSC2-EA-Hotspot MMDVM 433.6000 MHz
20250916164333	EA5ERA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5ERA-DP!99900.00N/99900.00rRNG0034 IPSC2-EA-Hotspot MMDVM 433.6000 MHz
20250916181511	EA5ERA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5ERA-DP!99900.00N/99900.00rRNG0034 IPSC2-EA-Hotspot MMDVM 433.6000 MHz