APRS Packet Errors for TA7ZN-8 (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
20260208131831TA7ZN-8>APAT81,WIDE1-1,WIDE2-1,qAO,YM5SKE-10:!3751.22N/03230.93E[066/000/A=003464TA5EMC OPERATOR AHMET 73
20260208132333TA7ZN-8>APAT81,WIDE1-1,WIDE2-1,qAO,YM5SKE-10:!3752.18N/03231.55E[033/000/A=003412TA5EMC OPERATOR AHMET 73
20260208132835TA7ZN-8>APAT81,WIDE1-1,WIDE2-1,qAO,YM5SKE-10:!3753.62N/03230.89E[307/000/A=003389TA5EMC OPERATOR AHMET 73