APRS Packet Errors for WIK (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
20260927215312WIK>APTCPAS,W,qAR,AE7AF:;KM4AZW70953z36NW08 Wa10MHzink t Ga
20260927221326WIK>APWL2K,TCPAS,WLNK-1,qAR,AE7AF:;WSA *271013z4016.W074 Wa145.0 inlM Wide Gatewa
20260927224419WIK>APWL2K,TCPNK-1,qAR,AE7AF:;71044z W82. a4acket G
20260927225116WIK>AqAS,WLNK-1,qAR,AE7AF:;KI448. NW08342. 45.070MHznlink Packetteway
20260928000813WIK>APWKTPP,A,qAR,AE7AF:;VA3OG-10 *2808z4341. NW947. Wa145.030MHz Winlk VARA Fde Gat
20260928001841WIK>APW2CPIP,S,WLN,qAR,AE7AF:;W6JCL-10 *281218z6. 807Wa223.540ilink Packet Gatewa
20260928003506WIK>APWL2K,TCPIS,W,qAR,AE7AF:;F10 35z00114455MHz Winlink PaGteway
20260928010352WIK>APWL2K,TCPIP,qAS,AE7AF:;NA3M0*2801QUAIL>APOT30,WIDE2-2,qAR,VAILMT:T#087,126,029,073,083,048,00000000
20260928010721WIK>APWL2qAS,WLNK-1,qAR,AE7AF:;PY2Z*280107z23SW0455145.57Winlinket Ga
20260928013545WIK>APWL2K,TCP-1,qAR,AE7AF:;H05z4W0074.4.950MHz VARA Fe Gatewa
20260928021617WIK>APWL2K,TCPIP*,qAS,AE7AF:;W4RGSTRY>APZ100,TCPIP*,qAC,T2RDU::WXNOW :ping{816
20260928022125WIK>APWL2K,TCPIP*,qAS,AE7AF:;W7YAM-10 *280206.2307441Hz n Packet Gateway
20260928025412WIK>APK1,qAR,AE7AF:;K-11 025408. NW11747. Wa144.970MHz Winlink Pet Gateway
20260928032952WIK>APWL2K,TCPIP*,qAS,AE7AF:;*28032. SW1702AD1CT>APGRWO,TCPIP*,qC:!:=4f/014.8