APRS Packet Errors for TA9M (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
20251219131452TA9M>APAT81-1,YM9ERZ*,WIDE2-2,qAR,TA9A-15:!3953.25N/04115.87E
20251219131913TA9M>APAT81-1,YM9ERZ*,WIDE2-2,qAR,TA9A-15:!®’ˆŠd@eð!3953.28N/04115.89Eb010/000/A=006348APRS Analog 878
20251219135659TA9M>APAT81-1,YM9ERZ*,WIDE2-2,qAR,TA9A-15:!3953.29N=006413APRS Analog 878
20251219140044TA9M>APAT81-1,YM9ERZ*,WIDE2-2,qAR,TA9A-15:!3953.28N/04115