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
20260220060307LZ1PRO-9>APLRT1,WIDE1-1,qAR,LZ1NAG-10:!/8t%"TCVc_ 4Q.../...g...t071r...p...P...h..b10143
20260220062315LZ1PRO-9>APLRT1,WIDE1-1,qAR,LZ1NAG-10:!/8t%=TCVt_ KQ.../...g...t065r...p...P...h..b10172
20260220071335LZ1PRO-9>APLRT1,WIDE1-1,qAR,LZ1NAG-10:!/8t$HTCVM_ JQ.../...g...t057r...p...P...h..b10165
20260220074347LZ1PRO-9>APLRT1,WIDE1-1,qAR,LZ1NAG-10:!/8t%ATCV\_ OQ.../...g...t055r...p...P...h..b10181
20260220080355LZ1PRO-9>APLRT1,WIDE1-1,qAR,LZ1NAG-10:!/8t$]TCW#_ tQ.../...g...t054r...p...P...h..b10235
20260220082403LZ1PRO-9>APLRT1,WIDE1-1,qAR,LZ1NAG-10:!/8t%0TCVM_ MQ.../...g...t054r...p...P...h..b10179Yanko on road
20260220083413LZ1PRO-9>APLRT1,LZ1NAG-10*,qAR,LZ1HCO-10:!/8t$mTCVf_ 8Q.../...g...t054r...p...P...h..b10151
20260220084417LZ1PRO-9>APLRT1,LZ1NAG-10*,qAR,LZ1EVA-10:!/8t%9TCVa_ NQ.../...g...t053r...p...P...h..b10183
20260220091422LZ1PRO-9>APLRT1,WIDE1-1,qAR,LZ1NAG-10:!/8t%(TCV\_ JQ.../...g...t053r...p...P...h..b10176
20260220092427LZ1PRO-9>APLRT1,WIDE1-1,qAR,LZ1NAG-10:!/8t%!TCVh_ KQ.../...g...t053r...p...P...h..b10177