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
20220702083154EA3BIL-2>APRS,TCPIP*,qAS,BM2142POS:@020831z4133.36N/00201.100ErHOME 439.4750/433.4750 CC2
20220702090153EA3BIL-2>APRS,TCPIP*,qAS,BM2142POS:@020901z4133.36N/00201.100ErHOME 439.4750/433.4750 CC2
20220702093203EA3BIL-2>APRS,TCPIP*,qAS,BM2142POS:@020932z4133.36N/00201.100ErHOME 439.4750/433.4750 CC2
20220702100200EA3BIL-2>APRS,TCPIP*,qAS,BM2142POS:@021002z4133.36N/00201.100ErHOME 439.4750/433.4750 CC2
20220702103154EA3BIL-2>APRS,TCPIP*,qAS,BM2142POS:@021031z4133.36N/00201.100ErHOME 439.4750/433.4750 CC2
20220702110156EA3BIL-2>APRS,TCPIP*,qAS,BM2142POS:@021101z4133.36N/00201.100ErHOME 439.4750/433.4750 CC2
20220702113156EA3BIL-2>APRS,TCPIP*,qAS,BM2142POS:@021131z4133.36N/00201.100ErHOME 439.4750/433.4750 CC2
20220702120157EA3BIL-2>APRS,TCPIP*,qAS,BM2142POS:@021201z4133.36N/00201.100ErHOME 439.4750/433.4750 CC2
20220702123156EA3BIL-2>APRS,TCPIP*,qAS,BM2142POS:@021231z4133.36N/00201.100ErHOME 439.4750/433.4750 CC2
20220702130158EA3BIL-2>APRS,TCPIP*,qAS,BM2142POS:@021301z4133.36N/00201.100ErHOME 439.4750/433.4750 CC2
20220702133150EA3BIL-2>APRS,TCPIP*,qAS,BM2142POS:@021331z4133.36N/00201.100ErHOME 439.4750/433.4750 CC2
20220702140204EA3BIL-2>APRS,TCPIP*,qAS,BM2142POS:@021402z4133.36N/00201.100ErHOME 439.4750/433.4750 CC2