APRS Packet Errors for SV1WE-DP (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
20260208131000SV1WE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV1WE-DP!4144.00N/05023.99WrRNG0034 IPSC2-GR-DMO2 MMDVM 222.3400 MHz
20260208134041SV1WE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV1WE-DP!4144.00N/05023.99WrRNG0034 IPSC2-GR-DMO2 MMDVM 222.3400 MHz
20260208141136SV1WE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV1WE-DP!4144.00N/05023.99WrRNG0034 IPSC2-GR-DMO2 MMDVM 222.3400 MHz
20260208144240SV1WE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV1WE-DP!4144.00N/05023.99WrRNG0034 IPSC2-GR-DMO2 MMDVM 222.3400 MHz
20260208151333SV1WE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV1WE-DP!4144.00N/05023.99WrRNG0034 IPSC2-GR-DMO2 MMDVM 222.3400 MHz
20260208154426SV1WE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV1WE-DP!4144.00N/05023.99WrRNG0034 IPSC2-GR-DMO2 MMDVM 222.3400 MHz
20260208161520SV1WE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV1WE-DP!4144.00N/05023.99WrRNG0034 IPSC2-GR-DMO2 MMDVM 222.3400 MHz
20260208164627SV1WE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV1WE-DP!4144.00N/05023.99WrRNG0034 IPSC2-GR-DMO2 MMDVM 222.3400 MHz
20260208181921SV1WE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV1WE-DP!3801.26N/02342.48ErRNG0034 IPSC2-GR-DMO2 MMDVM 431.1500 MHz
20260208185020SV1WE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV1WE-DP!3801.26N/02342.48ErRNG0034 IPSC2-GR-DMO2 MMDVM 431.1500 MHz