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
20190425044530SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190425050210SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190425051848SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190425053532SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190425055212SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190425060855SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190425062536SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190425064225SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190425065911SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190425071553SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190425073233SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190425074920SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190425080602SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190425082244SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190425083925SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190425085612SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190425091253SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190425092933SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190425094615SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190425100301SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190425101943SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz