APRS Packet Errors for SV4LAD (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
20190720073911SV4LAD>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4LAD-DP!4144.00N/-50-23.99rRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190720080524SV4LAD>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4LAD-DP!4144.00N/-50-23.99rRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190720082213SV4LAD>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4LAD-DP!4144.00N/-50-23.99rRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190720083900SV4LAD>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4LAD-DP!4144.00N/-50-23.99rRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190720085545SV4LAD>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4LAD-DP!4144.00N/-50-23.99rRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190720091235SV4LAD>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4LAD-DP!4144.00N/-50-23.99rRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190720092923SV4LAD>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4LAD-DP!4144.00N/-50-23.99rRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190720100950SV4LAD>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4LAD-DP!4144.00N/-50-23.99rRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190720102639SV4LAD>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4LAD-DP!4144.00N/-50-23.99rRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190720104327SV4LAD>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4LAD-DP!4144.00N/-50-23.99rRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190720110014SV4LAD>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4LAD-DP!4144.00N/-50-23.99rRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190720111703SV4LAD>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4LAD-DP!4144.00N/-50-23.99rRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190720115842SV4LAD>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4LAD-DP!4144.00N/-50-23.99rRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190720121603SV4LAD>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4LAD-DP!4144.00N/-50-23.99rRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190720123250SV4LAD>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4LAD-DP!4144.00N/-50-23.99rRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190720124940SV4LAD>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4LAD-DP!4144.00N/-50-23.99rRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190720130858SV4LAD>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4LAD-DP!4144.00N/-50-23.99rRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz