APRS Packet Errors for PI1SNK-2 (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
20180716181803PI1SNK-2>APBPQ1,TCPIP*,qAC,PD2RLD-JS:;PI8SNK BBS 144.8875 !5301.59N/00538.84EB
20180716184620PI1SNK-2>APBPQ1,TCPIP*,qAC,PD2RLD-JS:;PI8SNK BBS 144.8875 !5301.59N/00538.84EB
20180716191435PI1SNK-2>APBPQ1,TCPIP*,qAC,PD2RLD-JS:;PI8SNK BBS 144.8875 !5301.59N/00538.84EB
20180716194249PI1SNK-2>APBPQ1,TCPIP*,qAC,PD2RLD-JS:;PI8SNK BBS 144.8875 !5301.59N/00538.84EB
20180716201104PI1SNK-2>APBPQ1,TCPIP*,qAC,PD2RLD-JS:;PI8SNK BBS 144.8875 !5301.59N/00538.84EB
20180716203918PI1SNK-2>APBPQ1,TCPIP*,qAC,PD2RLD-JS:;PI8SNK BBS 144.8875 !5301.59N/00538.84EB
20180716210731PI1SNK-2>APBPQ1,TCPIP*,qAC,PD2RLD-JS:;PI8SNK BBS 144.8875 !5301.59N/00538.84EB
20180716213544PI1SNK-2>APBPQ1,TCPIP*,qAC,PD2RLD-JS:;PI8SNK BBS 144.8875 !5301.59N/00538.84EB
20180716220400PI1SNK-2>APBPQ1,TCPIP*,qAC,PD2RLD-JS:;PI8SNK BBS 144.8875 !5301.59N/00538.84EB
20180716223215PI1SNK-2>APBPQ1,TCPIP*,qAC,PD2RLD-JS:;PI8SNK BBS 144.8875 !5301.59N/00538.84EB
20180716230026PI1SNK-2>APBPQ1,TCPIP*,qAC,PD2RLD-JS:;PI8SNK BBS 144.8875 !5301.59N/00538.84EB
20180716232841PI1SNK-2>APBPQ1,TCPIP*,qAC,PD2RLD-JS:;PI8SNK BBS 144.8875 !5301.59N/00538.84EB
20180716235657PI1SNK-2>APBPQ1,TCPIP*,qAC,PD2RLD-JS:;PI8SNK BBS 144.8875 !5301.59N/00538.84EB