APRS Packet Errors for LZ1PRO-9 (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
20250717170158LZ1PRO-9>APLRT1,WIDE1-1,qAR,LZ1PDB-10:!/8r@3TC"c_ ;Q.../...g...t085r...p...P...h..b10187
20250717171202LZ1PRO-9>APLRT1,WIDE1-1,qAR,LZ1PRO-10:!/8r?xTC"h_ 1Q.../...g...t083r...p...P...h..b10176Yanko on road
20250717172206LZ1PRO-9>APLRT1,WIDE1-1,qAR,LZ1PRO-10:!/8r@7TC"a_ 7Q.../...g...t081r...p...P...h..b10182
20250717173210LZ1PRO-9>APLRT1,WIDE1-1,qAR,LZ1PRO-10:!/8r@#TC"^_ 3Q.../...g...t080r...p...P...h..b10175
20250717175218LZ1PRO-9>APLRT1,WIDE1-1,qAR,LZ1PRO-10:!/8r@(TC"^_ 8Q.../...g...t078r...p...P...h..b10184
20250717180222LZ1PRO-9>APLRT1,WIDE1-1,qAR,LZ1PRO-10:!/8r@.TC"k_ 9Q.../...g...t077r...p...P...h..b10183
20250717181226LZ1PRO-9>APLRT1,WIDE1-1,qAR,LZ1PRO-10:!/8r@(TC"c_ ?Q.../...g...t076r...p...P...h..b10199