APRS Packet Errors for SV8HEH (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
20250701050506SV8HEH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV8HEH-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 434.2000 MHz
20250701053637SV8HEH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV8HEH-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 434.2000 MHz
20250701060809SV8HEH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV8HEH-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 434.2000 MHz
20250701063905SV8HEH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV8HEH-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 434.2000 MHz
20250701071019SV8HEH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV8HEH-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 434.2000 MHz
20250701074151SV8HEH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV8HEH-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 434.2000 MHz
20250701081249SV8HEH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV8HEH-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 434.2000 MHz
20250701084438SV8HEH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV8HEH-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 434.2000 MHz
20250701091519SV8HEH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV8HEH-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 434.2000 MHz
20250701094632SV8HEH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV8HEH-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 434.2000 MHz