APRS Packet Errors for INLINK (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
20260928154754INLINK>APWL2K,TCPIP*,N-1,qAR,AE7AF:;KD3WCO-10*28943. 12. .010Mink Packety
20260928155239INLINK>APWL2K,TCPIS,NK-1,qAR,AE7AF:;KH6ESK *280352z2203. NW15. Wa145.03MHz Winlink V M W Gaay
20260928161338INLINK>APWL2K,TCPS,WLNK-1,qAR,AE7AF:;W0JWT-80z3853. NW22. W00MHz Wa
20260928162558INLINK>APWL2K,TCAS,WLNK-1,qAR,AE7AF:;80425z447. z Winleway
20260928163926INLINK>AS,WLNK-1,qAR,AE7AF:;K-0 *280z011. 27. Wa3MHz inlink Packet Gatewa
20260928165934INLINK>A2K,TCPIS,W,qAR,AE7AF:;N00 *280459z4 W08. WaHz ink P
20260928170124INLINK>APWL2K,TCPIP1,qAR,AE7AF:;11 *280gi/I-Gate
20260928173348INLINK>APK,TCPIPAS,WLN,qAR,AE7AF:;AC9DE-10 *280533z3956. NW0 Wa145.610 inlink ket Ga
20260928174332INLINK>L2K,TPIP*,qAS,AE7AF:;K4 *24z425 W80.a145070MWinlnket a
20260928181111INLINK>APWL2K,TCPIqAS,WL1,qAR,AE7AF:;VE2-11*281z4618NW07a145.0Hz WinFM Widaeway
20260928182248INLINK>ACPINK-1,qAR,AE7AF:;W7OWO-10 z4518. 30MzAFM atewa
20260928195844INLINK>APWL2K,TCPIP*,qAS,AE7AF:;KT1*28071. N.45.050Hnlink Packet Ga
20260928202903INLINK>2K,TCPNK-1,qAR,AE7AF:;07412. W.010MHnk VA FM WGateway
20260928203414INLINK>APL2K,TCPIPNK-1,qAR,AE7AF:;AD7DD083 Wa4z Winlink V Ga
20260928203649INLINK>APCPIP1,qAR,AE7AF:;EA1URO-11*28216.717.4.55ilinktewa