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
20190717172350SV3BEO>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV3BEO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 433.0125 MHz
20190717174040SV3BEO>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV3BEO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 433.0125 MHz
20190717175728SV3BEO>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV3BEO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 433.0125 MHz
20190717181433SV3BEO>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV3BEO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 433.0125 MHz
20190717183135SV3BEO>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV3BEO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 433.0125 MHz
20190717184830SV3BEO>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV3BEO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 433.0125 MHz
20190717190524SV3BEO>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV3BEO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 433.0125 MHz
20190717192213SV3BEO>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV3BEO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 433.0125 MHz
20190717193919SV3BEO>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV3BEO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 433.0125 MHz
20190717195622SV3BEO>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV3BEO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 433.0125 MHz
20190717201312SV3BEO>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV3BEO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 433.0125 MHz
20190717203003SV3BEO>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV3BEO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 433.0125 MHz
20190717204659SV3BEO>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV3BEO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 433.0125 MHz
20190717210349SV3BEO>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV3BEO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 433.0125 MHz
20190717212042SV3BEO>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV3BEO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 433.0125 MHz
20190717213732SV3BEO>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV3BEO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 433.0125 MHz
20190717215429SV3BEO>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV3BEO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 433.0125 MHz
20190717221118SV3BEO>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV3BEO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 433.0125 MHz
20190717222808SV3BEO>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV3BEO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 433.0125 MHz
20190717224458SV3BEO>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV3BEO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 433.0125 MHz
20190717230156SV3BEO>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV3BEO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 433.0125 MHz