APRS Packet Errors for EA3BIL-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
20220928110016EA3BIL-2>APRS,TCPIP*,qAS,BM2142POS:@281100z4133.36N/00201.100ErHOME 439.4750/433.4750 CC2
20220928113021EA3BIL-2>APRS,TCPIP*,qAS,BM2142POS:@281130z4133.36N/00201.100ErHOME 439.4750/433.4750 CC2
20220928120023EA3BIL-2>APRS,TCPIP*,qAS,BM2142POS:@281200z4133.36N/00201.100ErHOME 439.4750/433.4750 CC2
20220928123025EA3BIL-2>APRS,TCPIP*,qAS,BM2142POS:@281230z4133.36N/00201.100ErHOME 439.4750/433.4750 CC2
20220928130027EA3BIL-2>APRS,TCPIP*,qAS,BM2142POS:@281300z4133.36N/00201.100ErHOME 439.4750/433.4750 CC2
20220928133027EA3BIL-2>APRS,TCPIP*,qAS,BM2142POS:@281330z4133.36N/00201.100ErHOME 439.4750/433.4750 CC2
20220928140028EA3BIL-2>APRS,TCPIP*,qAS,BM2142POS:@281400z4133.36N/00201.100ErHOME 439.4750/433.4750 CC2
20220928143035EA3BIL-2>APRS,TCPIP*,qAS,BM2142POS:@281430z4133.36N/00201.100ErHOME 439.4750/433.4750 CC2
20220928150033EA3BIL-2>APRS,TCPIP*,qAS,BM2142POS:@281500z4133.36N/00201.100ErHOME 439.4750/433.4750 CC2
20220928153035EA3BIL-2>APRS,TCPIP*,qAS,BM2142POS:@281530z4133.36N/00201.100ErHOME 439.4750/433.4750 CC2
20220928160036EA3BIL-2>APRS,TCPIP*,qAS,BM2142POS:@281600z4133.36N/00201.100ErHOME 439.4750/433.4750 CC2
20220928163039EA3BIL-2>APRS,TCPIP*,qAS,BM2142POS:@281630z4133.36N/00201.100ErHOME 439.4750/433.4750 CC2