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
20191205123229SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20191205124743SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20191205130258SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20191205131811SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20191205133322SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20191205134833SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20191205140349SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20191205141901SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20191205143415SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20191205144927SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20191205150441SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20191205151955SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20191205153507SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20191205155024SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20191205160540SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20191205162050SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20191205163602SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20191205165114SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20191205170629SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20191205172143SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20191205173656SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20191205175209SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20191205180724SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz