APRS Packet Errors for PI1SNK (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
20190418053222PI1SNK>APBPQ1,TCPIP*,qAC,PD2RLD-JS:;PI8SNK BBS 144.850 !5301.59N/00538.84EB
20190418055722PI1SNK>APBPQ1,TCPIP*,qAC,PD2RLD-JS:;PI8SNK BBS 144.850 !5301.59N/00538.84EB
20190418062223PI1SNK>APBPQ1,TCPIP*,qAC,PD2RLD-JS:;PI8SNK BBS 144.850 !5301.59N/00538.84EB
20190418064724PI1SNK>APBPQ1,TCPIP*,qAC,PD2RLD-JS:;PI8SNK BBS 144.850 !5301.59N/00538.84EB
20190418071225PI1SNK>APBPQ1,TCPIP*,qAC,PD2RLD-JS:;PI8SNK BBS 144.850 !5301.59N/00538.84EB
20190418073726PI1SNK>APBPQ1,TCPIP*,qAC,PD2RLD-JS:;PI8SNK BBS 144.850 !5301.59N/00538.84EB
20190418080227PI1SNK>APBPQ1,TCPIP*,qAC,PD2RLD-JS:;PI8SNK BBS 144.850 !5301.59N/00538.84EB
20190418082727PI1SNK>APBPQ1,TCPIP*,qAC,PD2RLD-JS:;PI8SNK BBS 144.850 !5301.59N/00538.84EB
20190418085229PI1SNK>APBPQ1,TCPIP*,qAC,PD2RLD-JS:;PI8SNK BBS 144.850 !5301.59N/00538.84EB
20190418091729PI1SNK>APBPQ1,TCPIP*,qAC,PD2RLD-JS:;PI8SNK BBS 144.850 !5301.59N/00538.84EB
20190418094230PI1SNK>APBPQ1,TCPIP*,qAC,PD2RLD-JS:;PI8SNK BBS 144.850 !5301.59N/00538.84EB
20190418100731PI1SNK>APBPQ1,TCPIP*,qAC,PD2RLD-JS:;PI8SNK BBS 144.850 !5301.59N/00538.84EB
20190418103232PI1SNK>APBPQ1,TCPIP*,qAC,PD2RLD-JS:;PI8SNK BBS 144.850 !5301.59N/00538.84EB
20190418105734PI1SNK>APBPQ1,TCPIP*,qAC,PD2RLD-JS:;PI8SNK BBS 144.850 !5301.59N/00538.84EB