APRS Packet Errors for G3JPJ (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
20240518131304G3JPJ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G3JPJ-DP!5140.17N/000-16.74rRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20240518134652G3JPJ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G3JPJ-DP!5140.17N/000-16.74rRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20240518142039G3JPJ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G3JPJ-DP!5140.17N/000-16.74rRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20240518145425G3JPJ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G3JPJ-DP!5140.17N/000-16.74rRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20240518152814G3JPJ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G3JPJ-DP!5140.17N/000-16.74rRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20240518160159G3JPJ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G3JPJ-DP!5140.17N/000-16.74rRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20240518163540G3JPJ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G3JPJ-DP!5140.17N/000-16.74rRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20240518170926G3JPJ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G3JPJ-DP!5140.17N/000-16.74rRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20240518174316G3JPJ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G3JPJ-DP!5140.17N/000-16.74rRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20240518181714G3JPJ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G3JPJ-DP!5140.17N/000-16.74rRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz