APRS Packet Errors for WIN (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
20261001113701WIN>APWL2K,TCPIP*,qAS,WLNK-1:;WCS-10 *137z3611. NW11517. Wank Packet G
20261001122831WIN>APWL2K,1,qAR,AE7AF:;W0M28z405. Wa145.ink Paay
20261001132437WIN>PLKTPP,LNK-1,qAR,AE7AF:;124z44 NW079W438.10Wnlink ateway
20261001133658WIN>APWL2K,TCPIPAS,WLNK-1,qAR,AE7AF:;JM-10 *103010MHz Winlink Packeay
20261001135340WIN>APWL2K,TCPAS,WLNK-1,qAR,AE7AF:;K3BBC-10 *010153z4038. a145.0H iln AAFM Wia
20261001140831WIN>APWL2K,TCPIP*,K-1,qAR,AE7AF:;KJ6TT016. NW11842. Wa22WinlinA FM WGatewa
20261001145209WIN>APWL2K,TP*,qAS,AE7AF:;HI8S-10 0252z1.010MHz k Pet aay
20261001154046WIN>APTCPAS,WLNK-1,qAR,AE7AF:;WB4UL010340z2838. NW. nli
20261001154410WIN>APWL2K,TCPIS,WLNK-1,qAR,AE7AF:;ZL1GSC-0344z375MH