A total of 72 recevied packets have been found for station/object EA3IBE-10 between 1764982403 and 1765241603.
Request took 0.002 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 72 packets.
[>] 1765240855: EA3IBE-10>APLRG1,TCPIP*,qAC,T2BELGIUM:!L9I^?O$a]_ G.../...g...t046h00b10190LoRa APRS Caldes de Montbui de l'EA3IBE, 73!
[>] 1765238455: EA3IBE-10>APLRG1,TCPIP*,qAC,T2BELGIUM:!L9I^?O$a]_ G.../...g...t045h00b10194LoRa APRS Caldes de Montbui de l'EA3IBE, 73!
[>] 1765149652: EA3IBE-10>APLRG1,TCPIP*,qAC,T2BELGIUM:!L9I^?O$a]_ G.../...g...t050h00b10193LoRa APRS Caldes de Montbui de l'EA3IBE, 73!
[>] 1765147251: EA3IBE-10>APLRG1,TCPIP*,qAC,T2BELGIUM:!L9I^?O$a]_ G.../...g...t050h00b10192LoRa APRS Caldes de Montbui de l'EA3IBE, 73!
[>] 1765144851: EA3IBE-10>APLRG1,TCPIP*,qAC,T2BELGIUM:!L9I^?O$a]_ G.../...g...t051h00b10190LoRa APRS Caldes de Montbui de l'EA3IBE, 73!
[>] 1765142451: EA3IBE-10>APLRG1,TCPIP*,qAC,T2BELGIUM:!L9I^?O$a]_ G.../...g...t052h00b10187LoRa APRS Caldes de Montbui de l'EA3IBE, 73!
[>] 1765140051: EA3IBE-10>APLRG1,TCPIP*,qAC,T2BELGIUM:!L9I^?O$a]_ G.../...g...t052h00b10187LoRa APRS Caldes de Montbui de l'EA3IBE, 73!
[>] 1765137651: EA3IBE-10>APLRG1,TCPIP*,qAC,T2BELGIUM:!L9I^?O$a]_ G.../...g...t052h00b10188LoRa APRS Caldes de Montbui de l'EA3IBE, 73!
[>] 1765135251: EA3IBE-10>APLRG1,TCPIP*,qAC,T2BELGIUM:!L9I^?O$a]_ G.../...g...t052h00b10186LoRa APRS Caldes de Montbui de l'EA3IBE, 73!
[>] 1765132851: EA3IBE-10>APLRG1,TCPIP*,qAC,T2BELGIUM:!L9I^?O$a]_ G.../...g...t054h00b10181LoRa APRS Caldes de Montbui de l'EA3IBE, 73!
[>] 1765130451: EA3IBE-10>APLRG1,TCPIP*,qAC,T2BELGIUM:!L9I^?O$a]_ G.../...g...t055h00b10180LoRa APRS Caldes de Montbui de l'EA3IBE, 73!
[>] 1765128051: EA3IBE-10>APLRG1,TCPIP*,qAC,T2BELGIUM:!L9I^?O$a]_ G.../...g...t057h00b10178LoRa APRS Caldes de Montbui de l'EA3IBE, 73!
[>] 1765125651: EA3IBE-10>APLRG1,TCPIP*,qAC,T2BELGIUM:!L9I^?O$a]_ G.../...g...t058h00b10172LoRa APRS Caldes de Montbui de l'EA3IBE, 73!
[>] 1765123250: EA3IBE-10>APLRG1,TCPIP*,qAC,T2BELGIUM:!L9I^?O$a]_ G.../...g...t065h80b10166LoRa APRS Caldes de Montbui de l'EA3IBE, 73!
[>] 1765120850: EA3IBE-10>APLRG1,TCPIP*,qAC,T2BELGIUM:!L9I^?O$a]_ G.../...g...t064h83b10163LoRa APRS Caldes de Montbui de l'EA3IBE, 73!
[>] 1765118450: EA3IBE-10>APLRG1,TCPIP*,qAC,T2BELGIUM:!L9I^?O$a]_ G.../...g...t073h53b10161LoRa APRS Caldes de Montbui de l'EA3IBE, 73!
[>] 1765116050: EA3IBE-10>APLRG1,TCPIP*,qAC,T2BELGIUM:!L9I^?O$a]_ G.../...g...t079h44b10161LoRa APRS Caldes de Montbui de l'EA3IBE, 73!
[>] 1765113650: EA3IBE-10>APLRG1,TCPIP*,qAC,T2BELGIUM:!L9I^?O$a]_ G.../...g...t074h53b10163LoRa APRS Caldes de Montbui de l'EA3IBE, 73!
[>] 1765111250: EA3IBE-10>APLRG1,TCPIP*,qAC,T2BELGIUM:!L9I^?O$a]_ G.../...g...t079h45b10167LoRa APRS Caldes de Montbui de l'EA3IBE, 73!
[>] 1765108850: EA3IBE-10>APLRG1,TCPIP*,qAC,T2BELGIUM:!L9I^?O$a]_ G.../...g...t075h50b10171LoRa APRS Caldes de Montbui de l'EA3IBE, 73!
[>] 1765106450: EA3IBE-10>APLRG1,TCPIP*,qAC,T2BELGIUM:!L9I^?O$a]_ G.../...g...t077h48b10173LoRa APRS Caldes de Montbui de l'EA3IBE, 73!
[>] 1765104050: EA3IBE-10>APLRG1,TCPIP*,qAC,T2BELGIUM:!L9I^?O$a]_ G.../...g...t064h78b10178LoRa APRS Caldes de Montbui de l'EA3IBE, 73!
[>] 1765101650: EA3IBE-10>APLRG1,TCPIP*,qAC,T2BELGIUM:!L9I^?O$a]_ G.../...g...t065h75b10183LoRa APRS Caldes de Montbui de l'EA3IBE, 73!
[>] 1765099250: EA3IBE-10>APLRG1,TCPIP*,qAC,T2BELGIUM:!L9I^?O$a]_ G.../...g...t078h42b10183LoRa APRS Caldes de Montbui de l'EA3IBE, 73!
[>] 1765096849: EA3IBE-10>APLRG1,TCPIP*,qAC,T2BELGIUM:!L9I^?O$a]_ G.../...g...t058h93b10177LoRa APRS Caldes de Montbui de l'EA3IBE, 73!
* 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.