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
20250726035145	LZ3JY-9>APLRT1,WIDE1-1,WIDE2-1,qAR,LZ1ASO-10:!/93C/UR@_ mQ.../...g...t085r...p...P...h40b10161
20250726040149	LZ3JY-9>APLRT1,WIDE1-1,WIDE2-1,qAR,LZ1ASO-10:!/93C-UR@_ dQ.../...g...t085r...p...P...h41b10160
20250726041154	LZ3JY-9>APLRT1,WIDE1-1,WIDE2-1,qAR,LZ1ASO-10:!/93C6UR=_ zQ.../...g...t084r...p...P...h40b10163SWATbg Team, SIMPLEX 439.625 MHz, CTCSS 123.0
20250726042158	LZ3JY-9>APLRT1,WIDE1-1,WIDE2-1,qAO,TCSAR-3:!/93C-URG_ zQ.../...g...t085r...p...P...h41b10162
20250726043202	LZ3JY-9>APLRT1,WIDE1-1,WIDE2-1,qAR,LZ1ASO-10:!/93C-URB_ ZQ.../...g...t084r...p...P...h41b10159
20250726044206	LZ3JY-9>APLRT1,WIDE1-1,WIDE2-1,qAR,LZ1ASO-10:!/93C+UR=_ nQ.../...g...t084r...p...P...h41b10151
20250726050214	LZ3JY-9>APLRT1,WIDE1-1,WIDE2-1,qAR,LZ1ASO-10:!/93C*UR=_ `Q.../...g...t085r...p...P...h42b10159
20250726051218	LZ3JY-9>APLRT1,WIDE1-1,WIDE2-1,qAR,LZ1ASO-10:!/93BvUR6_ pQ.../...g...t085r...p...P...h43b10161