APRS Packet Errors for KA9SXP (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
20190120155024KA9SXP>APBM1S,TCPIP*,qAS,N3FE-15:@201550z383119.80N/895807.79E-MMDVM MMDVM HS 433.4500/433.4500 CC1
20190120162149KA9SXP>APBM1S,TCPIP*,qAS,N3FE-15:@201621z383119.80N/895807.79E-MMDVM MMDVM HS 433.4500/433.4500 CC1
20190120165117KA9SXP>APBM1S,TCPIP*,qAS,N3FE-15:@201651z383119.80N/895807.79E-MMDVM MMDVM HS 433.4500/433.4500 CC1
20190120175343KA9SXP>APBM1S,TCPIP*,qAS,N3FE-15:@201753z383119.80N/895807.79E-MMDVM MMDVM HS 433.4500/433.4500 CC1
20190120182311KA9SXP>APBM1S,TCPIP*,qAS,N3FE-15:@201823z383119.80N/895807.79E-MMDVM MMDVM HS 433.4500/433.4500 CC1
20190120185355KA9SXP>APBM1S,TCPIP*,qAS,N3FE-15:@201853z383119.80N/895807.79E-MMDVM MMDVM HS 433.4500/433.4500 CC1
20190120192352KA9SXP>APBM1S,TCPIP*,qAS,N3FE-15:@201923z383119.80N/895807.79E-MMDVM MMDVM HS 433.4500/433.4500 CC1
20190120195446KA9SXP>APBM1S,TCPIP*,qAS,N3FE-15:@201954z383119.80N/895807.79E-MMDVM MMDVM HS 433.4500/433.4500 CC1
20190120202509KA9SXP>APBM1S,TCPIP*,qAS,N3FE-15:@202025z383119.80N/895807.79E-MMDVM MMDVM HS 433.4500/433.4500 CC1
20190120205428KA9SXP>APBM1S,TCPIP*,qAS,N3FE-15:@202054z383119.80N/895807.79E-MMDVM MMDVM HS 433.4500/433.4500 CC1