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
20190620135714SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190620141358SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190620143043SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190620144721SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190620150359SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190620152036SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190620153717SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190620155357SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190620161035SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190620162714SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190620164354SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190620170032SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190620171709SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190620173348SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190620175030SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190620180708SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190620182348SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190620184029SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190620185715SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190620191352SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190620193029SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz