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
20260713085912LZ3JY-9>APLRT1,WIDE1-1,WIDE2-1,qAR,LZ3JY-10:!/8se9TDOq_ MQ.../...g...t092r...p...P...h29b10248
20260713090916LZ3JY-9>APLRT1,WIDE1-1,WIDE2-1,qAR,LZ3JY-10:!/8seFTDP)_ MQ.../...g...t092r...p...P...h30b10246
20260713091920LZ3JY-9>APLRT1,WIDE1-1,WIDE2-1,qAR,LZ3JY-10:!/8se4TDP1_ 7Q.../...g...t092r...p...P...h30b10217
20260713092924LZ3JY-9>APLRT1,WIDE1-1,WIDE2-1,qAR,LZ3JY-10:!/8se=TDP._ AQ.../...g...t092r...p...P...h30b10230
20260713093928LZ3JY-9>APLRT1,WIDE1-1,WIDE2-1,qAR,LZ3JY-10:!/8sesTDP._ PQ.../...g...t092r...p...P...h31b10249
20260713094933LZ3JY-9>APLRT1,WIDE1-1,WIDE2-1,qAR,LZ3JY-10:!/8se]TDOb_ LQ.../...g...t092r...p...P...h31b10242SWATbg Team, SIMPLEX 439.625 MHz, CTCSS 123.0
20260713095937LZ3JY-9>APLRT1,WIDE1-1,WIDE2-1,qAR,LZ3JY-10:!/8sdzTDO{_ QQ.../...g...t092r...p...P...h30b10250
20260713100942LZ3JY-9>APLRT1,WIDE1-1,WIDE2-1,qAR,LZ3JY-10:!/8se-TDP1_ FQ.../...g...t092r...p...P...h30b10237
20260713101945LZ3JY-9>APLRT1,WIDE1-1,WIDE2-1,qAR,LZ3JY-10:!/8seWTDOi_ XQ.../...g...t092r...p...P...h29b10262