APRS Packet Errors for WINK (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
20260928071458WINK>APWL2K,TAS,WLNK-1,qAR,AE7AF:;W *280714z2908227. 630MHz Winlint Gateway
20260928075622WINK>APWL2K,TCqS,WLNK-1,qAR,AE7AF:;KP4DOG-10756z1 W06702. W090MHz Winlinket Gateway
20260928081005WINK>APWL2K,TCPIPqAS,WLNK-1,qAR,AE7AF:;VE1PAT-11280810z4438. NW06337. Wa145.3inlncket Gway
20260928082056WINK>APWK,TCPIqAS,WLNK-1,qAR,AE7AF:;W7FLO-9 *280820z58. NMHz WkVARA Wdteway
20260928082244WINK>ALNK-1,qAR,AE7AF:;W8CMNKD0SFY-1>APJY,TCPIP*T2LANE:@082243hT:m33PHG3330 Colorado Springs IGate
20260928085729WINK>APWL2K,TCPIP*,LNK-1,qAR,AE7AF:;80857z152. z WinlGatewa
20260928095922WINK>APWL2K,TCPIP,LNK-1,qAR,AE7AF:;N1XP-80959z NW07042. .730MHz Winlnk Pacateway
20260928102037WINK>APWL2K,TCPIP*,qAS,AE7AF:;W7ACS-8*28120z4743.4395HnlinA FM Wide Gatew
20260928102822WINK>2K,TCPAS,1,qAR,AE7AF:;O-1028. 47.45.z Wk Pet ay
20260928103228WINK>APWL2K,TCP,WLNK-1,qAR,AE7AF:;AA7MI*28132z4803. Wa14MHz WinVRA Fteway
20260928103817WINK>APWL2K,TCPIP*,qAS,AE7AF:;K2FAM-1z Winlink VA Wide ay
20260928112914WINK>APWL2K,TCIP*,qAS,AE7AF:;Z-12*283643. 442. .650MHlnk VARA FM Wateway
20260928123323WINK>APWL2K,WLNK-1,qAR,AE7AF:;AD710 *281233z3. NW07. Wa1450MHz Winliaket Gaay
20260928123654WINK>APWL2K,TCPIP*,qAS,AE7AF:;HB9T *2816. NW Ea144Mz Winlink VARA FMateway