A total of 244 recevied packets have been found for station/object PY2TK-5 between 1766111077 and 1766370277.
Request took 0.005 seconds to find in our database.
Packet history is available for up to 3 days. Sign up for a free account to view 30 up to days history. Use [>] to decode with our packet packet decoder tool.
Displaying 1 - 25 of 244 packets.
[>] 1766369339: PY2TK-5>APDR16,TCPIP*,qAC,T2LAUSITZ:=2328.33S/04654.03W(/A=002475 Max
[>] 1766368139: PY2TK-5>APDR16,TCPIP*,qAC,T2LAUSITZ:=2328.33S/04654.03W(/A=002482 Max
[>] 1766366939: PY2TK-5>APDR16,TCPIP*,qAC,T2LAUSITZ:=2328.33S/04654.03W(/A=002486 Max
[>] 1766365739: PY2TK-5>APDR16,TCPIP*,qAC,T2FINLAND:=2328.32S/04654.02W(012/002/A=002502 Max
[>] 1766365401: PY2TK-5>APDR16,TCPIP*,qAC,T2FINLAND:=2328.33S/04654.02W(266/000/A=002501 Max
[>] 1766364675: PY2TK-5>APDR16,TCPIP*,qAC,T2FINLAND:=2328.33S/04654.02W(/A=002504 Max
[>] 1766363679: PY2TK-5>APDR16,TCPIP*,qAC,T2LAUSITZ:=2328.34S/04654.02W(322/011/A=002503 Max
[>] 1766363582: PY2TK-5>APDR16,TCPIP*,qAC,T2LAUSITZ:=2328.60S/04653.96W(349/009/A=002522 Max
[>] 1766363564: PY2TK-5>APDR16,TCPIP*,qAC,T2LAUSITZ:=2328.65S/04653.95W(312/009/A=002507 Max
[>] 1766363435: PY2TK-5>APDR16,TCPIP*,qAC,T2HUN:=2328.56S/04653.79W(178/003/A=002422 Max
[>] 1766363420: PY2TK-5>APDR16,TCPIP*,qAC,T2HUN:=2328.55S/04653.80W(037/011/A=002414 Max
[>] 1766363397: PY2TK-5>APDR16,TCPIP*,qAC,T2HUN:=2328.62S/04653.80W(355/012/A=002417 Max
[>] 1766363382: PY2TK-5>APDR16,TCPIP*,qAC,T2HUN:=2328.65S/04653.83W(051/009/A=002409 Max
[>] 1766362794: PY2TK-5>APDR16,TCPIP*,qAC,T2LAUSITZ:=2329.34S/04653.40W(295/012/A=002491 Max
[>] 1766362771: PY2TK-5>APDR16,TCPIP*,qAC,T2LAUSITZ:=2329.32S/04653.36W(246/010/A=002460 Max
[>] 1766362716: PY2TK-5>APDR16,TCPIP*,qAC,T2LAUSITZ:=2329.41S/04653.14W(292/018/A=002423 Max
[>] 1766362702: PY2TK-5>APDR16,TCPIP*,qAC,T2LAUSITZ:=2329.44S/04653.08W(259/006/A=002443 Max
[>] 1766362661: PY2TK-5>APDR16,TCPIP*,qAC,T2LAUSITZ:=2329.29S/04652.99W(208/012/A=002467 Max
[>] 1766362646: PY2TK-5>APDR16,TCPIP*,qAC,T2LAUSITZ:=2329.29S/04652.95W(258/013/A=002455 Max
[>] 1766362631: PY2TK-5>APDR16,TCPIP*,qAC,T2LAUSITZ:=2329.31S/04652.89W(347/010/A=002444 Max
[>] 1766362611: PY2TK-5>APDR16,TCPIP*,qAC,T2LAUSITZ:=2329.37S/04652.92W(026/015/A=002455 Max
[>] 1766362596: PY2TK-5>APDR16,TCPIP*,qAC,T2LAUSITZ:=2329.45S/04652.94W(330/018/A=002495 Max
[>] 1766362579: PY2TK-5>APDR16,TCPIP*,qAC,T2LAUSITZ:=2329.51S/04652.87W(304/019/A=002527 Max
[>] 1766362564: PY2TK-5>APDR16,TCPIP*,qAC,T2LAUSITZ:=2329.57S/04652.84W(327/014/A=002522 Max
[>] 1766362549: PY2TK-5>APDR16,TCPIP*,qAC,T2LAUSITZ:=2329.58S/04652.76W(300/020/A=002483 Max
* If you compare the raw packets with similar data from other websites it may differ (especially the path), the reason is that we are not collecting packets from the same APRS-IS servers. Each APRS-IS server performes duplicate filtering, and which packet that is considered to be a duplicate may differ depending on which APRS-IS server you receive your data from.
Link directly to this page:
After more than a month of development, the fourth major update of the site has launched! This update is unique from the past updates as it brings only a few new features but more than 50 bug fixes.
While short on new features, it includes the very first top-down re-write of the web app code since it was first created. One new feature that should be useful is "Track My Location".
Track My Location periodically updates a special marker shown on the map with the location reported by the web browser. The location icon in the top right corner will turn red to indicate that your location is being tracked. For registered guests, this feature can be set to turn on automatically when visiting the site.
This release brings a total of 6 new map overlaps to OpenStreetMaps to help with that. This includes hiking and cycling trails, mountain bike trails, ski slopes, even railroads and Sea maps! These crowd-sourced map overlays are available for Leaflet (OpenStreetMaps) only.
Read about all of the changes in the what's new section.
As with any major software update, there will likely be bugs that haven't been caught in testing. Please contact us to share feedback or report problems.