APRS Packet Errors for SV6AYW (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
20250314184137SV6AYW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV6AYW-DP!39646700.00N/20862rRNG0034 IPSC2-GR-DMO2 MMDVM 434.5750 MHz
20250314184137SV6AYW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV6AYW-DP!4000.00N/021-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 145.5750 MHz
20250314191219SV6AYW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV6AYW-DP!39646700.00N/20862rRNG0034 IPSC2-GR-DMO2 MMDVM 434.5750 MHz
20250314191219SV6AYW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV6AYW-DP!4000.00N/021-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 145.5750 MHz
20250314194301SV6AYW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV6AYW-DP!39646700.00N/20862rRNG0034 IPSC2-GR-DMO2 MMDVM 434.5750 MHz
20250314194301SV6AYW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV6AYW-DP!4000.00N/021-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 145.5750 MHz
20250314201342SV6AYW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV6AYW-DP!39646700.00N/20862rRNG0034 IPSC2-GR-DMO2 MMDVM 434.5750 MHz
20250314201342SV6AYW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV6AYW-DP!4000.00N/021-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 145.5750 MHz
20250314204421SV6AYW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV6AYW-DP!39646700.00N/20862rRNG0034 IPSC2-GR-DMO2 MMDVM 434.5750 MHz
20250314204421SV6AYW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV6AYW-DP!4000.00N/021-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 145.5750 MHz
20250314211501SV6AYW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV6AYW-DP!39646700.00N/20862rRNG0034 IPSC2-GR-DMO2 MMDVM 434.5750 MHz
20250314211502SV6AYW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV6AYW-DP!4000.00N/021-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 145.5750 MHz
20250314214541SV6AYW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV6AYW-DP!39646700.00N/20862rRNG0034 IPSC2-GR-DMO2 MMDVM 434.5750 MHz
20250314214541SV6AYW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV6AYW-DP!4000.00N/021-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 145.5750 MHz
20250314221620SV6AYW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV6AYW-DP!39646700.00N/20862rRNG0034 IPSC2-GR-DMO2 MMDVM 434.5750 MHz
20250314224659SV6AYW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV6AYW-DP!39646700.00N/20862rRNG0034 IPSC2-GR-DMO2 MMDVM 434.5750 MHz
20250314231738SV6AYW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV6AYW-DP!39646700.00N/20862rRNG0034 IPSC2-GR-DMO2 MMDVM 434.5750 MHz
20250314234817SV6AYW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV6AYW-DP!39646700.00N/20862rRNG0034 IPSC2-GR-DMO2 MMDVM 434.5750 MHz
20250315001855SV6AYW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV6AYW-DP!39646700.00N/20862rRNG0034 IPSC2-GR-DMO2 MMDVM 434.5750 MHz