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
20250718182918G3JPJ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G3JPJ-DP!5141.25N/000-17.52rRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20250718193248G3JPJ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G3JPJ-DP!5141.25N/000-17.52rRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20250718200431G3JPJ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G3JPJ-DP!5141.25N/000-17.52rRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20250718203613G3JPJ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G3JPJ-DP!5141.25N/000-17.52rRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20250718210829G3JPJ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G3JPJ-DP!5141.25N/000-17.52rRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20250718214041G3JPJ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G3JPJ-DP!5141.25N/000-17.52rRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20250718221218G3JPJ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G3JPJ-DP!5141.25N/000-17.52rRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20250718224409G3JPJ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G3JPJ-DP!5141.25N/000-17.52rRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20250718231600G3JPJ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G3JPJ-DP!5141.25N/000-17.52rRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20250718234806G3JPJ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G3JPJ-DP!5141.25N/000-17.52rRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz