APRS Packet Errors for SV1HBS (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
20191117091521SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20191117093032SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20191117094542SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20191117100054SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20191117101610SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20191117103121SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20191117104634SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20191117110145SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20191117111700SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20191117113210SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20191117114723SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20191117120234SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20191117121749SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20191117123301SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20191117124812SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20191117130323SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20191117132604SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20191117134115SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20191117135628SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20191117141142SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20191117142659SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20191117144211SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20191117145723SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz