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
20190824060505SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190824062154SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190824063843SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190824065530SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190824071215SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190824072917SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190824074604SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190824080252SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190824081941SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190824083634SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190824085320SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190824094348SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190824100035SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190824101726SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190824103429SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190824105131SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190824110822SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190824112512SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190824114202SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz