sensors Mode-S transponder
4952B0
ICAO 24-bit transponder address · allocated to Portugal
Currently assigned to CS-TUP · AIRBUS A-330-900
- Hex
- 4952B0
- Octal
- 22251260
- Decimal
- 4,805,296
- Country
- PT
- Tail
- CS-TUP
- Type
- A339
- Flights observed
- 203
- Distinct callsigns
- 20
- Country
- PT
- Last broadcast
- Jul 26, 18:00 UTC
Last known position
Country allocation
The ICAO 24-bit address 4952B0 falls within the block assigned to Portugal (PT) by ICAO Annex 10, Volume III. Every aircraft registered in Portugal receives a permanent address from this block at the time of registration; the address stays with the airframe even if the aircraft is re-registered to a different operator within the country.
Callsign history 20 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| TAP093 | - | 15 | 2026-07-09 |
| TAP094 | - | 13 | 2026-07-08 |
| TAP077 | - | 12 | 2026-07-06 |
| TAP078 | - | 10 | 2026-07-07 |
| TAP074 | TAP Portugal | 8 | 2026-07-25 |
| TAP073 | TAP Portugal | 8 | 2026-07-26 |
| TAP084 | - | 7 | 2026-07-18 |
| TAP075 | TAP Portugal | 7 | 2026-07-24 |
| TAP294 | - | 6 | 2026-07-08 |
| TAP293 | - | 6 | 2026-07-08 |
| TAP083 | - | 6 | 2026-07-17 |
| TAP298 | - | 5 | 2026-07-23 |
| TAP072 | - | 5 | 2026-07-15 |
| TAP297 | - | 4 | 2026-07-23 |
| TAP244 | TAP Portugal | 4 | 2026-05-20 |
| TAP243U | TAP Portugal | 4 | 2026-05-20 |
| TAP225V | TAP Portugal | 4 | 2026-04-26 |
| TAP089 | - | 4 | 2026-06-25 |
| TAP088 | - | 4 | 2026-07-10 |
| TAP296 | - | 3 | 2026-07-10 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | TAP073 | LIS → GIG | Jul 26, 08:45 UTC | Jul 26, 18:00 UTC | 9h 15m |
| 2026-07-25 | TAP074 | GIG → LIS | Jul 25, 18:40 UTC | Jul 26, 03:50 UTC | 9h 10m |
| 2026-07-24 | TAP075 | LIS → GIG | Jul 24, 22:50 UTC | Jul 25, 08:05 UTC | 9h 15m |
| 2026-07-24 | TAP204A | EWR → LIS | Jul 24, 04:30 UTC | Jul 24, 10:45 UTC | 6h 15m |
| 2026-07-23 | TAP203 | LIS → EWR | Jul 23, 19:30 UTC | Jul 24, 02:20 UTC | 6h 50m |
| 2026-07-23 | TAP298 | - | Jul 23, 09:45 UTC | Jul 23, 17:05 UTC | 7h 20m |
| 2026-07-23 | TAP297 | - | Jul 23, 00:20 UTC | Jul 23, 07:10 UTC | 6h 50m |
| 2026-07-22 | TAP240 | SFO → TER | Jul 22, 03:15 UTC | Jul 22, 16:30 UTC | 13h 15m |
| 2026-07-21 | TAP241 | LIS → TER | Jul 21, 08:50 UTC | Jul 22, 00:30 UTC | 15h 40m |
| 2026-07-20 | TAP058 | BSB → LIS | Jul 20, 10:05 UTC | Jul 21, 05:05 UTC | 19h 0m |
| 2026-07-20 | TAP057 | LIS → BSB | Jul 20, 09:25 UTC | Jul 21, 05:05 UTC | 19h 40m |
| 2026-07-19 | TAP082 | GRU → LIS | Jul 19, 18:40 UTC | Jul 20, 03:45 UTC | 9h 5m |
| 2026-07-18 | TAP087 | LIS → GRU | Jul 18, 23:00 UTC | Jul 19, 08:35 UTC | 9h 35m |
| 2026-07-18 | TAP084 | - | Jul 18, 05:20 UTC | Jul 18, 14:30 UTC | 9h 10m |
| 2026-07-17 | TAP083 | - | Jul 17, 16:24 UTC | Jul 18, 02:05 UTC | 9h 40m |
| 2026-07-16 | TAP90EH | FNC → LIS | Jul 16, 13:45 UTC | Jul 16, 15:00 UTC | 1h 15m |
| 2026-07-16 | TAP89WT | LIS → FNC | Jul 16, 10:59 UTC | Jul 16, 12:25 UTC | 1h 25m |
| 2026-07-15 | TAP072 | - | Jul 15, 23:45 UTC | Jul 16, 08:50 UTC | 9h 5m |
| 2026-07-15 | TAP073 | - | Jul 15, 11:20 UTC | Jul 15, 20:40 UTC | 9h 20m |
| 2026-07-14 | TAP104 | - | Jul 14, 10:15 UTC | Jul 15, 05:30 UTC | 19h 14m |
| 2026-07-14 | TAP104 | LIS → LIS | Jul 14, 09:15 UTC | Jul 15, 05:30 UTC | 20h 14m |
| 2026-07-13 | TAP058 | - | Jul 13, 10:05 UTC | Jul 14, 05:10 UTC | 19h 5m |
| 2026-07-13 | TAP058 | LIS → LIS | Jul 13, 09:45 UTC | Jul 14, 05:10 UTC | 19h 25m |
| 2026-07-12 | TAP057 | - | Jul 12, 10:15 UTC | Jul 13, 05:01 UTC | 18h 45m |
| 2026-07-12 | TAP057 | LIS → LIS | Jul 12, 09:05 UTC | Jul 13, 05:01 UTC | 19h 55m |
| 2026-07-10 | TAP296 | - | Jul 10, 22:20 UTC | Jul 11, 05:40 UTC | 7h 20m |
| 2026-07-10 | TAP295 | - | Jul 10, 12:50 UTC | Jul 10, 19:45 UTC | 6h 55m |
| 2026-07-10 | TAP088 | - | Jul 10, 00:15 UTC | Jul 10, 09:15 UTC | 9h 0m |
| 2026-07-09 | TAP093 | - | Jul 9, 13:10 UTC | Jul 9, 22:05 UTC | 8h 55m |
| 2026-07-09 | TAP093 | - | Jul 9, 12:15 UTC | Jul 9, 13:05 UTC | 50m |
| 2026-07-08 | TAP294 | - | Jul 8, 22:30 UTC | Jul 9, 06:10 UTC | 7h 40m |
| 2026-07-08 | TAP293 | - | Jul 8, 12:35 UTC | Jul 8, 19:45 UTC | 7h 10m |
| 2026-07-08 | TAP094 | - | Jul 8, 00:10 UTC | Jul 8, 09:50 UTC | 9h 40m |
| 2026-07-07 | TAP093 | - | Jul 7, 12:15 UTC | Jul 7, 22:05 UTC | 9h 50m |
| 2026-07-07 | TAP078 | - | Jul 7, 00:20 UTC | Jul 7, 09:35 UTC | 9h 15m |
| 2026-07-06 | TAP077 | - | Jul 6, 12:45 UTC | Jul 6, 22:20 UTC | 9h 35m |
| 2026-07-05 | TAP294 | - | Jul 5, 23:05 UTC | Jul 6, 06:45 UTC | 7h 40m |
| 2026-07-05 | TAP293 | - | Jul 5, 13:35 UTC | Jul 5, 20:55 UTC | 7h 20m |
| 2026-07-05 | TAP094 | - | Jul 5, 02:05 UTC | Jul 5, 11:25 UTC | 9h 20m |
| 2026-07-04 | TAP093 | - | Jul 4, 13:35 UTC | Jul 4, 23:55 UTC | 10h 20m |
| 2026-07-04 | TAP078 | - | Jul 4, 00:45 UTC | Jul 4, 10:05 UTC | 9h 20m |
| 2026-07-03 | TAP077 | OPO → GIG | Jul 3, 12:30 UTC | Jul 3, 22:25 UTC | 9h 55m |
| 2026-07-03 | TAP094 | - | Jul 3, 00:40 UTC | Jul 3, 10:05 UTC | 9h 25m |
| 2026-07-02 | TAP093 | - | Jul 2, 12:00 UTC | Jul 2, 21:50 UTC | 9h 50m |
| 2026-07-01 | TAP294 | - | Jul 1, 22:55 UTC | Jul 2, 06:15 UTC | 7h 20m |
| 2026-07-01 | TAP293 | - | Jul 1, 12:55 UTC | Jul 1, 20:20 UTC | 7h 25m |
| 2026-07-01 | TAP094 | - | Jul 1, 00:25 UTC | Jul 1, 10:00 UTC | 9h 35m |
| 2026-06-30 | TAP093 | OPO → GRU | Jun 30, 12:25 UTC | Jun 30, 22:25 UTC | 10h 0m |
| 2026-06-30 | TAP078 | - | Jun 30, 00:55 UTC | Jun 30, 10:15 UTC | 9h 20m |
| 2026-06-29 | TAP077 | OPO → GIG | Jun 29, 13:09 UTC | Jun 29, 22:44 UTC | 9h 35m |
About Mode-S
A Mode-S transponder code (also called an "ICAO 24-bit address" or "hex code") is a 6-character hexadecimal identifier permanently assigned to an aircraft when it's first registered. Unlike callsigns (which change with each flight) or registrations (which can change if an aircraft is sold internationally), the Mode-S address stays with the airframe for the life of the aircraft in that country.
Every ADS-B transmission from an aircraft includes its Mode-S address, making it the most reliable way to identify a specific airframe. Flight-tracking services like Apparatus use the Mode-S address as the primary key for tying position broadcasts, callsigns, and ownership records together.
Prefer a tail-number view? See the CS-TUP page for operator, model, and routing details .