APRS Packet Errors for TA9ERZ-5 (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
20251226150239TA9ERZ-5>APAT81,YM9ERZ*,WIDE2-2,qAR,TA9A-15:!3952.:0N/04114.52ES/A=000000439.425 QRV
20251226150447TA9ERZ-5>APAT81,YM9ERZ*,WIDE2-2,qAR,YM9KE:!3952.:0N/04114.52ES/A=000000439.425 QRV
20251226160835TA9ERZ-5>APAT81,YM9ERZ*,WIDE2-2,qAR,YM9KE:!3952.:0N/04114.52ES/A=000000439.425 QRV
20251226161134TA9ERZ-5>APAT81,YM9ERZ*,WIDE2-2,qAR,YM9KE:!3952.:0N/04114.52ES/A=000000439.425 QRV
20251226161310TA9ERZ-5>APAT81,YM9ERZ*,WIDE2-2,qAR,YM9KE:!3952.:0N/04114.52ES/A=000000439.425 QRV
20251226161418TA9ERZ-5>APAT81,YM9ERZ*,WIDE2-2,qAR,TA9A-15:!3952.:0N/04114.
20251226161616TA9ERZ-5>APAT81,YM9ERZ*,WIDE2-2,qAR,YM9KE:!3952.:0N/04114.52ES/A=000000439.425 QRV
20251226162205TA9ERZ-5>APAT81,YM9ERZ*,WIDE2-2,qAR,TA9A-15:!3952.:0N/04114.52ES/A=000000439.425 QRV
20251226162452TA9ERZ-5>APAT81,YM9ERZ*,WIDE2-2,qAR,TA9A-15:!3952.:0N/04114.52ES/A=000000439.425 QRV
20251226162731TA9ERZ-5>APAT81,YM9ERZ*,WIDE2-2,qAR,TA9A-15:!3952.:0N/04114.52ES/A=000000439.425 QRV
20251226162937TA9ERZ-5>APAT81,YM9ERZ*,WIDE2-2,qAR,TA9A-15:!3952.:0N/04114.52ES/A=000000439.425 QRV
20251226163120TA9ERZ-5>APAT81,YM9ERZ*,WIDE2-2,qAR,TA9A-15:!3952.:0N/04114.52ES/A=000000439.425 QRV