APRS Packet Errors for SV9MBH (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
20190916153159SV9MBH>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9MBH-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.1000 MHz
20190916154708SV9MBH>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9MBH-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.1000 MHz
20190916160216SV9MBH>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9MBH-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.1000 MHz
20190916161729SV9MBH>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9MBH-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.1000 MHz
20190916163238SV9MBH>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9MBH-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.1000 MHz
20190916164747SV9MBH>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9MBH-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.1000 MHz
20190916170257SV9MBH>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9MBH-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.1000 MHz
20190916171815SV9MBH>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9MBH-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.1000 MHz
20190916173328SV9MBH>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9MBH-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.1000 MHz
20190916174841SV9MBH>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9MBH-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.1000 MHz
20190916180351SV9MBH>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9MBH-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.1000 MHz
20190916181904SV9MBH>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9MBH-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.1000 MHz
20190916183413SV9MBH>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9MBH-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.1000 MHz
20190916184923SV9MBH>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9MBH-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.1000 MHz
20190916190431SV9MBH>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9MBH-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.1000 MHz
20190916191945SV9MBH>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9MBH-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.1000 MHz
20190916193456SV9MBH>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9MBH-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.1000 MHz
20190916195005SV9MBH>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9MBH-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.1000 MHz
20190916200513SV9MBH>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9MBH-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.1000 MHz
20190916202025SV9MBH>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9MBH-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.1000 MHz
20190916203534SV9MBH>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9MBH-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.1000 MHz
20190916205044SV9MBH>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9MBH-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.1000 MHz
20190916210553SV9MBH>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9MBH-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.1000 MHz
20190916212108SV9MBH>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV9MBH-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.1000 MHz