APRS Packet Errors for DL3HRM (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
20260420063557	DL3HRM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DL3HRM-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DL-HOTSPOT MMDVM 144.8500 MHz
20260420070701	DL3HRM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DL3HRM-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DL-HOTSPOT MMDVM 144.8500 MHz
20260420073803	DL3HRM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DL3HRM-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DL-HOTSPOT MMDVM 144.8500 MHz
20260420080916	DL3HRM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DL3HRM-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DL-HOTSPOT MMDVM 144.8500 MHz
20260420084022	DL3HRM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DL3HRM-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DL-HOTSPOT MMDVM 144.8500 MHz
20260420091117	DL3HRM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DL3HRM-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DL-HOTSPOT MMDVM 144.8500 MHz
20260420094213	DL3HRM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DL3HRM-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DL-HOTSPOT MMDVM 144.8500 MHz