Not currently tracked · last seen 24m ago
- Flights observed
- 126 showing last 50
- Avg flight time
- 19h 20m
- Typical route
- -
- Last seen
- 24m ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-14 | - | Jul 14, 03:40 UTC | Jul 14, 04:40 UTC | 1h 0m |
| 2026-07-13 | FCO → CAI | Jul 13, 16:45 UTC | Jul 13, 19:25 UTC | 2h 40m |
| 2026-07-13 | CAI → FCO | Jul 13, 13:15 UTC | Jul 13, 15:15 UTC | 2h 0m |
| 2026-07-12 | - | Jul 12, 15:15 UTC | Jul 13, 10:35 UTC | 19h 20m |
| 2026-07-12 | - | Jul 12, 03:05 UTC | Jul 13, 03:01 UTC | 23h 55m |
| 2026-07-12 | - | Jul 12, 01:25 UTC | Jul 12, 19:20 UTC | 17h 55m |
| 2026-07-11 | - | Jul 11, 19:05 UTC | Jul 12, 19:01 UTC | 23h 55m |
| 2026-07-11 | - | Jul 11, 17:05 UTC | Jul 12, 17:01 UTC | 23h 55m |
| 2026-07-11 | - | Jul 11, 15:10 UTC | Jul 12, 03:05 UTC | 11h 55m |
| 2026-07-10 | - | Jul 10, 15:30 UTC | Jul 11, 03:30 UTC | 12h 0m |
| 2026-07-09 | - | Jul 9, 15:15 UTC | Jul 10, 03:10 UTC | 11h 55m |
| 2026-07-09 | - | Jul 9, 03:05 UTC | Jul 10, 03:00 UTC | 23h 55m |
| 2026-07-09 | - | Jul 9, 01:05 UTC | Jul 10, 01:00 UTC | 23h 55m |
| 2026-07-09 | - | Jul 9, 00:10 UTC | Jul 9, 19:20 UTC | 19h 10m |
| 2026-07-08 | - | Jul 8, 19:05 UTC | Jul 9, 19:00 UTC | 23h 55m |
| 2026-07-08 | - | Jul 8, 17:05 UTC | Jul 9, 17:00 UTC | 23h 55m |
| 2026-07-08 | - | Jul 8, 15:00 UTC | Jul 9, 03:15 UTC | 12h 15m |
| 2026-07-07 | - | Jul 7, 15:25 UTC | Jul 8, 03:40 UTC | 12h 15m |
| 2026-07-07 | - | Jul 7, 03:05 UTC | Jul 8, 03:00 UTC | 23h 55m |
| 2026-07-07 | - | Jul 7, 01:05 UTC | Jul 7, 19:35 UTC | 18h 30m |
| 2026-07-06 | - | Jul 6, 23:15 UTC | Jul 7, 19:35 UTC | 20h 20m |
| 2026-07-06 | - | Jul 6, 19:05 UTC | Jul 7, 19:00 UTC | 23h 55m |
| 2026-07-06 | - | Jul 6, 17:05 UTC | Jul 7, 17:00 UTC | 23h 55m |
| 2026-07-06 | - | Jul 6, 15:20 UTC | Jul 7, 03:15 UTC | 11h 55m |
| 2026-07-06 | - | Jul 6, 03:05 UTC | Jul 7, 03:00 UTC | 23h 55m |
| 2026-07-06 | - | Jul 6, 01:05 UTC | Jul 7, 01:00 UTC | 23h 55m |
| 2026-07-06 | - | Jul 6, 00:15 UTC | Jul 6, 19:35 UTC | 19h 20m |
| 2026-07-05 | - | Jul 5, 19:05 UTC | Jul 6, 19:00 UTC | 23h 55m |
| 2026-07-05 | - | Jul 5, 17:05 UTC | Jul 6, 17:00 UTC | 23h 55m |
| 2026-07-05 | - | Jul 5, 15:15 UTC | Jul 6, 03:15 UTC | 12h 0m |
| 2026-07-05 | - | Jul 5, 03:05 UTC | Jul 6, 03:00 UTC | 23h 55m |
| 2026-07-05 | - | Jul 5, 01:05 UTC | Jul 6, 01:00 UTC | 23h 55m |
| 2026-07-05 | - | Jul 5, 00:35 UTC | Jul 5, 19:25 UTC | 18h 50m |
| 2026-07-04 | - | Jul 4, 19:05 UTC | Jul 5, 19:00 UTC | 23h 55m |
| 2026-07-04 | - | Jul 4, 17:05 UTC | Jul 5, 17:00 UTC | 23h 55m |
| 2026-07-04 | - | Jul 4, 15:05 UTC | Jul 5, 03:15 UTC | 12h 10m |
| 2026-07-04 | - | Jul 4, 03:05 UTC | Jul 5, 03:00 UTC | 23h 55m |
| 2026-07-04 | - | Jul 4, 01:05 UTC | Jul 5, 01:00 UTC | 23h 55m |
| 2026-07-03 | - | Jul 3, 19:05 UTC | Jul 4, 19:00 UTC | 23h 55m |
| 2026-07-03 | - | Jul 3, 17:05 UTC | Jul 4, 17:00 UTC | 23h 55m |
| 2026-07-03 | - | Jul 3, 15:25 UTC | Jul 4, 03:25 UTC | 12h 0m |
| 2026-07-02 | - | Jul 2, 19:05 UTC | Jul 3, 19:00 UTC | 23h 55m |
| 2026-07-02 | - | Jul 2, 17:05 UTC | Jul 3, 17:00 UTC | 23h 55m |
| 2026-07-02 | - | Jul 2, 01:05 UTC | Jul 2, 19:25 UTC | 18h 20m |
| 2026-07-02 | - | Jul 2, 00:50 UTC | Jul 2, 19:25 UTC | 18h 35m |
| 2026-07-01 | - | Jul 1, 19:05 UTC | Jul 2, 19:00 UTC | 23h 55m |
| 2026-07-01 | - | Jul 1, 17:05 UTC | Jul 2, 17:00 UTC | 23h 55m |
| 2026-07-01 | - | Jul 1, 15:15 UTC | Jul 2, 03:55 UTC | 12h 40m |
| 2026-07-01 | - | Jul 1, 03:05 UTC | Jul 2, 03:00 UTC | 23h 55m |
| 2026-07-01 | - | Jul 1, 01:05 UTC | Jul 2, 01:00 UTC | 23h 55m |
Specifications
| Registration | SU-GDX |
| Aircraft type | BOEING 737-800 (B738) |
| Mode-S code | 010144 · 00200504 (octal) |
Looking for transponder-level data? View the Mode-S 010144 page for country allocation, callsign history, and ADS-B signal details.
SU-GDX frequently asked
What type of aircraft is SU-GDX?
SU-GDX is a BOEING 737-800 (ICAO type code B738).
What is the Mode-S transponder code for SU-GDX?
SU-GDX broadcasts on Mode-S (ICAO 24-bit) address 010144 (octal 00200504). View the transponder page.
Where is SU-GDX right now?
SU-GDX is not currently being tracked; last seen 24m ago.