APRS Packet Errors for SV1GGB (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
20250708041142	SV1GGB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV1GGB-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 431.0250 MHz
20250708051429	SV1GGB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV1GGB-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 431.0250 MHz
20250708054513	SV1GGB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV1GGB-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 431.0250 MHz
20250708061615	SV1GGB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV1GGB-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 431.0250 MHz
20250708064735	SV1GGB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV1GGB-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 431.0250 MHz
20250708071821	SV1GGB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV1GGB-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 431.0250 MHz
20250708074922	SV1GGB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV1GGB-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 431.0250 MHz
20250708082022	SV1GGB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV1GGB-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 431.0250 MHz