Back to the log
Aircraft
F-HBMR
Regular
The station's story
Address not received since 18 Jan 2024. The marker states the absence, it does not say why.
- Cumulative contact time
- 192 h
- Distinct days
- 299
- Highest captured altitude
- 50,500 ft
- Discovery rank
- #14,422 of 57,065
- Longest contact
- 1 h 22 min
Observed callsigns
VLJ (392 contacts, 2016-2023) · DBT (18 contacts, 2023)
Operator as per the registry of 29 Jul 2026; observed callsigns are the freshest measurement.
Visits
| Callsign | Route | First contact | Last contact | Altitude at end of contact | Positions |
|---|---|---|---|---|---|
| VLJ061L | route not resolved | 22 Feb 2017, 21:0722 Feb 2017 | 22 Feb 2017, 21:25 | 30,750 ft | no position received |
| VLJ053P | route not resolved | 20 Feb 2017, 18:3620 Feb 2017 | 20 Feb 2017, 19:59 | 24,000 ft | no position received |
| VLJ053M | route not resolved | 20 Feb 2017, 09:1020 Feb 2017 | 20 Feb 2017, 09:52 | 30,950 ft | no position received |
| VLJ053L | route not resolved | 20 Feb 2017, 08:0520 Feb 2017 | 20 Feb 2017, 08:34 | 1,025 ft | no position received |
| VLJ081M | route not resolved | 17 Feb 2017, 17:5917 Feb 2017 | 17 Feb 2017, 18:33 | 31,950 ft | no position received |
| VLJ081L | route not resolved | 17 Feb 2017, 09:5517 Feb 2017 | 17 Feb 2017, 10:15 | 31,750 ft | no position received |
| VLJ018L | route not resolved | 3 Feb 2017, 13:063 Feb 2017 | 3 Feb 2017, 13:17 | 25,325 ft | no position received |
| VLJ050Q | route not resolved | 2 Feb 2017, 19:032 Feb 2017 | 2 Feb 2017, 19:26 | 7,975 ft | no position received |
| VLJ050P | route not resolved | 2 Feb 2017, 17:322 Feb 2017 | 2 Feb 2017, 18:18 | 1,500 ft | no position received |
| VLJ050N | route not resolved | 2 Feb 2017, 09:402 Feb 2017 | 2 Feb 2017, 10:28 | 33,975 ft | no position received |
| VLJ050M | route not resolved | 2 Feb 2017, 08:372 Feb 2017 | 2 Feb 2017, 09:01 | 1,375 ft | no position received |
| VLJ024P | route not resolved | 24 Jan 2017, 19:3524 Jan 2017 | 24 Jan 2017, 20:08 | 26,100 ft | no position received |
| VLJ024L | route not resolved | 24 Jan 2017, 07:0224 Jan 2017 | 24 Jan 2017, 07:22 | 23,600 ft | no position received |
| VLJ027N | route not resolved | 17 Jan 2017, 12:2117 Jan 2017 | 17 Jan 2017, 12:44 | 31,950 ft | no position received |
| VLJ027M | route not resolved | 15 Jan 2017, 13:1715 Jan 2017 | 15 Jan 2017, 13:36 | 7,550 ft | no position received |
| VLJ603M | route not resolved | 15 Dec 2016, 20:4015 Dec 2016 | 15 Dec 2016, 21:08 | 24,100 ft | no position received |
| VLJ603L | route not resolved | 14 Dec 2016, 15:3514 Dec 2016 | 14 Dec 2016, 16:02 | 38,975 ft | no position received |
| VLJ589M | route not resolved | 13 Dec 2016, 21:4613 Dec 2016 | 13 Dec 2016, 22:05 | 34,975 ft | no position received |
| VLJ589L | route not resolved | 13 Dec 2016, 20:1313 Dec 2016 | 13 Dec 2016, 20:32 | 9,550 ft | no position received |
| VLJ597M | route not resolved | 10 Dec 2016, 12:0010 Dec 2016 | 10 Dec 2016, 12:33 | 24,525 ft | no position received |
| VLJ597L | route not resolved | 9 Dec 2016, 11:449 Dec 2016 | 9 Dec 2016, 12:06 | 5,775 ft | no position received |
| VLJ586M | route not resolved | 7 Dec 2016, 16:407 Dec 2016 | 7 Dec 2016, 17:12 | 27,950 ft | no position received |
| VLJ586L | route not resolved | 7 Dec 2016, 09:107 Dec 2016 | 7 Dec 2016, 09:31 | 32,975 ft | no position received |
| VLJ593L | route not resolved | 5 Dec 2016, 17:085 Dec 2016 | 5 Dec 2016, 17:33 | 21,975 ft | no position received |
| VLJ593L | route not resolved | 5 Dec 2016, 16:125 Dec 2016 | 5 Dec 2016, 16:22 | 10,650 ft | no position received |
