Not currently tracked · last seen 2d ago
- Flights observed
- 52 showing last 50
- Avg flight time
- 4h 56m
- Typical route
- RUN → CDG
- Last seen
- 2d ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-05-30 | CDG → RUN | May 30, 17:25 UTC | May 30, 20:50 UTC | 3h 25m |
| 2026-05-30 | RUN → CDG | May 30, 03:15 UTC | May 30, 06:20 UTC | 3h 5m |
| 2026-05-29 | RUN → CDG | May 29, 09:05 UTC | May 30, 06:20 UTC | 21h 15m |
| 2026-05-29 | RUN → CDG | May 29, 07:05 UTC | May 30, 06:20 UTC | 23h 15m |
| 2026-05-29 | RUN → CDG | May 29, 01:45 UTC | May 29, 04:30 UTC | 2h 45m |
| 2026-05-27 | BKK → RUN | May 27, 03:04 UTC | May 27, 03:34 UTC | 30m |
| 2026-05-24 | CDG → RUN | May 24, 17:15 UTC | May 24, 21:00 UTC | 3h 45m |
| 2026-05-24 | RUN → CDG | May 24, 03:35 UTC | May 24, 04:05 UTC | 30m |
| 2026-05-23 | BKK → RUN | May 23, 02:45 UTC | May 23, 03:15 UTC | 30m |
| 2026-05-22 | RUN → BKK | May 22, 23:00 UTC | May 22, 23:45 UTC | 45m |
| 2026-05-20 | CDG → RUN | May 20, 17:20 UTC | May 20, 20:00 UTC | 2h 40m |
| 2026-05-19 | RUN → CDG | May 19, 00:05 UTC | May 19, 03:35 UTC | 3h 30m |
| 2026-05-17 | CDG → RUN | May 17, 17:25 UTC | May 17, 20:15 UTC | 2h 50m |
| 2026-05-17 | RUN → CDG | May 17, 00:15 UTC | May 17, 03:45 UTC | 3h 30m |
| 2026-05-16 | RUN → CDG | May 16, 02:20 UTC | May 17, 01:00 UTC | 22h 40m |
| 2026-05-15 | RUN → BKK | May 15, 23:10 UTC | May 15, 23:50 UTC | 40m |
| 2026-05-08 | CDG → RUN | May 8, 17:10 UTC | May 8, 20:40 UTC | 3h 30m |
| 2026-05-08 | RUN → CDG | May 8, 03:09 UTC | May 8, 03:55 UTC | 45m |
| 2026-05-07 | BKK → RUN | May 7, 02:25 UTC | May 7, 03:00 UTC | 35m |
| 2026-05-06 | RUN → BKK | May 6, 23:15 UTC | May 6, 23:55 UTC | 40m |
| 2026-05-06 | RUN → BKK | May 6, 02:20 UTC | May 6, 23:55 UTC | 21h 34m |
| 2026-05-05 | RUN → BKK | May 5, 22:50 UTC | May 5, 23:30 UTC | 40m |
| 2026-05-04 | CDG → RUN | May 4, 17:30 UTC | May 4, 20:10 UTC | 2h 41m |
| 2026-05-04 | RUN → CDG | May 4, 00:34 UTC | May 4, 04:00 UTC | 3h 25m |
| 2026-05-02 | CDG → RUN | May 2, 21:15 UTC | May 3, 00:55 UTC | 3h 40m |
| 2026-05-02 | RUN → CDG | May 2, 14:55 UTC | May 2, 18:00 UTC | 3h 5m |
| 2026-05-01 | RUN → CDG | May 1, 19:05 UTC | May 2, 18:00 UTC | 22h 55m |
| 2026-05-01 | CDG → RUN | May 1, 17:30 UTC | May 2, 17:00 UTC | 23h 31m |
| 2026-05-01 | RUN → CDG | May 1, 01:10 UTC | May 1, 04:25 UTC | 3h 15m |
| 2026-04-30 | RUN → CDG | Apr 30, 03:05 UTC | May 1, 03:00 UTC | 23h 55m |
| 2026-04-30 | BKK → RUN | Apr 30, 02:55 UTC | Apr 30, 03:30 UTC | 35m |
| 2026-04-29 | RUN → BKK | Apr 29, 23:10 UTC | Apr 29, 23:50 UTC | 40m |
| 2026-04-28 | CDG → RUN | Apr 28, 17:25 UTC | Apr 28, 20:05 UTC | 2h 40m |
| 2026-04-28 | RUN → CDG | Apr 28, 00:20 UTC | Apr 28, 03:45 UTC | 3h 25m |
| 2026-04-26 | CDG → RUN | Apr 26, 22:10 UTC | Apr 27, 00:55 UTC | 2h 45m |
| 2026-04-26 | RUN → CDG | Apr 26, 03:20 UTC | Apr 26, 06:50 UTC | 3h 30m |
| 2026-04-25 | BKK → RUN | Apr 25, 02:40 UTC | Apr 25, 03:10 UTC | 30m |
| 2026-04-24 | RUN → BKK | Apr 24, 22:45 UTC | Apr 24, 23:35 UTC | 50m |
| 2026-04-22 | CDG → RUN | Apr 22, 17:15 UTC | Apr 22, 20:30 UTC | 3h 15m |
| 2026-04-22 | RUN → CDG | Apr 22, 00:15 UTC | Apr 22, 03:55 UTC | 3h 40m |
| 2026-04-19 | CDG → RUN | Apr 19, 17:15 UTC | Apr 19, 19:55 UTC | 2h 40m |
| 2026-04-19 | RUN → CDG | Apr 19, 01:40 UTC | Apr 19, 04:55 UTC | 3h 15m |
| 2026-04-17 | CDG → RUN | Apr 17, 21:25 UTC | Apr 17, 21:55 UTC | 30m |
| 2026-04-17 | CDG → RUN | Apr 17, 19:25 UTC | Apr 17, 21:20 UTC | 1h 55m |
| 2026-04-17 | RUN → CDG | Apr 17, 03:20 UTC | Apr 17, 03:50 UTC | 30m |
| 2026-04-17 | RUN → CDG | Apr 17, 01:20 UTC | Apr 17, 03:15 UTC | 1h 55m |
| 2026-04-17 | RUN → CDG | Apr 17, 00:35 UTC | Apr 17, 01:15 UTC | 40m |
| 2026-04-15 | CDG → RUN | Apr 15, 19:05 UTC | Apr 15, 20:50 UTC | 1h 45m |
| 2026-04-15 | CDG → RUN | Apr 15, 17:50 UTC | Apr 15, 19:00 UTC | 1h 10m |
| 2026-04-15 | RUN → CDG | Apr 15, 02:55 UTC | Apr 15, 03:45 UTC | 50m |
Specifications
| Registration | F-OREU |
| Aircraft type | BOEING 777-300ER (B77W) |
| Mode-S code | 3A4494 · 16442224 (octal) |
Looking for transponder-level data? View the Mode-S 3A4494 page for country allocation, callsign history, and ADS-B signal details.
F-OREU frequently asked
What type of aircraft is F-OREU?
F-OREU is a BOEING 777-300ER (ICAO type code B77W).
What is the Mode-S transponder code for F-OREU?
F-OREU broadcasts on Mode-S (ICAO 24-bit) address 3A4494 (octal 16442224). View the transponder page.
What route does F-OREU typically fly?
F-OREU most frequently flies between RUN and CDG based on observed flights.
Where is F-OREU right now?
F-OREU is not currently being tracked; last seen 2d ago.