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
20250509101418SQ9ANB-4>APLRT1,WIDE2-1,qAR,SQ9ANB-10:!/5.lJSO/Y_ QQ.../...g...t077r...p...P...h23b10213
20250509102419SQ9ANB-4>APLRT1,WIDE2-1,qAR,SQ9ANB-10:!/5.lPSO/W_ ?Q.../...g...t077r...p...P...h23b10201
20250509103420SQ9ANB-4>APLRT1,WIDE2-1,qAR,SQ9UKL-1:!/5.krSO0L_
20250509104421SQ9ANB-4>APLRT1,WIDE2-1,qAR,SQ9ANB-10:!/5.l+SO/T_ _Q.../...g...t077r...p...P...h23b10221TTGO T-Beam S3 SUPREME V3
20250509105422SQ9ANB-4>APLRT1,WIDE2-1,qAR,SQ9ANB-10:!/5.l:SO/C_ rQ.../...g...t077r...p...P...h23b10235
20250509110423SQ9ANB-4>APLRT1,WIDE2-1,qAR,SQ9ANB-10:!/5.l
20250509111424SQ9ANB-4>APLRT1,WIDE2-1,qAR,SQ9ANB-10:!/5.lESO/Y_ JQ.../...g...t077r...p...P...h23b10209
20250509112425SQ9ANB-4>APLRT1,WIDE2-1,qAR,SQ9ANB-10:!/5.l>SO/W_ LQ.../...g...t077r...p...P...h23b10209
20250509113426SQ9ANB-4>APLRT1,WIDE2-1,qAR,SQ9UKL-1:!/5.l:SO/{_ NQ.../...g...t077r...p...P...h23b10211
20250509114427SQ9ANB-4>APLRT1,WIDE2-1,qAR,SQ9ANB-10:!/5.lQ.../...g...t077r...p...P...h24b10200
20250509115428SQ9ANB-4>APLRT1,WIDE2-1,qAR,SQ9ANB-10:!/5.lPSO/t_ GQ.../...g...t077r...p...P...h24b10207