APRS Packet Errors for LZ1PRO-9 (last 24 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
20250712080925LZ1PRO-9>APLRT1,WIDE1-1,qAR,LZ1PRO-10:!/8nZJTA{Z_ 0Q.../...g...t086r...p...P...h..b10224
20250712081929LZ1PRO-9>APLRT1,WIDE1-1,qAR,LZ1PRO-10:!/8nZJTA{U_ 8Q.../...g...t085r...p...P...h..b10236
20250712082934LZ1PRO-9>APLRT1,WIDE1-1,qAR,LZ1PRO-10:!/8nZGTA{]_ :Q.../...g...t085r...p...P...h..b10239
20250712083938LZ1PRO-9>APLRT1,WIDE1-1,qAR,LZ1PRO-10:!/8nZ=TA{X_ >Q.../...g...t085r...p...P...h..b10244
20250712084941LZ1PRO-9>APLRT1,WIDE1-1,qAR,LZ1PRO-10:!/8nZMTA{Q_ 4Q.../...g...t085r...p...P...h..b10230
20250713055638LZ1PRO-9>APLRT1,WIDE1-1,qAR,LZ1PRO-10:!/8w=]TBcl_ gQ.../...g...t097r...p...P...h..b10414
20250713060643LZ1PRO-9>APLRT1,WIDE1-1,qAR,LZ1PRO-10:!/8w=WTBci_ dQ.../...g...t094r...p...P...h..b10406
20250713063655LZ1PRO-9>APLRT1,WIDE1-1,qAR,LZ1PRO-10:!/8w=ZTBcb_ _Q.../...g...t089r...p...P...h..b10389Yanko on road
20250713064658LZ1PRO-9>APLRT1,WIDE1-1,qAR,LZ1PRO-10:!/8w=WTBcn_ eQ.../...g...t088r...p...P...h..b10411