APRS Packet Errors for SV3ORU (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
20190419182509SV3ORU>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV3ORU-DP!381153.94N/214609.rRNG0034 IPSC2-GR-DMO MMDVM 0.0000 MHz
20190419184200SV3ORU>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV3ORU-DP!381153.94N/214609.rRNG0034 IPSC2-GR-DMO MMDVM 0.0000 MHz
20190419185846SV3ORU>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV3ORU-DP!381153.94N/214609.rRNG0034 IPSC2-GR-DMO MMDVM 0.0000 MHz
20190419191531SV3ORU>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV3ORU-DP!381153.94N/214609.rRNG0034 IPSC2-GR-DMO MMDVM 0.0000 MHz
20190419193216SV3ORU>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV3ORU-DP!381153.94N/214609.rRNG0034 IPSC2-GR-DMO MMDVM 0.0000 MHz
20190419194901SV3ORU>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV3ORU-DP!381153.94N/214609.rRNG0034 IPSC2-GR-DMO MMDVM 0.0000 MHz
20190419200544SV3ORU>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV3ORU-DP!381153.94N/214609.rRNG0034 IPSC2-GR-DMO MMDVM 0.0000 MHz
20190419202230SV3ORU>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV3ORU-DP!381153.94N/214609.rRNG0034 IPSC2-GR-DMO MMDVM 0.0000 MHz
20190419203911SV3ORU>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV3ORU-DP!381153.94N/214609.rRNG0034 IPSC2-GR-DMO MMDVM 0.0000 MHz
20190419205555SV3ORU>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV3ORU-DP!381153.94N/214609.rRNG0034 IPSC2-GR-DMO MMDVM 0.0000 MHz
20190419211241SV3ORU>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV3ORU-DP!381153.94N/214609.rRNG0034 IPSC2-GR-DMO MMDVM 0.0000 MHz
20190419212922SV3ORU>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV3ORU-DP!381153.94N/214609.rRNG0034 IPSC2-GR-DMO MMDVM 0.0000 MHz
20190419214557SV3ORU>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV3ORU-DP!381153.94N/214609.rRNG0034 IPSC2-GR-DMO MMDVM 0.0000 MHz
20190419220239SV3ORU>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV3ORU-DP!381153.94N/214609.rRNG0034 IPSC2-GR-DMO MMDVM 0.0000 MHz
20190419221922SV3ORU>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV3ORU-DP!381153.94N/214609.rRNG0034 IPSC2-GR-DMO MMDVM 0.0000 MHz
20190419223616SV3ORU>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV3ORU-DP!381153.94N/214609.rRNG0034 IPSC2-GR-DMO MMDVM 0.0000 MHz
20190419225301SV3ORU>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV3ORU-DP!381153.94N/214609.rRNG0034 IPSC2-GR-DMO MMDVM 0.0000 MHz
20190419230944SV3ORU>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV3ORU-DP!381153.94N/214609.rRNG0034 IPSC2-GR-DMO MMDVM 0.0000 MHz
20190419232620SV3ORU>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV3ORU-DP!381153.94N/214609.rRNG0034 IPSC2-GR-DMO MMDVM 0.0000 MHz
20190419234300SV3ORU>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV3ORU-DP!381153.94N/214609.rRNG0034 IPSC2-GR-DMO MMDVM 0.0000 MHz
20190419235933SV3ORU>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV3ORU-DP!381153.94N/214609.rRNG0034 IPSC2-GR-DMO MMDVM 0.0000 MHz
20190420001610SV3ORU>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV3ORU-DP!381153.94N/214609.rRNG0034 IPSC2-GR-DMO MMDVM 0.0000 MHz