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
20251009144201LZ3JY-9>APLRT1,WIDE1-1,WIDE2-1,qAR,LZ3JY-10:!/8seQ.../...g...t068r...p...P...h50b10253
20251009145206LZ3JY-9>APLRT1,WIDE1-1,WIDE2-1,qAR,LZ3JY-10:!/8se*TDP;_ >Q.../...g...t068r...p...P...h50b10253SWATbg Team, SIMPLEX 439.625 MHz, CTCSS 123.0
20251009150210LZ3JY-9>APLRT1,WIDE1-1,WIDE2-1,qAR,LZ3JY-10:!/8se.TDP;_ 9Q.../...g...t068r...p...P...h49b10247
20251009151214LZ3JY-9>APLRT1,WIDE1-1,WIDE2-1,qAR,LZ3JY-10:!/8seATDP._ GQ.../...g...t068r...p...P...h49b10268
20251009152218LZ3JY-9>APLRT1,WIDE1-1,WIDE2-1,qAR,LZ1PRO-10:!/8se(TDP6_ AQ.../...g...t068r...p...P...h48b10259
20251009153222LZ3JY-9>APLRT1,WIDE1-1,WIDE2-1,qAR,LZ3JY-10:!/8se6TDP._ 0Q.../...g...t068r...p...P...h48b10240
20251009154226LZ3JY-9>APLRT1,WIDE1-1,WIDE2-1,qAR,LZ3JY-10:!/8se7TDP1_ DQ.../...g...t068r...p...P...h46b10266
20251009155229LZ3JY-9>APLRT1,WIDE1-1,WIDE2-1,qAR,LZ3JY-10:!/8se4TDP1_ >Q.../...g...t068r...p...P...h47b10260
20251009160234LZ3JY-9>APLRT1,WIDE1-1,WIDE2-1,qAR,LZ3JY-10:!/8se)TDP8_ 0Q.../...g...t068r...p...P...h47b10242
20251009161238LZ3JY-9>APLRT1,WIDE1-1,WIDE2-1,qAR,LZ3JY-10:!/8seCTDP)_ ^Q.../...g...t067r...p...P...h46b10307
20251009162242LZ3JY-9>APLRT1,WIDE1-1,WIDE2-1,qAR,LZ3JY-10:!/8sdxTDOd_ ?Q.../...g...t067r...p...P...h46b10264