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 |
|---|---|---|---|---|---|
| VLJ153N | route not resolved | 11 May 2017, 14:3711 May 2017 | 11 May 2017, 15:16 | 34,975 ft | no position received |
| VLJ153M | route not resolved | 8 May 2017, 19:428 May 2017 | 8 May 2017, 20:10 | 25,000 ft | no position received |
| VLJ153L | route not resolved | 8 May 2017, 16:558 May 2017 | 8 May 2017, 17:28 | 32,925 ft | no position received |
| VLJ179P | route not resolved | 22 Apr 2017, 06:5422 Apr 2017 | 22 Apr 2017, 07:29 | 28,250 ft | no position received |
| VLJ179L | route not resolved | 21 Apr 2017, 07:4921 Apr 2017 | 21 Apr 2017, 08:08 | 32,975 ft | no position received |
| VLJ079Q | route not resolved | 20 Apr 2017, 12:4120 Apr 2017 | 20 Apr 2017, 13:05 | 35,000 ft | no position received |
| VLJ173N | route not resolved | 18 Apr 2017, 18:5218 Apr 2017 | 18 Apr 2017, 19:12 | 28,000 ft | no position received |
| VLJ173M | route not resolved | 18 Apr 2017, 07:1418 Apr 2017 | 18 Apr 2017, 07:31 | 21,975 ft | no position received |
| VLJ126P | route not resolved | 16 Apr 2017, 15:2716 Apr 2017 | 16 Apr 2017, 15:53 | 21,975 ft | no position received |
| VLJ126N | route not resolved | 16 Apr 2017, 14:3516 Apr 2017 | 16 Apr 2017, 14:59 | 6,150 ft | no position received |
| VLJ135Q | route not resolved | 15 Apr 2017, 17:5815 Apr 2017 | 15 Apr 2017, 18:37 | 35,975 ft | no position received |
| VLJ135P | route not resolved | 15 Apr 2017, 13:3115 Apr 2017 | 15 Apr 2017, 13:52 | 34,975 ft | no position received |
| VLJ168M | route not resolved | 12 Apr 2017, 10:0912 Apr 2017 | 12 Apr 2017, 10:19 | 19,475 ft | no position received |
| VLJ168L | route not resolved | 12 Apr 2017, 07:3612 Apr 2017 | 12 Apr 2017, 07:54 | 31,000 ft | no position received |
| VLJ091M | route not resolved | 6 Mar 2017, 00:366 Mar 2017 | 6 Mar 2017, 01:12 | 33,050 ft | no position received |
| VLJ091L | route not resolved | 5 Mar 2017, 13:535 Mar 2017 | 5 Mar 2017, 14:13 | 29,050 ft | no position received |
| VLJ072N | route not resolved | 4 Mar 2017, 18:104 Mar 2017 | 4 Mar 2017, 18:24 | 38,000 ft | no position received |
| VLJ072L | route not resolved | 4 Mar 2017, 15:404 Mar 2017 | 4 Mar 2017, 16:30 | 7,400 ft | no position received |
| VLJ082N | route not resolved | 1 Mar 2017, 20:041 Mar 2017 | 1 Mar 2017, 20:44 | 22,150 ft | no position received |
| VLJ082L | route not resolved | 28 Feb 2017, 08:2828 Feb 2017 | 28 Feb 2017, 09:05 | 37,000 ft | no position received |
| VLJ097N | route not resolved | 27 Feb 2017, 15:3527 Feb 2017 | 27 Feb 2017, 16:13 | 25,250 ft | no position received |
| VLJ097L | route not resolved | 27 Feb 2017, 12:3927 Feb 2017 | 27 Feb 2017, 13:09 | 26,475 ft | no position received |
| VLJ074M | route not resolved | 26 Feb 2017, 11:3826 Feb 2017 | 26 Feb 2017, 12:08 | 21,800 ft | no position received |
| VLJ096L | route not resolved | 25 Feb 2017, 15:3825 Feb 2017 | 25 Feb 2017, 16:12 | 16,875 ft | no position received |
| VLJ061M | route not resolved | 23 Feb 2017, 14:2923 Feb 2017 | 23 Feb 2017, 14:59 | 28,875 ft | no position received |
