APRS Packet Errors for KM6LYW-3 (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
20260209110005	KM6LYW-3>APRS,TCPIP*,qAC,T2PR:/091050z3854.83N/12057.14W_.../000g000t052r000h93b10282
20260209120005	KM6LYW-3>APRS,TCPIP*,qAC,T2OREGON:/091150z3854.83N/12057.14W_301/002g002t051r000h97b10277
20260209130005	KM6LYW-3>APRS,TCPIP*,qAC,T2MCI:/091250z3854.83N/12057.14W_295/001g003t049r000h99b10278
20260209140005	KM6LYW-3>APRS,TCPIP*,qAC,T2CAWEST:/091350z3854.83N/12057.14W_296/003g005t050r000h95b10272
20260209150005	KM6LYW-3>APRS,TCPIP*,qAC,T2USANW:/091450z3854.83N/12057.14W_063/001g002t047r000h98b10274
20260209160006	KM6LYW-3>APRS,TCPIP*,qAC,T2BC:/091550z3854.83N/12057.14W_010/001g003t047r000h99b10271