APRS Packet Errors for BG5HGP-9 (last 24 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
20190114232703BG5HGP-9>APLM2C,TCPIP*,qAS,BG5HGP-9:=0000.00N/00000.00E>000/000/A=000000APRSBox 00X_22S_3.95V
20190114233231BG5HGP-9>APLM2C,TCPIP*,qAS,BG5HGP-9:=0000.00N/00000.00E>000/000/A=000000APRSBox 00X_22S_3.95V
20190115064625BG5HGP-9>APLM2C,TCPIP*,qAS,BG5HGP-9:=0000.00N/00000.00E>000/000/A=000000APRSBox 00X_21S_3.95V
20190115111238BG5HGP-9>APLM2C,TCPIP*,qAS,BG5HGP-9:=0000.00N/00000.00E>000/000/A=000000APRSBox 00X_17S_3.95V
20190115123556BG5HGP-9>APLM2C,TCPIP*,qAS,BG5HGP-9:=0000.00N/00000.00E>000/000/A=000000APRSBox 00X_22S_3.95V
20190115124357BG5HGP-9>APLM2C,TCPIP*,qAS,BG5HGP-9:=0000.00N/00000.00E>000/000/A=000000APRSBox 00X_30S_3.95V
20190115144008BG5HGP-9>APLM2C,TCPIP*,qAS,BG5HGP-9:=0000.00N/00000.00E>000/000/A=000000APRSBox 00X_19S_3.95V