APRS Packet Errors for SP5XTF-11 (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
20260209105755SP5XTF-11>APLRT1,WIDE1-1,qAO,SP5XTF-3:!/4,CcSkWD>!!QLora Tracker Test Bat=3.31V 25%
20260209105926SP5XTF-11>APLRT1,WIDE1-1,qAO,SP5XTF-3:!/4,?QSkW">AkQ
20260209105949SP5XTF-11>APLRT1,WIDE1-1,qAO,SP5XTF-3:!/4,2cSkTd>AuQ
20260209110002SP5XTF-11>APLRT1,WIDE1-1,qAO,SP5XTF-3:!/4,0@SkO2>AsQ
20260209110121SP5XTF-11>APLRT1,WIDE1-1,qAO,SP5XTF-3:!/4+{pSk.;>AdQ
20260209110222SP5XTF-11>APLRT1,WIDE1-1,qAO,SP5XTF-3:!/4+oXSjnn>AhQLora Tracker Test Bat=3.32V 26%
20260209110424SP5XTF-11>APLRT1,WIDE1-1,QB2M3,qAR,SQ5NBR-11:!/4+`#SjM=>BdQ
20260209110559SP5XTF-11>APLRT1,WIDE1-1,QA4L3,qAR,SQ5NBR-11:!/4+>KSjEU>BnQ
20260209110912SP5XTF-11>APLRT1,WIDE1-1,qAO,SP6RVW-11:!/4*_fSj7=>BzQ
20260209110925SP5XTF-11>APLRT1,WIDE1-1,qAO,SP5XTF-10:!/4*[aSj7.>C0Q
20260209110951SP5XTF-11>APLRT1,WIDE1-1,qAO,SP6RVW-11:!/4*Z2Sj;u>C-Q
20260209111004SP5XTF-11>APLRT1,SQ5NBR-11,WIDE1*,qAR,SP5CWC-1:!/4*Z2Sj;u>C-Ñ
20260209111008SP5XTF-11>APLRT1,WIDE1-1,qAO,SP6RVW-11:!/4*]wSjC#Q
20260209111051SP5XTF-11>APLRT1,WIDE1-1,qAO,SP5XTF-10:!/4*bjSj:->BuQ
20260209134547SP5XTF-11>APLRT1,WIDE1-1,qAO,SP5XTF-10:!/4*a8Sj:n>!!QLora Tracker Test Bat=3.35V 29%