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
20190923150434SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190923151948SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190923153458SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190923155011SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190923160523SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190923162040SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190923163553SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190923165102SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190923170612SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190923172126SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190923173638SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190923175149SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190923180659SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190923182216SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190923183727SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190923185237SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190923190747SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190923192304SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190923193813SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190923195322SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190923200831SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190923202346SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190923203854SV4NLT>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4NLT-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz