A total of 292 recevied packets have been found for station/object EA6AMR-10 between 1789521625 and 1789780825.
Request took 0.009 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 292 packets.
[>] 1789780141: EA6AMR-10>APLRG1,TCPIP*,qAC,T2SYDNEY:=L:OnnO,Lg_ !G.../...g...t067h83b10197LoRa APRS 433.775 Mhz Santa Ponsa Batt=4.30V
[>] 1789779240: EA6AMR-10>APLRG1,TCPIP*,qAC,T2SYDNEY:=L:OnnO,Lg_ !G.../...g...t067h83b10197LoRa APRS 433.775 Mhz Santa Ponsa Batt=4.30V
[>] 1789778340: EA6AMR-10>APLRG1,TCPIP*,qAC,T2SYDNEY:=L:OnnO,Lg_ !G.../...g...t067h83b10197LoRa APRS 433.775 Mhz Santa Ponsa Batt=4.30V
[>] 1789777440: EA6AMR-10>APLRG1,TCPIP*,qAC,T2SYDNEY:=L:OnnO,Lg_ !G.../...g...t067h83b10196LoRa APRS 433.775 Mhz Santa Ponsa Batt=4.30V
[>] 1789776540: EA6AMR-10>APLRG1,TCPIP*,qAC,T2SYDNEY:=L:OnnO,Lg_ !G.../...g...t067h83b10197LoRa APRS 433.775 Mhz Santa Ponsa Batt=4.30V
[>] 1789775640: EA6AMR-10>APLRG1,TCPIP*,qAC,T2SYDNEY:=L:OnnO,Lg_ !G.../...g...t067h82b10198LoRa APRS 433.775 Mhz Santa Ponsa Batt=4.31V
[>] 1789774739: EA6AMR-10>APLRG1,TCPIP*,qAC,T2SYDNEY:=L:OnnO,Lg_ !G.../...g...t067h83b10199LoRa APRS 433.775 Mhz Santa Ponsa Batt=4.31V
[>] 1789773839: EA6AMR-10>APLRG1,TCPIP*,qAC,T2SYDNEY:=L:OnnO,Lg_ !G.../...g...t068h82b10200LoRa APRS 433.775 Mhz Santa Ponsa Batt=4.31V
[>] 1789772939: EA6AMR-10>APLRG1,TCPIP*,qAC,T2SYDNEY:=L:OnnO,Lg_ !G.../...g...t068h82b10201LoRa APRS 433.775 Mhz Santa Ponsa Batt=4.29V
[>] 1789772039: EA6AMR-10>APLRG1,TCPIP*,qAC,T2SYDNEY:=L:OnnO,Lg_ !G.../...g...t068h82b10201LoRa APRS 433.775 Mhz Santa Ponsa Batt=4.30V
[>] 1789771138: EA6AMR-10>APLRG1,TCPIP*,qAC,T2SYDNEY:=L:OnnO,Lg_ !G.../...g...t068h82b10200LoRa APRS 433.775 Mhz Santa Ponsa Batt=4.29V
[>] 1789770238: EA6AMR-10>APLRG1,TCPIP*,qAC,T2SYDNEY:=L:OnnO,Lg_ !G.../...g...t068h82b10199LoRa APRS 433.775 Mhz Santa Ponsa Batt=4.30V
[>] 1789769338: EA6AMR-10>APLRG1,TCPIP*,qAC,T2SYDNEY:=L:OnnO,Lg_ !G.../...g...t068h82b10201LoRa APRS 433.775 Mhz Santa Ponsa Batt=4.31V
[>] 1789768438: EA6AMR-10>APLRG1,TCPIP*,qAC,T2SYDNEY:=L:OnnO,Lg_ !G.../...g...t069h82b10198LoRa APRS 433.775 Mhz Santa Ponsa Batt=4.30V
[>] 1789767537: EA6AMR-10>APLRG1,TCPIP*,qAC,T2SYDNEY:=L:OnnO,Lg_ !G.../...g...t069h82b10196LoRa APRS 433.775 Mhz Santa Ponsa Batt=4.32V
[>] 1789766637: EA6AMR-10>APLRG1,TCPIP*,qAC,T2SYDNEY:=L:OnnO,Lg_ !G.../...g...t069h82b10195LoRa APRS 433.775 Mhz Santa Ponsa Batt=4.31V
[>] 1789765737: EA6AMR-10>APLRG1,TCPIP*,qAC,T2SYDNEY:=L:OnnO,Lg_ !G.../...g...t069h82b10194LoRa APRS 433.775 Mhz Santa Ponsa Batt=4.31V
[>] 1789764837: EA6AMR-10>APLRG1,TCPIP*,qAC,T2SYDNEY:=L:OnnO,Lg_ !G.../...g...t069h82b10194LoRa APRS 433.775 Mhz Santa Ponsa Batt=4.29V
[>] 1789763936: EA6AMR-10>APLRG1,TCPIP*,qAC,T2SYDNEY:=L:OnnO,Lg_ !G.../...g...t069h82b10194LoRa APRS 433.775 Mhz Santa Ponsa Batt=4.29V
[>] 1789763036: EA6AMR-10>APLRG1,TCPIP*,qAC,T2SYDNEY:=L:OnnO,Lg_ !G.../...g...t070h82b10193LoRa APRS 433.775 Mhz Santa Ponsa Batt=4.30V
[>] 1789761236: EA6AMR-10>APLRG1,TCPIP*,qAC,T2ROMANIA:=L:OnnO,Lg_ !G.../...g...t070h81b10189LoRa APRS 433.775 Mhz Santa Ponsa Batt=4.30V
[>] 1789760335: EA6AMR-10>APLRG1,TCPIP*,qAC,T2ROMANIA:=L:OnnO,Lg_ !G.../...g...t070h81b10186LoRa APRS 433.775 Mhz Santa Ponsa Batt=4.29V
[>] 1789759435: EA6AMR-10>APLRG1,TCPIP*,qAC,T2ROMANIA:=L:OnnO,Lg_ !G.../...g...t071h81b10183LoRa APRS 433.775 Mhz Santa Ponsa Batt=4.32V
[>] 1789758540: EA6AMR-10>APLRG1,TCPIP*,qAC,T2PERTH:=L:OnnO,Lg_ !G.../...g...t071h81b10182LoRa APRS 433.775 Mhz Santa Ponsa Batt=4.30V
[>] 1789757639: EA6AMR-10>APLRG1,TCPIP*,qAC,T2PERTH:=L:OnnO,Lg_ !G.../...g...t072h81b10180LoRa APRS 433.775 Mhz Santa Ponsa Batt=4.31V
* 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.