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
20260713160852LZ1PRO-9>APLRT1,WIDE1-1,qAR,LZ1NAG-10:!/8uniTC[i_ {Q.../...g...t102r...p...P...h..b10221
20260713161903LZ1PRO-9>APLRT1,LZ1NAG-10*,qAR,LZ1PRO-10:!/8uo-TC[d_ uQ.../...g...t099r...p...P...h..b10213
20260713162907LZ1PRO-9>APLRT1,LZ1NAG-10*,qAR,LZ3JY-10:!/8unQTC[g_ )Q.../...g...t097r...p...P...h..b10236
20260713163905LZ1PRO-9>APLRT1,WIDE1-1,qAR,LZ1NAG-10:!/8uo6TC[g_ {Q.../...g...t095r...p...P...h..b10222
20260713164909LZ1PRO-9>APLRT1,WIDE1-1,qAR,LZ1NAG-10:!/8uo4TC[]_ zQ.../...g...t094r...p...P...h..b10223Yanko on road