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