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
20260524140203LZ1PRO-9>APLRT1,WIDE1-1,qAR,LZ1PRO-10:!/8wLETDSr_ &Q.../...g...t090r...p...P...h..b10293
20260524142211LZ1PRO-9>APLRT1,WIDE1-1,qAR,LZ1PRO-10:!/8wL;TDSh_ BQ.../...g...t090r...p...P...h..b10346
20260524143215LZ1PRO-9>APLRT1,WIDE1-1,qAR,LZ1PRO-10:!/8wL5TDSt_ ,Q.../...g...t089r...p...P...h..b10303
20260524144220LZ1PRO-9>APLRT1,WIDE1-1,qAO,LZ3DJ-10:!/8wLATDSp_ 4Q.../...g...t089r...p...P...h..b10316
20260524145224LZ1PRO-9>APLRT1,WIDE1-1,qAR,LZ1PRO-10:!/8wLWTDSm_ 1Q.../...g...t089r...p...P...h..b10310
20260524185238LZ1PRO-9>APLRT1,WIDE1-1,qAR,LZ1PRO-10:!/8nqATAJd_ BQ.../...g...t088r...p...P...h..b10307
20260524190242LZ1PRO-9>APLRT1,WIDE1-1,qAR,LZ1PRO-10:!/8npyTAJb_ EQ.../...g...t086r...p...P...h..b10311
20260524191246LZ1PRO-9>APLRT1,WIDE1-1,qAR,LZ1PRO-10:!/8nq7TAJd_ >Q.../...g...t083r...p...P...h..b10304
20260524192251LZ1PRO-9>APLRT1,WIDE1-1,qAR,LZ1PRO-10:!/8nq=TAJ__ >Q.../...g...t081r...p...P...h..b10306
20260524193254LZ1PRO-9>APLRT1,WIDE1-1,qAR,LZ1PRO-10:!/8nq(TAJg_ 9Q.../...g...t080r...p...P...h..b10299
20260524194259LZ1PRO-9>APLRT1,WIDE1-1,qAR,LZ1PRO-10:!/8nq0TAJg_ 5Q.../...g...t078r...p...P...h..b10295
20260524195305LZ1PRO-9>APLRT1,WIDE1-1,qAR,LZ1PRO-10:!/8nq>TAJg_ 8Q.../...g...t077r...p...P...h..b10299Yanko on road