APRS Packet Errors for SV2JOL (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
20250707045349SV2JOL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV2JOL-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 438.8000@-7.4 MHz
20250707052431SV2JOL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV2JOL-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 438.8000@-7.4 MHz
20250707075942SV2JOL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV2JOL-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 438.8000@-7.4 MHz
20250707083040SV2JOL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV2JOL-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 438.8000@-7.4 MHz
20250707090139SV2JOL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV2JOL-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 438.8000@-7.4 MHz
20250707093236SV2JOL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV2JOL-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 438.8000@-7.4 MHz
20250707100336SV2JOL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV2JOL-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 438.8000@-7.4 MHz
20250707103435SV2JOL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV2JOL-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 438.8000@-7.4 MHz