APRS Packet Errors for HG8LXL-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
20250326181502HG8LXL-7>APLRT1,WIDE1-1,qAO,HG8PKU-11:!/6uf:ST#u_ GQ.../...g...t069h46b10168
20250326190910HG8LXL-7>APLRT1,WIDE1-1,qAR,HA9OZD-17:!/q2CSUqh>€D
20250326190910HG8LXL-7>APLRT1,WIDE1-1,qAR,HA9OZD-17:!/q2CSUqh>€D
20250326192507HG8LXL-7>APLRT1,WIDE1-1,qAO,HG8PDN-11:!/6q6SSUpG_ ?Q.../...g...t067h47b10163
20250326193517HG8LXL-7>APLRT1,WIDE1-1,qAO,HG8PDN-11:!/6q6ZSUp?_ ,Q.../...g...t067h47b10157
20250326194521HG8LXL-7>APLRT1,WIDE1-1,qAO,HG8PKU-11:!/6q6^SUpL_ :Q.../...g...t067h47b10159
20250326195525HG8LXL-7>APLRT1,WIDE1-1,qAO,HG8GL-15:!/6q6XSUpG_ aQ.../...g...t067h47b10168
20250326200528HG8LXL-7>APLRT1,WIDE1-1,qAO,HG8PKU-11:!/6q6`SUpN_ VQ.../...g...t066h46b10166