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
20190720180251SV4LAD>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4LAD-DP!4144.00N/-50-23.99rRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190720181952SV4LAD>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4LAD-DP!4144.00N/-50-23.99rRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190720183645SV4LAD>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4LAD-DP!4144.00N/-50-23.99rRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190720185330SV4LAD>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4LAD-DP!4144.00N/-50-23.99rRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190720191033SV4LAD>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4LAD-DP!4144.00N/-50-23.99rRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190720192732SV4LAD>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4LAD-DP!4144.00N/-50-23.99rRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190720194419SV4LAD>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4LAD-DP!4144.00N/-50-23.99rRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190720200106SV4LAD>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4LAD-DP!4144.00N/-50-23.99rRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190720201755SV4LAD>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4LAD-DP!4144.00N/-50-23.99rRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190720203446SV4LAD>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4LAD-DP!4144.00N/-50-23.99rRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190720205133SV4LAD>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4LAD-DP!4144.00N/-50-23.99rRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190720210820SV4LAD>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4LAD-DP!4144.00N/-50-23.99rRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190720212509SV4LAD>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4LAD-DP!4144.00N/-50-23.99rRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190720214200SV4LAD>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4LAD-DP!4144.00N/-50-23.99rRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190720215847SV4LAD>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4LAD-DP!4144.00N/-50-23.99rRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190720221534SV4LAD>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4LAD-DP!4144.00N/-50-23.99rRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190720223220SV4LAD>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4LAD-DP!4144.00N/-50-23.99rRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190720224911SV4LAD>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4LAD-DP!4144.00N/-50-23.99rRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190720232152SV4LAD>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4LAD-DP!4144.00N/-50-23.99rRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190720233838SV4LAD>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4LAD-DP!4144.00N/-50-23.99rRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz
20190720235526SV4LAD>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV4LAD-DP!4144.00N/-50-23.99rRNG0034 IPSC2-GR-DMO MMDVM 434.1000 MHz