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
20190821061542SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20190821063225SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20190821064916SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20190821070559SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20190821072246SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20190821073928SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20190821075611SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20190821081254SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20190821082941SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20190821084629SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20190821090317SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20190821092001SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20190821093647SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20190821095331SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20190821101014SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20190821102659SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20190821104353SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20190821110037SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20190821111725SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20190821113412SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz
20190821115110SV1HBS>APZDMR,QTH,TCPIP*,qAU,APRSLK-I2:)SV1HBS-DP!5000.00N/-0300.00ErRNG0034 IPSC2-GR-DMO MMDVM 438.0550 MHz