APRS Packet Errors for EA1TZ (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
20250915141817EA1TZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1TZ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-EA-Hotspot MMDVM 432.0000 MHz
20250915151920EA1TZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1TZ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-EA-Hotspot MMDVM 432.0000 MHz
20250915154950EA1TZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1TZ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-EA-Hotspot MMDVM 432.0000 MHz
20250915162021EA1TZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1TZ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-EA-Hotspot MMDVM 432.0000 MHz
20250915165052EA1TZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1TZ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-EA-Hotspot MMDVM 432.0000 MHz
20250915172122EA1TZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1TZ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-EA-Hotspot MMDVM 432.0000 MHz
20250915175153EA1TZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1TZ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-EA-Hotspot MMDVM 432.0000 MHz
20250915182224EA1TZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1TZ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-EA-Hotspot MMDVM 432.0000 MHz
20250915185253EA1TZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1TZ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-EA-Hotspot MMDVM 432.0000 MHz
20250915192323EA1TZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1TZ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-EA-Hotspot MMDVM 432.0000 MHz