A total of 78 recevied packets have been found for station/object XE2AD-5 between 1793562086 and 1793821286.
Request took 0.003 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 78 packets.
[>] 1793818386: XE2AD-5>APLRG1,TCPIP*,qAC,T2VAN:=LCFjv4[cS_ !G.../...g...t075h43b08085LoRa APRS IGate and WX at 433.775MHz Batt=4.24V
[>] 1793815085: XE2AD-5>APLRG1,TCPIP*,qAC,T2VAN:=LCFjv4[cS_ !G.../...g...t073h45b08095LoRa APRS IGate and WX at 433.775MHz Batt=4.24V
[>] 1793811785: XE2AD-5>APLRG1,TCPIP*,qAC,T2VAN:=LCFjv4[cS_ !G.../...g...t072h45b08103LoRa APRS IGate and WX at 433.775MHz Batt=4.25V
[>] 1793808485: XE2AD-5>APLRG1,TCPIP*,qAC,T2VAN:=LCFjv4[cS_ !G.../...g...t072h45b08105LoRa APRS IGate and WX at 433.775MHz Batt=4.24V
[>] 1793805185: XE2AD-5>APLRG1,TCPIP*,qAC,T2VAN:=LCFjv4[cS_ !G.../...g...t072h44b08101LoRa APRS IGate and WX at 433.775MHz Batt=4.24V
[>] 1793801885: XE2AD-5>APLRG1,TCPIP*,qAC,T2VAN:=LCFjv4[cS_ !G.../...g...t072h42b08099LoRa APRS IGate and WX at 433.775MHz Batt=4.24V
[>] 1793798585: XE2AD-5>APLRG1,TCPIP*,qAC,T2VAN:=LCFjv4[cS_ !G.../...g...t072h42b08093LoRa APRS IGate and WX at 433.775MHz Batt=4.24V
[>] 1793795284: XE2AD-5>APLRG1,TCPIP*,qAC,T2VAN:=LCFjv4[cS_ !G.../...g...t073h45b08089LoRa APRS IGate and WX at 433.775MHz Batt=4.25V
[>] 1793791984: XE2AD-5>APLRG1,TCPIP*,qAC,T2VAN:=LCFjv4[cS_ !G.../...g...t074h44b08085LoRa APRS IGate and WX at 433.775MHz Batt=4.24V
[>] 1793788684: XE2AD-5>APLRG1,TCPIP*,qAC,T2VAN:=LCFjv4[cS_ !G.../...g...t074h44b08082LoRa APRS IGate and WX at 433.775MHz Batt=4.24V
[>] 1793785384: XE2AD-5>APLRG1,TCPIP*,qAC,T2VAN:=LCFjv4[cS_ !G.../...g...t075h43b08079LoRa APRS IGate and WX at 433.775MHz Batt=4.24V
[>] 1793782084: XE2AD-5>APLRG1,TCPIP*,qAC,T2VAN:=LCFjv4[cS_ !G.../...g...t075h43b08080LoRa APRS IGate and WX at 433.775MHz Batt=4.25V
[>] 1793778784: XE2AD-5>APLRG1,TCPIP*,qAC,T2VAN:=LCFjv4[cS_ !G.../...g...t076h42b08081LoRa APRS IGate and WX at 433.775MHz Batt=4.25V
[>] 1793775483: XE2AD-5>APLRG1,TCPIP*,qAC,T2VAN:=LCFjv4[cS_ !G.../...g...t076h42b08082LoRa APRS IGate and WX at 433.775MHz Batt=4.25V
[>] 1793772183: XE2AD-5>APLRG1,TCPIP*,qAC,T2VAN:=LCFjv4[cS_ !G.../...g...t077h41b08083LoRa APRS IGate and WX at 433.775MHz Batt=4.24V
[>] 1793768883: XE2AD-5>APLRG1,TCPIP*,qAC,T2VAN:=LCFjv4[cS_ !G.../...g...t077h39b08086LoRa APRS IGate and WX at 433.775MHz Batt=4.23V
[>] 1793765583: XE2AD-5>APLRG1,TCPIP*,qAC,T2VAN:=LCFjv4[cS_ !G.../...g...t078h37b08084LoRa APRS IGate and WX at 433.775MHz Batt=4.23V
[>] 1793762283: XE2AD-5>APLRG1,TCPIP*,qAC,T2VAN:=LCFjv4[cS_ !G.../...g...t079h39b08080LoRa APRS IGate and WX at 433.775MHz Batt=4.25V
[>] 1793758983: XE2AD-5>APLRG1,TCPIP*,qAC,T2VAN:=LCFjv4[cS_ !G.../...g...t079h40b08073LoRa APRS IGate and WX at 433.775MHz Batt=4.24V
[>] 1793755682: XE2AD-5>APLRG1,TCPIP*,qAC,T2VAN:=LCFjv4[cS_ !G.../...g...t079h40b08069LoRa APRS IGate and WX at 433.775MHz Batt=4.23V
[>] 1793752382: XE2AD-5>APLRG1,TCPIP*,qAC,T2VAN:=LCFjv4[cS_ !G.../...g...t079h38b08064LoRa APRS IGate and WX at 433.775MHz Batt=4.23V
[>] 1793749082: XE2AD-5>APLRG1,TCPIP*,qAC,T2VAN:=LCFjv4[cS_ !G.../...g...t079h39b08060LoRa APRS IGate and WX at 433.775MHz Batt=4.25V
[>] 1793745782: XE2AD-5>APLRG1,TCPIP*,qAC,T2VAN:=LCFjv4[cS_ !G.../...g...t079h37b08059LoRa APRS IGate and WX at 433.775MHz Batt=4.23V
[>] 1793742482: XE2AD-5>APLRG1,TCPIP*,qAC,T2VAN:=LCFjv4[cS_ !G.../...g...t078h38b08061LoRa APRS IGate and WX at 433.775MHz Batt=4.25V
[>] 1793739182: XE2AD-5>APLRG1,TCPIP*,qAC,T2VAN:=LCFjv4[cS_ !G.../...g...t077h38b08065LoRa APRS IGate and WX at 433.775MHz Batt=4.25V
* 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.