APRS Packet Errors for GM3DRA (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
20260326015408	GM3DRA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)GM3DRA-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20260326022624	GM3DRA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)GM3DRA-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20260326025840	GM3DRA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)GM3DRA-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20260326033057	GM3DRA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)GM3DRA-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20260326040312	GM3DRA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)GM3DRA-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20260326050739	GM3DRA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)GM3DRA-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20260326053951	GM3DRA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)GM3DRA-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20260326061205	GM3DRA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)GM3DRA-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20260326064423	GM3DRA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)GM3DRA-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20260326071643	GM3DRA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)GM3DRA-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz