APRS Packet Errors for NLINK (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
20260925011107NLINK>APWL21,qAR,AE7AF:;W3*25011121a14inlRA FM Gateway
20260925015147NLINK>APTCPIAS,1,qAR,AE7AF:;*254013. NW07 Wa145.010MHz Winl Packet Gateway
20260925024321NLINK>APWL2K,TCPIP*,qAS,AE7AF:;KF7ZYF-12*2543 NW12237. W50MHz Winlink Packet G
20260925025420NLINK>APWL2KK-1,qAR,AE7AF:;N5TW-120257. Wa145 VA Wi
20260925025815NLINK>APWL2K,T,qAS,AE7AF:;NU5D*250258z3103. NW09727. Wa145.030MHz Winlink Packet Gateway
20260925030450NLINK>APK,TP*,qAS,AE7AF:;W0030848. 937.a14. Wink FMW Gate
20260925030613NLINK>APWL2K,TCPIP,qAR,AE7AF:;W 306z41 NW Wa650Hnlinkcketway
20260925035121NLINK>CPILNK-1,qAR,AE7AF:;T-10 0351z3703. NW07. Wa100MHzW PatGatewa
20260925055813NLINK>APWL2K,TCPIPK-1,qAR,AE7AF:;NR6V-1*25055z4 NW11830MHz ink Pa
20260925061010NLINK>APWL2K,IP*,W1,qAR,AE7AF:;5*256 NW9 00Mzlnk e Gay
20260925063231NLINK>APWL2K,TCP,qAR,AE7AF:;K51 *250318. 942. MHz inlinFM Gay