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
20250314182725SQ9ANB-4>APLRT1,WIDE2-1,qAR,SQ9UKL-1:!/5.lKSO/x_ 2Q.../...g...t085r...p...P...h31b10061
20250314182758SQ9ANB-4>APLRT1,SQ9UKL-1*,qAR,SP9KSK-3:!/5.lKSO/x_ 2Q.../...g...t085r...p...P...h31b10061
20250314183726SQ9ANB-4>APLRT1,WIDE2-1,qAR,SQ9UKL-1:!/5.lASO/W_ XQ.../...g...t085r...p...P...h31b10088TTGO T-Beam S3 SUPREME V3
20250314183808SQ9ANB-4>APLRT1,SQ9UKL-1*,qAR,SP9KSK-3:!/5.lASO/W_ XQ.../...g...t085r...p...P...h31b10088TTGO T-Beam S3 SUPREME V3
20250314184727SQ9ANB-4>APLRT1,WIDE2-1,qAR,SQ9UKL-1:!/5.l&SO/`_ GQ.../...g...t086r...p...P...h32b10077
20250314185728SQ9ANB-4>APLRT1,WIDE2-1,qAR,SQ9UKL-1:!/5.kuSO/e_ VQ.../...g...t086r...p...P...h32b10088
20250314190730SQ9ANB-4>APLRT1,WIDE2-1,qAR,SQ9UKL-1:!/5.l"SO//_ sQ.../...g...t085r...p...P...h32b10110
20250314192825SQ9ANB-4>APLRT1,WIDE2-1,qAR,SQ9UKL-1:!/5.l9SO/`_ TQ.../...g...t082r...p...P...h32b10092
20250314193826SQ9ANB-4>APLRT1,WIDE2-1,qAR,SQ9ANB-10:!/5.kwSO/R_ GQ.../...g...t084r...p...P...h32b10083