APRS Packet Errors for N4ATY (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
20250807002612N4ATY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)N4ATY-DP!5000.00N/003-0.00WrRNG0034 IPSC2-EA-Hotspot MMDVM 438.8000 MHz
20250807005636N4ATY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)N4ATY-DP!5000.00N/003-0.00WrRNG0034 IPSC2-EA-Hotspot MMDVM 438.8000 MHz
20250807012658N4ATY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)N4ATY-DP!5000.00N/003-0.00WrRNG0034 IPSC2-EA-Hotspot MMDVM 438.8000 MHz
20250807015721N4ATY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)N4ATY-DP!5000.00N/003-0.00WrRNG0034 IPSC2-EA-Hotspot MMDVM 438.8000 MHz
20250807022743N4ATY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)N4ATY-DP!5000.00N/003-0.00WrRNG0034 IPSC2-EA-Hotspot MMDVM 438.8000 MHz
20250807025805N4ATY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)N4ATY-DP!5000.00N/003-0.00WrRNG0034 IPSC2-EA-Hotspot MMDVM 438.8000 MHz
20250807032826N4ATY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)N4ATY-DP!5000.00N/003-0.00WrRNG0034 IPSC2-EA-Hotspot MMDVM 438.8000 MHz
20250807035848N4ATY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)N4ATY-DP!5000.00N/003-0.00WrRNG0034 IPSC2-EA-Hotspot MMDVM 438.8000 MHz
20250807042909N4ATY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)N4ATY-DP!5000.00N/003-0.00WrRNG0034 IPSC2-EA-Hotspot MMDVM 438.8000 MHz