APRS Packet Errors for DL6YA-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
20260218175410DL6YA-5>APLRT1,WIDE1-1,qAO,DB0UHC-L4:!/4bj8P9ye_ zQ.../...g...t040r...p...P...h74b10075 Bat=3.26V (-94mA)
20260218180413DL6YA-5>APLRT1,WIDE1-1,qAO,DB0UHC-L4:!/4biiP9yt_ MQ.../...g...t040r...p...P...h73b10080
20260218183425DL6YA-5>APLRT1,WIDE1-1,qAO,DB0UHC-L4:!/4biVP9yt_ !Q.../...g...t039r...p...P...h73b10095
20260218184429DL6YA-5>APLRT1,WIDE1-1,qAO,DB0UHC-L4:!/4biOP9yt_ VQ.../...g...t038r...p...P...h72b10086
20260218190437DL6YA-5>APLRT1,WIDE1-1,qAO,DB0UHC-L4:!/4biaP9yv_ ZQ.../...g...t038r...p...P...h72b10072
20260218201505DL6YA-5>APLRT1,WIDE1-1,qAO,DB0UHC-L4:!/4bilP9yY_ jQ.../...g...t037r...p...P...h70b10089