APRS Packet Errors for SV3BEO (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
20190720181952SV3BEO>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV3BEO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 433.0125 MHz
20190720183645SV3BEO>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV3BEO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 433.0125 MHz
20190720185330SV3BEO>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV3BEO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 433.0125 MHz
20190720191033SV3BEO>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV3BEO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 433.0125 MHz
20190720192732SV3BEO>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV3BEO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 433.0125 MHz
20190720194419SV3BEO>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV3BEO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 433.0125 MHz
20190720200106SV3BEO>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV3BEO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 433.0125 MHz
20190720201755SV3BEO>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV3BEO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 433.0125 MHz
20190720203446SV3BEO>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV3BEO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 433.0125 MHz
20190720205133SV3BEO>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV3BEO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 433.0125 MHz
20190720210820SV3BEO>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV3BEO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 433.0125 MHz
20190720212509SV3BEO>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV3BEO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 433.0125 MHz
20190720214200SV3BEO>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV3BEO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 433.0125 MHz
20190720215847SV3BEO>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV3BEO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 433.0125 MHz
20190720221534SV3BEO>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV3BEO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 433.0125 MHz
20190720223220SV3BEO>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV3BEO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 433.0125 MHz
20190720224911SV3BEO>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV3BEO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 433.0125 MHz
20190720232152SV3BEO>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV3BEO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 433.0125 MHz
20190720233838SV3BEO>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV3BEO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 433.0125 MHz
20190720235526SV3BEO>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV3BEO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 433.0125 MHz