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
20250211081201HG8LXL-7>APLRT1,WIDE1-1,qAO,HG8GL-15:!/6b_QSM{__ 6Q.../...g...t074h15b10339
20250211082205HG8LXL-7>APLRT1,WIDE1-1,qAO,HG8GL-15:!/6b_XSM{U_ Q.../...g...t076h16b10351|%E!!|
20250211084215HG8LXL-7>APLRT1,WIDE1-1,qAR,HA9OZD-17:!/6b_LSM{X_ ^Q.../...g...t071h18b10324
20250211085219HG8LXL-7>APLRT1,WIDE1-1,qAO,HG8PKU-11:!/6b_SM{]_ mQ.../...g...t069h19b10330
20250211090223HG8LXL-7>APLRT1,WIDE1-1,qAO,HG8GL-15:!/6b_jSM{]_ eQ.../...g...t067h21b10328
20250211112335HG8LXL-7>APLRT1,WIDE1-1,qAO,HA9OZD-18:!/6b_OSM{g_ !Q.../...g...t053h26b10330