APRS Packet Errors for O6ZQ (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
20260925010339O6ZQ>A00,TqAC,SIXTH,qAR,AE7AF:;JY-060*103z3494N13342.41E;SOTv. planned o026092700z
20260925013101O6ZQ>APN100,TCPIT,qAR,AE7AF:;DLB-3z4729.3302.;SOactiv. planned on 60925 0730z
20260925033750O6ZQ>APN10NTH,qAR,AE7AF:;JR7CVG0337z361.42E;1MHz Stvation JA/NI
20260925052754O6ZQ>APN10CPI,EI,qAR,AE7AF:;GW-0250z248.77035;SOAtivlnne2260 11
20260925062454O6ZQ>APN100,TCqAC,FOURTH,qAR,AE7AF:;I/TN-335 01056OTA https:/.be/-/335