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
20181210081810PI1SNK>APBPQ1,TCPIP*,qAC,PD2RLD-JS:;PI8SNK BBS 144.850 !5301.59N/00538.84EB
20181210084520PI1SNK>APBPQ1,TCPIP*,qAC,PD2RLD-JS:;PI8SNK BBS 144.850 !5301.59N/00538.84EB
20181210091227PI1SNK>APBPQ1,TCPIP*,qAC,PD2RLD-JS:;PI8SNK BBS 144.850 !5301.59N/00538.84EB
20181210093933PI1SNK>APBPQ1,TCPIP*,qAC,PD2RLD-JS:;PI8SNK BBS 144.850 !5301.59N/00538.84EB
20181210100640PI1SNK>APBPQ1,TCPIP*,qAC,PD2RLD-JS:;PI8SNK BBS 144.850 !5301.59N/00538.84EB
20181210103347PI1SNK>APBPQ1,TCPIP*,qAC,PD2RLD-JS:;PI8SNK BBS 144.850 !5301.59N/00538.84EB
20181210110052PI1SNK>APBPQ1,TCPIP*,qAC,PD2RLD-JS:;PI8SNK BBS 144.850 !5301.59N/00538.84EB
20181210112758PI1SNK>APBPQ1,TCPIP*,qAC,PD2RLD-JS:;PI8SNK BBS 144.850 !5301.59N/00538.84EB
20181210115507PI1SNK>APBPQ1,TCPIP*,qAC,PD2RLD-JS:;PI8SNK BBS 144.850 !5301.59N/00538.84EB
20181210122213PI1SNK>APBPQ1,TCPIP*,qAC,PD2RLD-JS:;PI8SNK BBS 144.850 !5301.59N/00538.84EB
20181210124921PI1SNK>APBPQ1,TCPIP*,qAC,PD2RLD-JS:;PI8SNK BBS 144.850 !5301.59N/00538.84EB
20181210131627PI1SNK>APBPQ1,TCPIP*,qAC,PD2RLD-JS:;PI8SNK BBS 144.850 !5301.59N/00538.84EB
20181210134336PI1SNK>APBPQ1,TCPIP*,qAC,PD2RLD-JS:;PI8SNK BBS 144.850 !5301.59N/00538.84EB