APRS Packet Errors for SQ9ANB-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
20250124185409	SQ9ANB-9>APLRT1,WIDE2-1,qAR,SQ9ANB-10:!/5.knSO.f_ nQ.../...g...t080r...p...P...h26b10193
20250124190410	SQ9ANB-9>APLRT1,WIDE2-1,qAR,SQ9ANB-10:!/5.lASO/2_ mQ.../...g...t080r...p...P...h27b10192
20250124190537	SQ9ANB-9>APLRT1,SQ9UKL-1*,qAR,SQ9ANB-10:!/5.lASO/2_ mQ.../...g...t080r...p...P...h27b10192
20250124191411	SQ9ANB-9>APLRT1,WIDE2-1,qAR,SQ9ANB-10:!/5.l@SO/c_ NQ.../...g...t080r...p...P...h26b10170TTGO T-Beam S3 SUPREME V3
20250124192412	SQ9ANB-9>APLRT1,WIDE2-1,qAR,SQ9ANB-10:!/5.lWSO0B_ 9Q.../...g...t080r...p...P...h26b10156
20250124193413	SQ9ANB-9>APLRT1,WIDE2-1,qAR,SQ9ANB-10:!/5.l>SO.o_ hQ.../...g...t080r...p...P...h26b10185
20250124193514	SQ9ANB-9>APLRT1,SQ9UKL-1*,qAR,SQ9ANB-10:!/5.l>SO.o_ hQ.../...g...t080r...p...P...h26b10185
20250124194414	SQ9ANB-9>APLRT1,WIDE2-1,qAR,SQ9ANB-10:!/5.lRSO08_ +Q.../...g...t079r...p...P...h27b10144
20250124195415	SQ9ANB-9>APLRT1,WIDE2-1,qAR,SQ9ANB-10:!/5.l`SO.:_ >Q.../...g...t079r...p...P...h26b10221