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
20260905051532LZ3JY-9>APLRT1,WIDE1-1,WIDE2-1,qAR,LZ3JY-10:!/8uSUTCDh_ DQ.../...g...t076r...p...P...h25b10321
20260905052536LZ3JY-9>APLRT1,WIDE1-1,WIDE2-1,qAR,LZ1HCO-10:!/8uS@TCE%_ .Q.../...g...t076r...p...P...h25b10286
20260905053540LZ3JY-9>APLRT1,WIDE1-1,WIDE2-1,qAR,LZ1HCO-10:!/8uS+TCE/_ )Q.../...g...t076r...p...P...h25b10279
20260905054544LZ3JY-9>APLRT1,WIDE1-1,WIDE2-1,qAR,LZ3JY-10:!/8uS5TCE7_ /Q.../...g...t076r...p...P...h25b10287
20260905055547LZ3JY-9>APLRT1,WIDE1-1,WIDE2-1,qAR,LZ1HCO-10:!/8uSJTCDr_ vQ.../...g...t076r...p...P...h25b10258
20260905060552LZ3JY-9>APLRT1,WIDE1-1,WIDE2-1,qAR,LZ3JY-10:!/8uSrTCEB_ =Q.../...g...t076r...p...P...h25b10311
20260905061556LZ3JY-9>APLRT1,WIDE1-1,WIDE2-1,qAR,LZ3JY-10:!/8uT:TCED_ ;Q.../...g...t077r...p...P...h25b10308
20260905062600LZ3JY-9>APLRT1,WIDE1-1,WIDE2-1,qAR,LZ3JY-10:!/8uSoTCE2_ zQ.../...g...t077r...p...P...h25b10264
20260905063604LZ3JY-9>APLRT1,WIDE1-1,WIDE2-1,qAR,LZ3JY-10:!/8uSVTCE-_ +Q.../...g...t077r...p...P...h25b10283
20260905064609LZ3JY-9>APLRT1,WIDE1-1,WIDE2-1,qAR,LZ3JY-10:!/8uRxTCEL_ tQ.../...g...t077r...p...P...h29b10255SWATbg Team, SIMPLEX 439.625 MHz, CTCSS 123.0
20260905065613LZ3JY-9>APLRT1,WIDE1-1,WIDE2-1,qAR,LZ3JY-10:!/8uS/TCEQ_ zQ.../...g...t078r...p...P...h30b10263