APRS Packet Errors for SV6J (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
20260611022724SV6J>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV6J-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-RPT MMDVM 438.7000@-7.6 MHz
20260611025823SV6J>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV6J-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-RPT MMDVM 438.7000@-7.6 MHz
20260611032923SV6J>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV6J-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-RPT MMDVM 438.7000@-7.6 MHz
20260611040021SV6J>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV6J-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-RPT MMDVM 438.7000@-7.6 MHz
20260611043120SV6J>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV6J-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-RPT MMDVM 438.7000@-7.6 MHz
20260611050223SV6J>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV6J-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-RPT MMDVM 438.7000@-7.6 MHz
20260611053347SV6J>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV6J-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-RPT MMDVM 438.7000@-7.6 MHz
20260611060446SV6J>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV6J-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-RPT MMDVM 438.7000@-7.6 MHz
20260611070650SV6J>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV6J-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-RPT MMDVM 438.7000@-7.6 MHz
20260611080848SV6J>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV6J-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-RPT MMDVM 438.7000@-7.6 MHz