APRS Packet Errors for SV4NLT (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
20190420124724SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190420130403SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190420132055SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190420133738SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190420135417SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190420141140SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190420142822SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190420144506SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190420150201SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190420151851SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190420153536SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190420155225SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190420160903SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190420162550SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190420164227SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190420165907SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190420171540SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190420173218SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190420174851SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190420180526SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190420182206SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190420183847SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz