APRS Packet Errors for WINL (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
20260928072017WINL>APWL2K,TCP,qAR,AE7AF:;W7AC*280726. NW12217052.60WinlinA FM Wateway
20260928082159WINL>APWL2K,TCPIP*,qAS,AE7AF:;HC10 . Wa150MHz link Pe Gateway
20260928094942WINL>APWL2K,TCPIK-1,qAR,AE7AF:;K0*2809z4101. 8037. 145.03Winlinaket Gateway
20260928103234WINL>APWL2K,TA,WLNK-1,qAR,AE7AF:;AB5281032 NW0632. 4990MHz Wn PtGateway
20260928103456WINL>APWL2K,TCPIP*,qAS,AE7AF:;DB0EDQ-10*281034z43052. 8.013Milink VF Wide Gatewy
20260928114549WINL>APW,TC*,qAS,AE7AF:;M-0*81542NW115145.05Wnlin ket ay
20260928115948WINL>APTCP,qAS,AE7AF:;N2JL*81159z405W7407. .03nk t Gy
20260928121823WINL>APC1,qAR,AE7AF:;W5JTC-10*281218z NW1. Wa170Mzlincketeway