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,346 of 57,065
- 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 29 Jul 2026; observed callsigns are the freshest measurement.
Visits
| Callsign | Route | First contact | Last contact | Altitude at end of contact | Positions |
|---|---|---|---|---|---|
| VLJ080M | route not resolved | 1 Mar 2017, 23:511 Mar 2017 | 2 Mar 2017, 00:24 | 23,750 ft | no position received |
| VLJ080L | route not resolved | 1 Mar 2017, 15:551 Mar 2017 | 1 Mar 2017, 16:16 | 39,000 ft | no position received |
| not transmitted | route not resolved | 22 Feb 2017, 21:1322 Feb 2017 | 22 Feb 2017, 21:17 | 26,000 ft | no position received |
| VLJ055N | route not resolved | 17 Feb 2017, 16:2117 Feb 2017 | 17 Feb 2017, 16:55 | 22,775 ft | no position received |
| VLJ055M | route not resolved | 16 Feb 2017, 17:3216 Feb 2017 | 16 Feb 2017, 18:00 | 29,275 ft | no position received |
| VLJ004M | route not resolved | 4 Feb 2017, 08:354 Feb 2017 | 4 Feb 2017, 08:57 | 25,850 ft | no position received |
| VLJ004L | route not resolved | 4 Feb 2017, 06:574 Feb 2017 | 4 Feb 2017, 07:16 | 18,575 ft | no position received |
| VLJ033M | route not resolved | 27 Jan 2017, 12:2127 Jan 2017 | 27 Jan 2017, 12:51 | 24,075 ft | no position received |
| VLJ033L | route not resolved | 24 Jan 2017, 08:3524 Jan 2017 | 24 Jan 2017, 09:00 | 39,000 ft | no position received |
| VLJ619M | route not resolved | 11 Jan 2017, 16:1711 Jan 2017 | 11 Jan 2017, 16:51 | 23,275 ft | no position received |
| VLJ619L | route not resolved | 10 Jan 2017, 08:2210 Jan 2017 | 10 Jan 2017, 08:47 | 27,100 ft | no position received |
| VLJ578M | route not resolved | 1 Dec 2016, 21:191 Dec 2016 | 1 Dec 2016, 21:47 | 23,400 ft | no position received |
| VLJ578L | route not resolved | 1 Dec 2016, 12:321 Dec 2016 | 1 Dec 2016, 12:58 | 24,050 ft | no position received |
| VLJ577M | route not resolved | 30 Nov 2016, 10:2530 Nov 2016 | 30 Nov 2016, 10:57 | 22,850 ft | no position received |
| VLJ577L | route not resolved | 27 Nov 2016, 10:1627 Nov 2016 | 27 Nov 2016, 10:42 | 41,000 ft | no position received |
| VLJ458P | route not resolved | 25 Sept 2016, 18:5225 Sept 2016 | 25 Sept 2016, 19:17 | 24,300 ft | no position received |
| VLJ358L | route not resolved | 23 Sept 2016, 17:2823 Sept 2016 | 23 Sept 2016, 17:55 | 26,625 ft | no position received |
| VLJ452M | route not resolved | 23 Sept 2016, 12:2523 Sept 2016 | 23 Sept 2016, 12:55 | 22,725 ft | no position received |
| VLJ450L | route not resolved | 19 Sept 2016, 09:4919 Sept 2016 | 19 Sept 2016, 10:14 | 39,025 ft | no position received |
| VLJ445M | route not resolved | 8 Sept 2016, 15:318 Sept 2016 | 8 Sept 2016, 15:51 | 27,350 ft | no position received |
| VLJ445L | route not resolved | 8 Sept 2016, 13:598 Sept 2016 | 8 Sept 2016, 14:16 | 31,000 ft | no position received |
| VLJ439L | route not resolved | 2 Sept 2016, 10:452 Sept 2016 | 2 Sept 2016, 11:03 | 28,675 ft | no position received |
| VLJ400L | route not resolved | 17 Aug 2016, 11:0517 Aug 2016 | 17 Aug 2016, 11:26 | 26,175 ft | no position received |
| VLJ340L | route not resolved | 13 Aug 2016, 10:1413 Aug 2016 | 13 Aug 2016, 10:30 | 39,025 ft | no position received |
| VLJ360M | route not resolved | 2 Aug 2016, 16:242 Aug 2016 | 2 Aug 2016, 16:58 | 25,175 ft | no position received |
