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
20251225022625LZ1PRO-9>APLRT1,WIDE1-1,qAR,LZ1PRO-10:!/8nqETAJg_ CQ.../...g...t046r...p...P...h..b10262
20251225023629LZ1PRO-9>APLRT1,WIDE1-1,qAR,LZ1PRO-10:!/8nq=TAJn_ KQ.../...g...t046r...p...P...h..b10273
20251225024632LZ1PRO-9>APLRT1,WIDE1-1,qAR,LZ1PRO-10:!/8nqVTAJz_ PQ.../...g...t046r...p...P...h..b10278
20251225030640LZ1PRO-9>APLRT1,WIDE1-1,qAR,LZ1PRO-10:!/8nq9TAJk_
20251225031644LZ1PRO-9>APLRT1,WIDE1-1,qAR,LZ1PRO-10:!/8nq1TAJs_
20251225032649LZ1PRO-9>APLRT1,WIDE1-1,qAR,LZ1PRO-10:!/8nqCTAJd_ CQ.../...g...t046r...p...P...h..b10259