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
20260515123900LZ1PRO-9>APLRT1,WIDE1-1,qAR,LZ1NAG-10:!/8u:)TBk2_ $Q.../...g...t091r...p...P...h..b10139Yanko on road
20260515124903LZ1PRO-9>APLRT1,WIDE1-1,qAR,LZ1NAG-10:!/8u9ZTBk4_ xQ.../...g...t089r...p...P...h..b10128
20260515135931LZ1PRO-9>APLRT1,WIDE1-1,qAR,LZ1NAG-10:!/8u9?TBkF_ )Q.../...g...t080r...p...P...h..b10143
20260515141940LZ1PRO-9>APLRT1,WIDE1-1,qAR,LZ1NAG-10:!/8u9;TBk(_ %Q.../...g...t080r...p...P...h..b10137Yanko on road
20260515143947LZ1PRO-9>APLRT1,WIDE1-1,qAR,LZ1NAG-10:!/8u9_TBk<_ $Q.../...g...t080r...p...P...h..b10137
20260515144951LZ1PRO-9>APLRT1,WIDE1-1,qAR,LZ1NAG-10:!/8u9.TBk7_ 1Q.../...g...t080r...p...P...h..b10156
20260515150959LZ1PRO-9>APLRT1,WIDE1-1,qAR,LZ1NAG-10:!/8u9QTBk-_ vQ.../...g...t081r...p...P...h..b10122
20260515152003LZ1PRO-9>APLRT1,WIDE1-1,qAR,LZ1NAG-10:!/8u9vTBk-_ *Q.../...g...t081r...p...P...h..b10143
20260515154011LZ1PRO-9>APLRT1,WIDE1-1,qAR,LZ1NAG-10:!/8u:)TBkA_ $Q.../...g...t081r...p...P...h..b10135
20260515155015LZ1PRO-9>APLRT1,WIDE1-1,qAR,LZ1NAG-10:!/8u9OTBk-_ uQ.../...g...t081r...p...P...h..b10120