Not currently tracked · last seen Jul 26, 22:45 UTC
- Flights observed
- 234 showing last 50
- Avg flight time
- 8h 9m
- Typical route
- JFK → LHR
- Last seen
- Jul 26, 22:45 UTC
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-26 | LHR → SFO | Jul 26, 12:05 UTC | Jul 26, 22:45 UTC | 10h 40m |
| 2026-07-25 | LAX → LHR | Jul 25, 23:15 UTC | Jul 26, 08:35 UTC | 9h 21m |
| 2026-07-25 | LHR → LAX | Jul 25, 09:25 UTC | Jul 25, 20:15 UTC | 10h 50m |
| 2026-07-24 | ATL → LHR | Jul 24, 22:30 UTC | Jul 25, 05:55 UTC | 7h 25m |
| 2026-07-24 | LHR → ATL | Jul 24, 10:45 UTC | Jul 24, 19:00 UTC | 8h 15m |
| 2026-07-23 | JFK → LHR | Jul 23, 05:30 UTC | Jul 23, 10:35 UTC | 5h 5m |
| 2026-07-23 | JFK → LHR | Jul 23, 04:20 UTC | Jul 23, 05:25 UTC | 1h 5m |
| 2026-07-22 | LHR → JFK | Jul 22, 17:55 UTC | Jul 23, 00:45 UTC | 6h 50m |
| 2026-07-22 | JFK → LHR | Jul 22, 11:10 UTC | Jul 22, 12:40 UTC | 1h 30m |
| 2026-07-21 | LHR → JFK | Jul 21, 20:55 UTC | Jul 22, 03:55 UTC | 7h 0m |
| 2026-07-21 | SFO → LHR | Jul 21, 01:25 UTC | Jul 21, 11:05 UTC | 9h 40m |
| 2026-07-20 | LHR → SFO | Jul 20, 12:10 UTC | Jul 20, 22:35 UTC | 10h 25m |
| 2026-07-20 | BOS → LHR | Jul 20, 02:15 UTC | Jul 20, 08:30 UTC | 6h 15m |
| 2026-07-19 | - | Jul 19, 16:20 UTC | Jul 19, 22:55 UTC | 6h 35m |
| 2026-07-19 | SFO → LHR | Jul 19, 01:30 UTC | Jul 19, 10:50 UTC | 9h 20m |
| 2026-07-18 | LHR → SFO | Jul 18, 12:25 UTC | Jul 18, 22:55 UTC | 10h 30m |
| 2026-07-18 | JFK → LHR | Jul 18, 01:50 UTC | Jul 18, 08:15 UTC | 6h 26m |
| 2026-07-17 | - | Jul 17, 16:00 UTC | Jul 17, 22:45 UTC | 6h 45m |
| 2026-07-16 | SFO → LHR | Jul 16, 01:30 UTC | Jul 16, 11:10 UTC | 9h 40m |
| 2026-07-15 | - | Jul 15, 12:15 UTC | Jul 15, 22:45 UTC | 10h 30m |
| 2026-07-14 | LAX → LHR | Jul 14, 23:00 UTC | Jul 15, 09:05 UTC | 10h 5m |
| 2026-07-14 | - | Jul 14, 09:25 UTC | Jul 14, 19:45 UTC | 10h 20m |
| 2026-07-13 | ATL → LHR | Jul 13, 22:40 UTC | Jul 14, 06:15 UTC | 7h 35m |
| 2026-07-13 | LHR → ATL | Jul 13, 11:25 UTC | Jul 13, 19:30 UTC | 8h 5m |
| 2026-07-13 | JFK → LHR | Jul 13, 01:01 UTC | Jul 13, 07:25 UTC | 6h 25m |
| 2026-07-12 | LHR → JFK | Jul 12, 15:40 UTC | Jul 12, 22:20 UTC | 6h 40m |
| 2026-07-12 | SFO → LHR | Jul 12, 01:30 UTC | Jul 12, 10:55 UTC | 9h 25m |
| 2026-07-11 | LHR → SFO | Jul 11, 12:00 UTC | Jul 11, 22:35 UTC | 10h 35m |
| 2026-07-10 | LAX → LHR | Jul 10, 23:10 UTC | Jul 11, 09:00 UTC | 9h 50m |
| 2026-07-10 | LHR → LAX | Jul 10, 09:35 UTC | Jul 10, 20:05 UTC | 10h 30m |
| 2026-07-09 | ATL → LHR | Jul 9, 22:50 UTC | Jul 10, 06:20 UTC | 7h 30m |
| 2026-07-09 | LHR → ATL | Jul 9, 10:40 UTC | Jul 9, 18:55 UTC | 8h 15m |
| 2026-07-08 | ATL → LHR | Jul 8, 22:30 UTC | Jul 9, 06:20 UTC | 7h 50m |
| 2026-07-08 | - | Jul 8, 10:45 UTC | Jul 8, 18:50 UTC | 8h 5m |
| 2026-07-07 | JFK → LHR | Jul 7, 23:30 UTC | Jul 8, 05:45 UTC | 6h 15m |
| 2026-07-07 | - | Jul 7, 08:30 UTC | Jul 7, 15:20 UTC | 6h 50m |
| 2026-07-06 | - | Jul 6, 01:50 UTC | Jul 6, 11:30 UTC | 9h 40m |
| 2026-07-05 | - | Jul 5, 12:15 UTC | Jul 5, 22:50 UTC | 10h 35m |
| 2026-07-04 | LAX → LHR | Jul 4, 23:15 UTC | Jul 5, 09:05 UTC | 9h 50m |
| 2026-07-04 | - | Jul 4, 09:40 UTC | Jul 4, 20:20 UTC | 10h 40m |
| 2026-07-02 | JFK → LHR | Jul 2, 23:40 UTC | Jul 3, 05:40 UTC | 6h 0m |
| 2026-07-02 | - | Jul 2, 13:05 UTC | Jul 2, 20:20 UTC | 7h 15m |
| 2026-07-02 | YYZ → LHR | Jul 2, 03:50 UTC | Jul 2, 10:00 UTC | 6h 10m |
| 2026-07-01 | LHR → YYZ | Jul 1, 17:15 UTC | Jul 2, 00:40 UTC | 7h 25m |
| 2026-07-01 | SFO → LHR | Jul 1, 01:30 UTC | Jul 1, 10:40 UTC | 9h 10m |
| 2026-06-30 | - | Jun 30, 12:10 UTC | Jun 30, 22:05 UTC | 9h 55m |
| 2026-06-29 | LAX → LHR | Jun 29, 23:14 UTC | Jun 30, 08:45 UTC | 9h 30m |
| 2026-06-29 | - | Jun 29, 09:29 UTC | Jun 29, 19:39 UTC | 10h 10m |
| 2026-06-28 | - | Jun 28, 22:55 UTC | Jun 29, 05:04 UTC | 6h 10m |
| 2026-06-28 | - | Jun 28, 07:54 UTC | Jun 28, 14:39 UTC | 6h 45m |
Specifications
| Registration | G-VLUX |
| Aircraft type | AIRBUS A-350-1000 (A35K) |
| Mode-S code | 4075B3 · 20072663 (octal) |
Looking for transponder-level data? View the Mode-S 4075B3 page for country allocation, callsign history, and ADS-B signal details.
G-VLUX frequently asked
What type of aircraft is G-VLUX?
G-VLUX is a AIRBUS A-350-1000 (ICAO type code A35K).
What is the Mode-S transponder code for G-VLUX?
G-VLUX broadcasts on Mode-S (ICAO 24-bit) address 4075B3 (octal 20072663). View the transponder page.
What route does G-VLUX typically fly?
G-VLUX most frequently flies between JFK and LHR based on observed flights.
Where is G-VLUX right now?
G-VLUX is not currently being tracked; last seen Jul 26, 22:45 UTC.