APRS Packet Errors for EA5KV (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
20251018014738EA5KV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5KV-DP!3832.38N/000-30.33rRNG0034 IPSC2-EA-Hotspot MMDVM 434.1000 MHz
20251018021806EA5KV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5KV-DP!3832.38N/000-30.33rRNG0034 IPSC2-EA-Hotspot MMDVM 434.1000 MHz
20251018024834EA5KV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5KV-DP!3832.38N/000-30.33rRNG0034 IPSC2-EA-Hotspot MMDVM 434.1000 MHz
20251018031900EA5KV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5KV-DP!3832.38N/000-30.33rRNG0034 IPSC2-EA-Hotspot MMDVM 434.1000 MHz
20251018034927EA5KV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5KV-DP!3832.38N/000-30.33rRNG0034 IPSC2-EA-Hotspot MMDVM 434.1000 MHz
20251018052047EA5KV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5KV-DP!3832.38N/000-30.33rRNG0034 IPSC2-EA-Hotspot MMDVM 434.1000 MHz
20251018055113EA5KV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5KV-DP!3832.38N/000-30.33rRNG0034 IPSC2-EA-Hotspot MMDVM 434.1000 MHz
20251018062139EA5KV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5KV-DP!3832.38N/000-30.33rRNG0034 IPSC2-EA-Hotspot MMDVM 434.1000 MHz
20251018065206EA5KV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5KV-DP!3832.38N/000-30.33rRNG0034 IPSC2-EA-Hotspot MMDVM 434.1000 MHz
20251018072234EA5KV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5KV-DP!3832.38N/000-30.33rRNG0034 IPSC2-EA-Hotspot MMDVM 434.1000 MHz