APRS Packet Errors for EA4DGY (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
20261024022157	EA4DGY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4DGY-DP!99900.00N/99900.00rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8500 MHz
20261024025216	EA4DGY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4DGY-DP!99900.00N/99900.00rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8500 MHz
20261024032236	EA4DGY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4DGY-DP!99900.00N/99900.00rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8500 MHz
20261024035255	EA4DGY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4DGY-DP!99900.00N/99900.00rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8500 MHz
20261024042314	EA4DGY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4DGY-DP!99900.00N/99900.00rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8500 MHz
20261024045334	EA4DGY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4DGY-DP!99900.00N/99900.00rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8500 MHz
20261024052354	EA4DGY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4DGY-DP!99900.00N/99900.00rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8500 MHz
20261024055413	EA4DGY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4DGY-DP!99900.00N/99900.00rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8500 MHz