APRS Packet Errors for LZ3JY-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
20251013150400LZ3JY-9>APLRT1,WIDE1-1,WIDE2-1,qAR,LZ1PRO-10:!/8uSzTCED_ 1Q.../...g...t067r...p...P...h46b10301
20251013151404LZ3JY-9>APLRT1,WIDE1-1,WIDE2-1,qAR,LZ1PRO-10:!/8uSfTCEG_ "Q.../...g...t067r...p...P...h46b10279
20251013152408LZ3JY-9>APLRT1,WIDE1-1,WIDE2-1,qAR,LZ1MTS-1:!/8uS_TCEI_ "Q.../...g...t067r...p...P...h46b10280
20251013153412LZ3JY-9>APLRT1,WIDE1-1,WIDE2-1,qAR,LZ1PRO-10:!/8uSUTCE@_ wQ.../...g...t067r...p...P...h46b10270
20251013154416LZ3JY-9>APLRT1,WIDE1-1,WIDE2-1,qAR,LZ1HCO-10:!/8uS_TCE=_ *Q.../...g...t067r...p...P...h45b10293
20251013155420LZ3JY-9>APLRT1,WIDE1-1,WIDE2-1,qAR,LZ1MTS-1:!/8uSUTCE(_ %Q.../...g...t066r...p...P...h45b10286
20251013160425LZ3JY-9>APLRT1,WIDE1-1,WIDE2-1,qAR,LZ1PRO-10:!/8uSdTCE4_ -Q.../...g...t066r...p...P...h45b10299SWATbg Team, SIMPLEX 439.625 MHz, CTCSS 123.0
20251013170449LZ3JY-9>APLRT1,WIDE1-1,WIDE2-1,qAR,LZ1PRO-10:!/8uSYTCDw_ 8Q.../...g...t065r...p...P...h44b10318
20251013171453LZ3JY-9>APLRT1,WIDE1-1,WIDE2-1,qAR,LZ3JY-10:!/8uSrTCE2_ 6Q.../...g...t065r...p...P...h44b10315