APRS Packet Errors for SQ9ANB-4 (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
20251013100416	SQ9ANB-4>APLRT1,WIDE2-1,qAR,SQ9ANB-10:!/5.l_SO/j_ RQ.../...g...t085r...p...P...h32b10262TTGO T-Beam S3 SUPREME V3
20251013101417	SQ9ANB-4>APLRT1,WIDE2-1,qAR,SQ9ANB-10:!/5.k;SO0@_ NQ.../...g...t084r...p...P...h32b10203
20251013102418	SQ9ANB-4>APLRT1,WIDE2-1,qAR,SQ9ANB-10:!/5.lZSO/R_ tQ.../...g...t085r...p...P...h32b10286
20251013124251	SQ9ANB-4>APLRT1,WIDE2-1,qAR,SQ9ANB-10:!/5.m#SO/w_ >Q.../...g...t085r...p...P...h31b10303
20251013130253	SQ9ANB-4>APLRT1,WIDE2-1,qAR,SQ9ANB-10:!/5.l.SO/{_ AQ.../...g...t086r...p...P...h31b10238
20251013152109	SQ9ANB-4>APLRT1,WIDE2-1,qAR,SQ9ANB-10:!/5.l1SO/^_ OQ.../...g...t085r...p...P...h31b10247
20251013153110	SQ9ANB-4>APLRT1,WIDE2-1,qAR,SQ9ANB-10:!/5.l.SO0@_ zQ.../...g...t086r...p...P...h30b10217
20251013154111	SQ9ANB-4>APLRT1,WIDE2-1,qAR,SQ9ANB-10:!/5.l1SO/E_ FQ.../...g...t086r...p...P...h30b10241TTGO T-Beam S3 SUPREME V3