Not currently tracked · last seen Jul 26, 18:00 UTC
- Flights observed
- 203 showing last 50
- Avg flight time
- 10h 12m
- Typical route
- LIS → LIS
- Last seen
- Jul 26, 18:00 UTC
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-26 | LIS → GIG | Jul 26, 08:45 UTC | Jul 26, 18:00 UTC | 9h 15m |
| 2026-07-25 | GIG → LIS | Jul 25, 18:40 UTC | Jul 26, 03:50 UTC | 9h 10m |
| 2026-07-24 | LIS → GIG | Jul 24, 22:50 UTC | Jul 25, 08:05 UTC | 9h 15m |
| 2026-07-24 | EWR → LIS | Jul 24, 04:30 UTC | Jul 24, 10:45 UTC | 6h 15m |
| 2026-07-23 | LIS → EWR | Jul 23, 19:30 UTC | Jul 24, 02:20 UTC | 6h 50m |
| 2026-07-23 | - | Jul 23, 09:45 UTC | Jul 23, 17:05 UTC | 7h 20m |
| 2026-07-23 | - | Jul 23, 00:20 UTC | Jul 23, 07:10 UTC | 6h 50m |
| 2026-07-22 | SFO → TER | Jul 22, 03:15 UTC | Jul 22, 16:30 UTC | 13h 15m |
| 2026-07-21 | LIS → TER | Jul 21, 08:50 UTC | Jul 22, 00:30 UTC | 15h 40m |
| 2026-07-20 | BSB → LIS | Jul 20, 10:05 UTC | Jul 21, 05:05 UTC | 19h 0m |
| 2026-07-20 | LIS → BSB | Jul 20, 09:25 UTC | Jul 21, 05:05 UTC | 19h 40m |
| 2026-07-19 | GRU → LIS | Jul 19, 18:40 UTC | Jul 20, 03:45 UTC | 9h 5m |
| 2026-07-18 | LIS → GRU | Jul 18, 23:00 UTC | Jul 19, 08:35 UTC | 9h 35m |
| 2026-07-18 | - | Jul 18, 05:20 UTC | Jul 18, 14:30 UTC | 9h 10m |
| 2026-07-17 | - | Jul 17, 16:24 UTC | Jul 18, 02:05 UTC | 9h 40m |
| 2026-07-16 | FNC → LIS | Jul 16, 13:45 UTC | Jul 16, 15:00 UTC | 1h 15m |
| 2026-07-16 | LIS → FNC | Jul 16, 10:59 UTC | Jul 16, 12:25 UTC | 1h 25m |
| 2026-07-15 | - | Jul 15, 23:45 UTC | Jul 16, 08:50 UTC | 9h 5m |
| 2026-07-15 | - | Jul 15, 11:20 UTC | Jul 15, 20:40 UTC | 9h 20m |
| 2026-07-14 | - | Jul 14, 10:15 UTC | Jul 15, 05:30 UTC | 19h 14m |
| 2026-07-14 | LIS → LIS | Jul 14, 09:15 UTC | Jul 15, 05:30 UTC | 20h 14m |
| 2026-07-13 | - | Jul 13, 10:05 UTC | Jul 14, 05:10 UTC | 19h 5m |
| 2026-07-13 | LIS → LIS | Jul 13, 09:45 UTC | Jul 14, 05:10 UTC | 19h 25m |
| 2026-07-12 | - | Jul 12, 10:15 UTC | Jul 13, 05:01 UTC | 18h 45m |
| 2026-07-12 | LIS → LIS | Jul 12, 09:05 UTC | Jul 13, 05:01 UTC | 19h 55m |
| 2026-07-10 | - | Jul 10, 22:20 UTC | Jul 11, 05:40 UTC | 7h 20m |
| 2026-07-10 | - | Jul 10, 12:50 UTC | Jul 10, 19:45 UTC | 6h 55m |
| 2026-07-10 | - | Jul 10, 00:15 UTC | Jul 10, 09:15 UTC | 9h 0m |
| 2026-07-09 | - | Jul 9, 13:10 UTC | Jul 9, 22:05 UTC | 8h 55m |
| 2026-07-09 | - | Jul 9, 12:15 UTC | Jul 9, 13:05 UTC | 50m |
| 2026-07-08 | - | Jul 8, 22:30 UTC | Jul 9, 06:10 UTC | 7h 40m |
| 2026-07-08 | - | Jul 8, 12:35 UTC | Jul 8, 19:45 UTC | 7h 10m |
| 2026-07-08 | - | Jul 8, 00:10 UTC | Jul 8, 09:50 UTC | 9h 40m |
| 2026-07-07 | - | Jul 7, 12:15 UTC | Jul 7, 22:05 UTC | 9h 50m |
| 2026-07-07 | - | Jul 7, 00:20 UTC | Jul 7, 09:35 UTC | 9h 15m |
| 2026-07-06 | - | Jul 6, 12:45 UTC | Jul 6, 22:20 UTC | 9h 35m |
| 2026-07-05 | - | Jul 5, 23:05 UTC | Jul 6, 06:45 UTC | 7h 40m |
| 2026-07-05 | - | Jul 5, 13:35 UTC | Jul 5, 20:55 UTC | 7h 20m |
| 2026-07-05 | - | Jul 5, 02:05 UTC | Jul 5, 11:25 UTC | 9h 20m |
| 2026-07-04 | - | Jul 4, 13:35 UTC | Jul 4, 23:55 UTC | 10h 20m |
| 2026-07-04 | - | Jul 4, 00:45 UTC | Jul 4, 10:05 UTC | 9h 20m |
| 2026-07-03 | OPO → GIG | Jul 3, 12:30 UTC | Jul 3, 22:25 UTC | 9h 55m |
| 2026-07-03 | - | Jul 3, 00:40 UTC | Jul 3, 10:05 UTC | 9h 25m |
| 2026-07-02 | - | Jul 2, 12:00 UTC | Jul 2, 21:50 UTC | 9h 50m |
| 2026-07-01 | - | Jul 1, 22:55 UTC | Jul 2, 06:15 UTC | 7h 20m |
| 2026-07-01 | - | Jul 1, 12:55 UTC | Jul 1, 20:20 UTC | 7h 25m |
| 2026-07-01 | - | Jul 1, 00:25 UTC | Jul 1, 10:00 UTC | 9h 35m |
| 2026-06-30 | OPO → GRU | Jun 30, 12:25 UTC | Jun 30, 22:25 UTC | 10h 0m |
| 2026-06-30 | - | Jun 30, 00:55 UTC | Jun 30, 10:15 UTC | 9h 20m |
| 2026-06-29 | OPO → GIG | Jun 29, 13:09 UTC | Jun 29, 22:44 UTC | 9h 35m |
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 LIS and LIS based on observed flights.
Where is CS-TUP right now?
CS-TUP is not currently being tracked; last seen Jul 26, 18:00 UTC.