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
20180526233201PI1SNK-2>APBPQ1,TCPIP*,qAC,PD2RLD-JS:;PI8SNK BBS 144.8875 !5301.59N/00538.84EB
20180527000018PI1SNK-2>APBPQ1,TCPIP*,qAC,PD2RLD-JS:;PI8SNK BBS 144.8875 !5301.59N/00538.84EB
20180527002838PI1SNK-2>APBPQ1,TCPIP*,qAC,PD2RLD-JS:;PI8SNK BBS 144.8875 !5301.59N/00538.84EB
20180527005658PI1SNK-2>APBPQ1,TCPIP*,qAC,PD2RLD-JS:;PI8SNK BBS 144.8875 !5301.59N/00538.84EB
20180527012513PI1SNK-2>APBPQ1,TCPIP*,qAC,PD2RLD-JS:;PI8SNK BBS 144.8875 !5301.59N/00538.84EB
20180527015332PI1SNK-2>APBPQ1,TCPIP*,qAC,PD2RLD-JS:;PI8SNK BBS 144.8875 !5301.59N/00538.84EB
20180527022151PI1SNK-2>APBPQ1,TCPIP*,qAC,PD2RLD-JS:;PI8SNK BBS 144.8875 !5301.59N/00538.84EB
20180527025010PI1SNK-2>APBPQ1,TCPIP*,qAC,PD2RLD-JS:;PI8SNK BBS 144.8875 !5301.59N/00538.84EB
20180527031826PI1SNK-2>APBPQ1,TCPIP*,qAC,PD2RLD-JS:;PI8SNK BBS 144.8875 !5301.59N/00538.84EB
20180527034646PI1SNK-2>APBPQ1,TCPIP*,qAC,PD2RLD-JS:;PI8SNK BBS 144.8875 !5301.59N/00538.84EB
20180527041504PI1SNK-2>APBPQ1,TCPIP*,qAC,PD2RLD-JS:;PI8SNK BBS 144.8875 !5301.59N/00538.84EB
20180527044321PI1SNK-2>APBPQ1,TCPIP*,qAC,PD2RLD-JS:;PI8SNK BBS 144.8875 !5301.59N/00538.84EB
20180527051138PI1SNK-2>APBPQ1,TCPIP*,qAC,PD2RLD-JS:;PI8SNK BBS 144.8875 !5301.59N/00538.84EB