Not currently tracked · last seen Jul 26, 22:05 UTC
- Flights observed
- 205 showing last 50
- Avg flight time
- 10h 48m
- Typical route
- LIS → LIS
- Last seen
- Jul 26, 22:05 UTC
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-26 | GRU → LIS | Jul 26, 19:00 UTC | Jul 26, 22:05 UTC | 3h 5m |
| 2026-07-26 | LIS → GRU | Jul 26, 00:00 UTC | Jul 26, 09:20 UTC | 9h 21m |
| 2026-07-24 | GIG → LIS | Jul 24, 18:50 UTC | Jul 25, 04:00 UTC | 9h 10m |
| 2026-07-23 | LIS → GIG | Jul 23, 22:45 UTC | Jul 24, 08:10 UTC | 9h 25m |
| 2026-07-23 | REC → LIS | Jul 23, 05:10 UTC | Jul 23, 11:55 UTC | 6h 45m |
| 2026-07-22 | LIS → REC | Jul 22, 19:25 UTC | Jul 23, 02:30 UTC | 7h 5m |
| 2026-07-21 | LIS → LIS | Jul 21, 22:55 UTC | Jul 22, 15:50 UTC | 16h 55m |
| 2026-07-20 | MIA → LIS | Jul 20, 20:35 UTC | Jul 21, 04:25 UTC | 7h 50m |
| 2026-07-20 | LIS → MIA | Jul 20, 09:55 UTC | Jul 20, 18:00 UTC | 8h 5m |
| 2026-07-19 | GIG → LIS | Jul 19, 18:55 UTC | Jul 20, 03:50 UTC | 8h 55m |
| 2026-07-18 | LIS → GIG | Jul 18, 22:50 UTC | Jul 19, 08:15 UTC | 9h 25m |
| 2026-07-17 | GIG → LIS | Jul 17, 18:44 UTC | Jul 18, 03:40 UTC | 8h 56m |
| 2026-07-16 | LIS → GIG | Jul 16, 22:59 UTC | Jul 17, 08:25 UTC | 9h 25m |
| 2026-07-15 | - | Jul 15, 10:50 UTC | Jul 16, 05:35 UTC | 18h 45m |
| 2026-07-15 | LIS → LIS | Jul 15, 09:35 UTC | Jul 16, 05:35 UTC | 20h 0m |
| 2026-07-14 | - | Jul 14, 20:40 UTC | Jul 15, 04:15 UTC | 7h 34m |
| 2026-07-14 | - | Jul 14, 09:55 UTC | Jul 14, 18:15 UTC | 8h 20m |
| 2026-07-13 | - | Jul 13, 20:15 UTC | Jul 14, 05:10 UTC | 8h 55m |
| 2026-07-12 | LIS → GIG | Jul 12, 08:50 UTC | Jul 12, 18:25 UTC | 9h 35m |
| 2026-07-11 | - | Jul 11, 21:05 UTC | Jul 12, 04:45 UTC | 7h 40m |
| 2026-07-11 | LIS → MIA | Jul 11, 10:15 UTC | Jul 11, 18:35 UTC | 8h 20m |
| 2026-07-10 | - | Jul 10, 18:50 UTC | Jul 11, 03:30 UTC | 8h 40m |
| 2026-07-09 | - | Jul 9, 22:50 UTC | Jul 10, 08:20 UTC | 9h 30m |
| 2026-07-09 | - | Jul 9, 00:10 UTC | Jul 9, 10:10 UTC | 10h 0m |
| 2026-07-08 | LIS → SFO | Jul 8, 09:35 UTC | Jul 8, 21:25 UTC | 11h 50m |
| 2026-07-07 | - | Jul 7, 21:15 UTC | Jul 8, 05:30 UTC | 8h 15m |
| 2026-07-07 | - | Jul 7, 08:50 UTC | Jul 8, 05:30 UTC | 20h 40m |
| 2026-07-06 | - | Jul 6, 20:50 UTC | Jul 7, 04:35 UTC | 7h 45m |
| 2026-07-06 | LIS → MIA | Jul 6, 10:00 UTC | Jul 6, 18:10 UTC | 8h 10m |
| 2026-07-06 | ORD → LIS | Jul 6, 00:20 UTC | Jul 6, 07:40 UTC | 7h 20m |
| 2026-07-05 | LIS → ORD | Jul 5, 12:35 UTC | Jul 5, 21:10 UTC | 8h 35m |
| 2026-07-05 | ORD → LIS | Jul 5, 03:25 UTC | Jul 5, 10:30 UTC | 7h 5m |
| 2026-07-05 | - | Jul 5, 00:15 UTC | Jul 5, 00:50 UTC | 35m |
| 2026-07-04 | - | Jul 4, 12:45 UTC | Jul 4, 21:50 UTC | 9h 5m |
| 2026-07-03 | - | Jul 3, 22:35 UTC | Jul 4, 07:30 UTC | 8h 55m |
| 2026-07-03 | - | Jul 3, 09:00 UTC | Jul 3, 18:25 UTC | 9h 25m |
| 2026-07-02 | - | Jul 2, 16:20 UTC | Jul 3, 05:25 UTC | 13h 5m |
| 2026-07-02 | LIS → LIS | Jul 2, 09:45 UTC | Jul 3, 05:25 UTC | 19h 40m |
| 2026-07-01 | - | Jul 1, 11:00 UTC | Jul 2, 05:45 UTC | 18h 45m |
| 2026-07-01 | LIS → LIS | Jul 1, 10:00 UTC | Jul 2, 05:45 UTC | 19h 45m |
| 2026-06-30 | - | Jun 30, 18:35 UTC | Jul 1, 03:45 UTC | 9h 10m |
| 2026-06-29 | - | Jun 29, 22:49 UTC | Jun 30, 08:35 UTC | 9h 46m |
| 2026-06-29 | - | Jun 29, 15:39 UTC | Jun 29, 17:10 UTC | 1h 30m |
| 2026-06-28 | - | Jun 28, 18:49 UTC | Jun 29, 17:10 UTC | 22h 20m |
| 2026-06-28 | - | Jun 28, 18:29 UTC | Jun 29, 16:44 UTC | 22h 15m |
| 2026-06-28 | - | Jun 28, 03:05 UTC | Jun 28, 13:00 UTC | 9h 55m |
| 2026-06-27 | LIS → SFO | Jun 27, 13:00 UTC | Jun 28, 00:39 UTC | 11h 40m |
| 2026-06-26 | - | Jun 26, 15:45 UTC | Jun 27, 05:35 UTC | 13h 50m |
| 2026-06-26 | LIS → LIS | Jun 26, 09:24 UTC | Jun 27, 05:35 UTC | 20h 10m |
| 2026-06-25 | - | Jun 25, 18:59 UTC | Jun 26, 03:54 UTC | 8h 55m |
Specifications
| Registration | CS-TUK |
| Aircraft type | AIRBUS A-330-900 (A339) |
| Mode-S code | 4952AB · 22251253 (octal) |
Looking for transponder-level data? View the Mode-S 4952AB page for country allocation, callsign history, and ADS-B signal details.
CS-TUK frequently asked
What type of aircraft is CS-TUK?
CS-TUK is a AIRBUS A-330-900 (ICAO type code A339).
What is the Mode-S transponder code for CS-TUK?
CS-TUK broadcasts on Mode-S (ICAO 24-bit) address 4952AB (octal 22251253). View the transponder page.
What route does CS-TUK typically fly?
CS-TUK most frequently flies between LIS and LIS based on observed flights.
Where is CS-TUK right now?
CS-TUK is not currently being tracked; last seen Jul 26, 22:05 UTC.