A total of 288 recevied packets have been found for station/object EA6AMR-10 between 1789558622 and 1789817822.
Request took 0.013 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 288 packets.
[>] 1789817044: EA6AMR-10>APLRG1,TCPIP*,qAC,T2CHILE:=L:OnnO,Lg_ !G.../...g...t096h68b10218LoRa APRS 433.775 Mhz Santa Ponsa Batt=4.30V
[>] 1789816144: EA6AMR-10>APLRG1,TCPIP*,qAC,T2CHILE:=L:OnnO,Lg_ !G.../...g...t096h68b10220LoRa APRS 433.775 Mhz Santa Ponsa Batt=4.30V
[>] 1789815243: EA6AMR-10>APLRG1,TCPIP*,qAC,T2CHILE:=L:OnnO,Lg_ !G.../...g...t095h68b10220LoRa APRS 433.775 Mhz Santa Ponsa Batt=4.30V
[>] 1789814343: EA6AMR-10>APLRG1,TCPIP*,qAC,T2CHILE:=L:OnnO,Lg_ !G.../...g...t096h68b10222LoRa APRS 433.775 Mhz Santa Ponsa Batt=4.29V
[>] 1789813443: EA6AMR-10>APLRG1,TCPIP*,qAC,T2CHILE:=L:OnnO,Lg_ !G.../...g...t096h69b10222LoRa APRS 433.775 Mhz Santa Ponsa Batt=4.30V
[>] 1789812543: EA6AMR-10>APLRG1,TCPIP*,qAC,T2CHILE:=L:OnnO,Lg_ !G.../...g...t097h68b10222LoRa APRS 433.775 Mhz Santa Ponsa Batt=4.30V
[>] 1789811643: EA6AMR-10>APLRG1,TCPIP*,qAC,T2CHILE:=L:OnnO,Lg_ !G.../...g...t095h71b10222LoRa APRS 433.775 Mhz Santa Ponsa Batt=4.28V
[>] 1789810742: EA6AMR-10>APLRG1,TCPIP*,qAC,T2CHILE:=L:OnnO,Lg_ !G.../...g...t094h71b10223LoRa APRS 433.775 Mhz Santa Ponsa Batt=4.30V
[>] 1789809842: EA6AMR-10>APLRG1,TCPIP*,qAC,T2CHILE:=L:OnnO,Lg_ !G.../...g...t094h70b10222LoRa APRS 433.775 Mhz Santa Ponsa Batt=4.30V
[>] 1789808942: EA6AMR-10>APLRG1,TCPIP*,qAC,T2CHILE:=L:OnnO,Lg_ !G.../...g...t092h69b10221LoRa APRS 433.775 Mhz Santa Ponsa Batt=4.31V
[>] 1789808042: EA6AMR-10>APLRG1,TCPIP*,qAC,T2CHILE:=L:OnnO,Lg_ !G.../...g...t092h68b10219LoRa APRS 433.775 Mhz Santa Ponsa Batt=4.29V
[>] 1789807141: EA6AMR-10>APLRG1,TCPIP*,qAC,T2CHILE:=L:OnnO,Lg_ !G.../...g...t092h65b10219LoRa APRS 433.775 Mhz Santa Ponsa Batt=4.31V
[>] 1789806241: EA6AMR-10>APLRG1,TCPIP*,qAC,T2CHILE:=L:OnnO,Lg_ !G.../...g...t090h65b10217LoRa APRS 433.775 Mhz Santa Ponsa Batt=4.30V
[>] 1789805341: EA6AMR-10>APLRG1,TCPIP*,qAC,T2CHILE:=L:OnnO,Lg_ !G.../...g...t090h62b10216LoRa APRS 433.775 Mhz Santa Ponsa Batt=4.31V
[>] 1789804441: EA6AMR-10>APLRG1,TCPIP*,qAC,T2CHILE:=L:OnnO,Lg_ !G.../...g...t088h63b10214LoRa APRS 433.775 Mhz Santa Ponsa Batt=4.32V
[>] 1789803541: EA6AMR-10>APLRG1,TCPIP*,qAC,T2CHILE:=L:OnnO,Lg_ !G.../...g...t084h66b10213LoRa APRS 433.775 Mhz Santa Ponsa Batt=4.32V
[>] 1789802640: EA6AMR-10>APLRG1,TCPIP*,qAC,T2CHILE:=L:OnnO,Lg_ !G.../...g...t081h68b10213LoRa APRS 433.775 Mhz Santa Ponsa Batt=4.31V
[>] 1789801742: EA6AMR-10>APLRG1,TCPIP*,qAC,T2CHILE:=L:OnnO,Lg_ !G.../...g...t076h73b10211LoRa APRS 433.775 Mhz Santa Ponsa Batt=4.30V
[>] 1789800841: EA6AMR-10>APLRG1,TCPIP*,qAC,T2CHILE:=L:OnnO,Lg_ !G.../...g...t074h75b10210LoRa APRS 433.775 Mhz Santa Ponsa Batt=4.30V
[>] 1789799941: EA6AMR-10>APLRG1,TCPIP*,qAC,T2CHILE:=L:OnnO,Lg_ !G.../...g...t071h78b10209LoRa APRS 433.775 Mhz Santa Ponsa Batt=4.32V
[>] 1789799041: EA6AMR-10>APLRG1,TCPIP*,qAC,T2CHILE:=L:OnnO,Lg_ !G.../...g...t069h80b10207LoRa APRS 433.775 Mhz Santa Ponsa Batt=4.31V
[>] 1789798141: EA6AMR-10>APLRG1,TCPIP*,qAC,T2CHILE:=L:OnnO,Lg_ !G.../...g...t067h82b10206LoRa APRS 433.775 Mhz Santa Ponsa Batt=4.31V
[>] 1789797240: EA6AMR-10>APLRG1,TCPIP*,qAC,T2CHILE:=L:OnnO,Lg_ !G.../...g...t065h83b10204LoRa APRS 433.775 Mhz Santa Ponsa Batt=4.30V
[>] 1789796340: EA6AMR-10>APLRG1,TCPIP*,qAC,T2CHILE:=L:OnnO,Lg_ !G.../...g...t065h83b10201LoRa APRS 433.775 Mhz Santa Ponsa Batt=4.32V
[>] 1789795440: EA6AMR-10>APLRG1,TCPIP*,qAC,T2CHILE:=L:OnnO,Lg_ !G.../...g...t065h83b10201LoRa APRS 433.775 Mhz Santa Ponsa Batt=4.30V
* 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.