APRS Packet Errors for EA5PJ (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
20260208181101EA5PJ>APAT51,WIDE1-1,WIDE2-1,qAR,EA5AKC-1:!3823.65N!00030.89W-019/000/A=00000073! QRZ.COM
20260208184113EA5PJ>APAT51,WIDE1-1,WIDE2-1,qAR,EA5AKC-1:!3823.65N!00030.89W-019/000/A=00000073! QRZ.COM
20260208191123EA5PJ>APAT51,WIDE1-1,WIDE2-1,qAR,EA5AKC-1:!3823.65N!00030.89W-019/000/A=00000073! QRZ.COM
20260208194135EA5PJ>APAT51,WIDE1-1,WIDE2-1,qAR,EA5AKC-1:!3823.65N!00030.89W-019/000/A=00000073! QRZ.COM
20260208201147EA5PJ>APAT51,WIDE1-1,WIDE2-1,qAR,EA5AKC-1:!3823.65N!00030.89W-019/000/A=00000073! QRZ.COM
20260208204156EA5PJ>APAT51,WIDE1-1,WIDE2-1,qAR,EA5AKC-1:!3823.65N!00030.89W-019/000/A=00000073! QRZ.COM
20260208211205EA5PJ>APAT51,WIDE1-1,WIDE2-1,qAR,EA5AKC-1:!3823.65N!00030.89W-019/000/A=00000073! QRZ.COM
20260208214214EA5PJ>APAT51,WIDE1-1,WIDE2-1,qAR,EA5AKC-1:!3823.65N!00030.89W-232/000/A=00000073! QRZ.COM
20260208221223EA5PJ>APAT51,WIDE1-1,WIDE2-1,qAR,EA5AKC-1:!3823.65N!00030.89W-232/000/A=00000073! QRZ.COM
20260208224233EA5PJ>APAT51,WIDE1-1,WIDE2-1,qAR,EA5AKC-1:!3823.65N!00030.89W-232/000/A=00000073! QRZ.COM
20260208231257EA5PJ>APAT51,WIDE1-1,WIDE2-1,qAR,EA5AKC-1:!3823.65N!00030.89W-232/000/A=00000073! QRZ.COM
20260208234307EA5PJ>APAT51,WIDE1-1,WIDE2-1,qAR,EA5AKC-1:!3823.65N!00030.89W-232/000/A=00000073! QRZ.COM