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
20251219161643DL6YA-5>APLRT1,WIDE1-1,qAO,DB0UHC-L4:!/4bimP9yV_ pQ.../...g...t054r...p...P...h67b10250 Bat=3.28V (-91mA)
20251219162647DL6YA-5>APLRT1,WIDE1-1,qAO,DB0UHC-L4:!/4bj[P9yq_ Q.../...g...t053r...p...P...h68b10266
20251219165620DL6YA-5>APLRT1,WIDE1-1,qAO,DB0UHC-L4:!/4biUP9yL_ 7Q.../...g...t052r...p...P...h69b10226
20251219171628DL6YA-5>APLRT1,WIDE1-1,qAO,DB0UHC-L4:!/4biTP9y^_ bQ.../...g...t051r...p...P...h69b10234
20251219173636DL6YA-5>APLRT1,WIDE1-1,qAO,DB0UHC-L4:!/4bh{P9y*_ zQ.../...g...t051r...p...P...h69b10204
20251219174641DL6YA-5>APLRT1,WIDE1-1,qAO,DB0UHC-L4:!/4biPP9yO_ =Q.../...g...t051r...p...P...h69b10218 Bat=3.05V (-94mA)
20251219175644DL6YA-5>APLRT1,WIDE1-1,qAO,DB0UHC-L4:!/4biJP9yO_ WQ.../...g...t050r...p...P...h69b10212