Back to the log
Aircraft
F-HREX
Common
The station's story
Address not received since 11 Aug 2022. The marker states the absence, it does not say why.
- Cumulative contact time
- 201 h
- Distinct days
- 394
- Highest captured altitude
- 41,050 ft
- 1 corrupted frame(s) excluded from this maximum
- Discovery rank
- #7,349 of 57,209
- Longest contact
- 1 h 24 min
Observed callsigns
VLJ (558 contacts, 2016-2022) · VMJ (1 contacts, 2016) · WLJ (1 contacts, 2017)
Operator as per the registry of 12 Aug 2026; observed callsigns are the freshest measurement.
Visits
| Callsign | Route | First contact | Last contact | Altitude at end of contact | Positions |
|---|---|---|---|---|---|
| VLJ18AE | route not resolved | 26 Jul 2019, 15:4526 Jul 2019 | 26 Jul 2019, 16:02 | 31,000 ft | no position received |
| VLJ16AE | route not resolved | 25 Jul 2019, 14:4725 Jul 2019 | 25 Jul 2019, 15:06 | 23,425 ft | no position received |
| VLJ16AE | route not resolved | 25 Jul 2019, 09:4625 Jul 2019 | 25 Jul 2019, 10:08 | 10,500 ft | no position received |
| VLJ10AA | route not resolved | 22 Jul 2019, 17:2022 Jul 2019 | 22 Jul 2019, 17:40 | 29,000 ft | no position received |
| VLJ10AA | route not resolved | 22 Jul 2019, 14:4522 Jul 2019 | 22 Jul 2019, 14:58 | 3,575 ft | no position received |
| VLJ12AE | route not resolved | 21 Jul 2019, 15:2221 Jul 2019 | 21 Jul 2019, 15:51 | 26,750 ft | no position received |
| VLJ12AE | route not resolved | 19 Jul 2019, 19:0619 Jul 2019 | 19 Jul 2019, 19:34 | 37,000 ft | no position received |
| VLJ02AR | route not resolved | 10 Jul 2019, 08:2110 Jul 2019 | 10 Jul 2019, 08:52 | 22,500 ft | no position received |
| VLJ02AR | route not resolved | 9 Jul 2019, 13:439 Jul 2019 | 9 Jul 2019, 14:02 | 33,000 ft | no position received |
| VLJ03AA | route not resolved | 9 Jul 2019, 07:449 Jul 2019 | 9 Jul 2019, 08:04 | 3,500 ft | no position received |
| VLJ08AE | route not resolved | 7 Jul 2019, 20:577 Jul 2019 | 7 Jul 2019, 21:13 | 22,025 ft | no position received |
| VLJ07AE | route not resolved | 5 Jul 2019, 17:135 Jul 2019 | 5 Jul 2019, 17:41 | 27,600 ft | no position received |
| VLJ37GA | route not resolved | 3 Jul 2019, 17:183 Jul 2019 | 3 Jul 2019, 17:50 | 24,200 ft | no position received |
| VLJ37GA | route not resolved | 3 Jul 2019, 13:243 Jul 2019 | 3 Jul 2019, 14:02 | 41,050 ft | no position received |
| VLJ04AE | route not resolved | 2 Jul 2019, 18:482 Jul 2019 | 2 Jul 2019, 19:14 | 21,925 ft | no position received |
| VLJ02AE | route not resolved | 30 Jun 2019, 17:1530 Jun 2019 | 30 Jun 2019, 17:40 | 23,100 ft | no position received |
| VLJ50BE | route not resolved | 27 Feb 2019, 12:3627 Feb 2019 | 27 Feb 2019, 12:57 | 26,475 ft | no position received |
| VLJ50BE | route not resolved | 26 Feb 2019, 13:5526 Feb 2019 | 26 Feb 2019, 14:14 | 39,025 ft | no position received |
| VLJ43BH | route not resolved | 25 Feb 2019, 23:3925 Feb 2019 | 26 Feb 2019, 00:07 | 27,175 ft | no position received |
| VLJ43BH | route not resolved | 25 Feb 2019, 17:3025 Feb 2019 | 25 Feb 2019, 17:59 | 37,025 ft | no position received |
| VLJ42BE | route not resolved | 24 Feb 2019, 18:5124 Feb 2019 | 24 Feb 2019, 19:09 | 23,275 ft | no position received |
| VLJ42BE | route not resolved | 24 Feb 2019, 17:4524 Feb 2019 | 24 Feb 2019, 18:03 | 6,675 ft | no position received |
| VLJ47BE | route not resolved | 21 Feb 2019, 12:5521 Feb 2019 | 21 Feb 2019, 13:36 | 22,825 ft | no position received |
| VLJ47BE | route not resolved | 21 Feb 2019, 09:0721 Feb 2019 | 21 Feb 2019, 09:46 | 950 ft | no position received |
| VLJ95AE | route not resolved | 10 Feb 2019, 19:1310 Feb 2019 | 10 Feb 2019, 19:28 | 26,025 ft | no position received |
