APRS Packet Errors for TA9MFE-7 (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
20260405123439TA9MFE-7>APAT81-7,YM9ERZ*,WIDE2-2,qAR,TA9A-15:!4002.41N/04111.06E
20260405124319TA9MFE-7>APAT81-7,WIDE1-1,WIDE2-2,qAR,TA9A-15:!4002.41X310/000/A=006092TA9MFE
20260405125710TA9MFE-7>APAT81-7,WIDE1-1,WIDE2-2,qAR,TA9A-15:!4002.42N/04111
20260405130345TA9MFE-7>APAT81-7,WIDE1-1,WIDE2-2,qAR,TA9A-15:!4002.41N/041
20260405130649TA9MFE-7>APAT81-7,WIDE1-1,WIDE2-2,qAR,TA9A-15:!4002.41N/0411
20260405131819TA9MFE-7>APAT81-7,WIDE1-1,WIDE2-2,qAR,TA9A-15:!4002.42N/04111.06
20260405140314TA9MFE-7>APAT81-7,WIDE1-1,WIDE2-2,qAR,TA9A-15:!4002.42N/04111.06
20260405142217TA9MFE-7>APAT81-7,YM9ERZ*,WIDE2-2,qAR,TA9A-15:!4002.42N/04111.05