APRS Packet Errors for KI5YLX-7 (last 24 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
20260909150448KI5YLX-7>APAT81,WIDE1-1,WIDE2-1,qAR,W5NGU-3:!0000.00N0000.00Ek077/059/A=000000KI5YLX
20260909150653KI5YLX-7>APAT81,KI5RKU*,WIDE2-1,qAR,W5NGU-3:!0000.00N0000.00Ek090/060/A=000000KI5YLX
20260909150958KI5YLX-7>APAT81,WIDE1-1,WIDE2-1,qAO,N5COR-3:!0000.00N0000.00Ek074/063/A=000000KI5YLX
20260909151202KI5YLX-7>APAT81,WIDE1-1,WIDE2-1,qAO,N5COR-3:!0000.00N0000.00Ek090/063/A=000000KI5YLX
20260909151304KI5YLX-7>APAT81,WIDE1-1,WIDE2-1,qAO,N5COR-3:!0000.00N0000.00Ek093/062/A=000000KI5YLX
20260909151406KI5YLX-7>APAT81,WIDE1-1,WIDE2-1,qAO,N5COR-3:!0000.00N0000.00Ek159/060/A=000000KI5YLX
20260909151508KI5YLX-7>APAT81,WIDE1-1,WIDE2-1,qAO,N5COR-3:!0000.00N0000.00Ek135/060/A=000000KI5YLX
20260909151610KI5YLX-7>APAT81,WIDE1-1,WIDE2-1,qAO,N5COR-3:!0000.00N0000.00Ek125/055/A=000000KI5YLX
20260909151814KI5YLX-7>APAT81,WIDE1-1,WIDE2-1,qAO,N5COR-3:!0000.00N0000.00Ek114/057/A=000000KI5YLX
20260909152018KI5YLX-7>APAT81,WIDE1-1,WIDE2-1,qAO,N5COR-3:!0000.00N0000.00Ek239/000/A=000000KI5YLX
20260909152733KI5YLX-7>APAT81,KK5PP-3,WIDE1*,WIDE2-1,qAR,K5VZC-1:!0000.00N0000.00Ek046/033/A=000000KI5YLX
20260909152937KI5YLX-7>APAT81,KK5PP-3,WIDE1*,WIDE2-1,qAO,KG5JPL-1:!0000.00N0000.00Ek086/000/A=000000KI5YLX