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
20190216204132PI1SNK>APBPQ1,TCPIP*,qAC,PD2RLD-JS:;PI8SNK BBS 144.850 !5301.59N/00538.84EB
20190216210726PI1SNK>APBPQ1,TCPIP*,qAC,PD2RLD-JS:;PI8SNK BBS 144.850 !5301.59N/00538.84EB
20190216213323PI1SNK>APBPQ1,TCPIP*,qAC,PD2RLD-JS:;PI8SNK BBS 144.850 !5301.59N/00538.84EB
20190216215918PI1SNK>APBPQ1,TCPIP*,qAC,PD2RLD-JS:;PI8SNK BBS 144.850 !5301.59N/00538.84EB
20190216222515PI1SNK>APBPQ1,TCPIP*,qAC,PD2RLD-JS:;PI8SNK BBS 144.850 !5301.59N/00538.84EB
20190216225111PI1SNK>APBPQ1,TCPIP*,qAC,PD2RLD-JS:;PI8SNK BBS 144.850 !5301.59N/00538.84EB
20190216231706PI1SNK>APBPQ1,TCPIP*,qAC,PD2RLD-JS:;PI8SNK BBS 144.850 !5301.59N/00538.84EB
20190216234300PI1SNK>APBPQ1,TCPIP*,qAC,PD2RLD-JS:;PI8SNK BBS 144.850 !5301.59N/00538.84EB
20190217000900PI1SNK>APBPQ1,TCPIP*,qAC,PD2RLD-JS:;PI8SNK BBS 144.850 !5301.59N/00538.84EB
20190217003456PI1SNK>APBPQ1,TCPIP*,qAC,PD2RLD-JS:;PI8SNK BBS 144.850 !5301.59N/00538.84EB
20190217010049PI1SNK>APBPQ1,TCPIP*,qAC,PD2RLD-JS:;PI8SNK BBS 144.850 !5301.59N/00538.84EB
20190217012650PI1SNK>APBPQ1,TCPIP*,qAC,PD2RLD-JS:;PI8SNK BBS 144.850 !5301.59N/00538.84EB
20190217015247PI1SNK>APBPQ1,TCPIP*,qAC,PD2RLD-JS:;PI8SNK BBS 144.850 !5301.59N/00538.84EB
20190217021844PI1SNK>APBPQ1,TCPIP*,qAC,PD2RLD-JS:;PI8SNK BBS 144.850 !5301.59N/00538.84EB