APRS Packet Errors for CE2II-7 (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
20260208170511	CE2II-7>APLRT1,WIDE1-1,qAR,CE2II-10:=/_*9c
20260208170534	CE2II-7>APLRT1,WIDE1-1,qAR,CE2II-10:=/_*9-
20260208170557	CE2II-7>APLRT1,WIDE1-1,qAR,CE2II-10:=/_*7n
20260208175541	CE2II-7>APLRT1,WIDE1-1,qAR,CE2II-10:=/_*Xs
20260208180602	CE2II-7>APLRT1,WIDE1-1,qAR,CE2II-10:=/_*WJ
20260208181449	CE2II-7>APLRT1,WIDE1-1,qAR,CE2II-10:=/_*^G
20260208183049	CE2II-7>APLRT1,WIDE1-1,qAR,CE2II-10:=/_*3Y
20260208183112	CE2II-7>APLRT1,WIDE1-1,qAR,CE2II-10:=/_*4n
20260208183139	CE2II-7>APLRT1,WIDE1-1,qAR,CE2II-10:=/_*9E
20260208183207	CE2II-7>APLRT1,WIDE1-1,qAR,CE2II-10:=/_*9m
20260208183942	CE2II-7>APLRT1,WIDE1-1,qAR,CE2II-10:=/_*9^
20260208184005	CE2II-7>APLRT1,WIDE1-1,qAR,CE2II-10:=/_*7[
20260208184028	CE2II-7>APLRT1,WIDE1-1,qAR,CE2II-10:=/_*3q
20260208184118	CE2II-7>APLRT1,WIDE1-1,qAR,CE2II-10:=/_*$N
20260208184141	CE2II-7>APLRT1,WIDE1-1,qAR,CE2II-10:=/_)w_
20260208191105	CE2II-7>APLRT1,WIDE1-1,qAR,CE2II-10:=/_*XC
20260208194112	CE2II-7>APLRT1,WIDE1-1,qAR,CE2II-10:=/_*Xd
20260208195614	CE2II-7>APLRT1,WIDE1-1,qAR,CE2II-10:=/_*XH
20260208201117	CE2II-7>APLRT1,WIDE1-1,qAR,CE2II-10:=/_*XH