sensors Mode-S transponder
4952AB
ICAO 24-bit transponder address · allocated to Portugal
Currently assigned to CS-TUK · AIRBUS A-330-900
- Hex
- 4952AB
- Octal
- 22251253
- Decimal
- 4,805,291
- Country
- PT
- Tail
- CS-TUK
- Type
- A339
- Flights observed
- 113
- Distinct callsigns
- 20
- Country
- PT
- Last broadcast
- 1h ago
Last known position
Country allocation
The ICAO 24-bit address 4952AB 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 |
|---|---|---|---|
| TAP084 | TAP Portugal | 7 | 2026-05-14 |
| TAP083 | TAP Portugal | 7 | 2026-05-13 |
| TAP89WT | TAP Portugal | 5 | 2026-05-26 |
| TAP3177 | - | 5 | 2026-05-25 |
| TAP104 | TAP Portugal | 5 | 2026-05-10 |
| TAP089 | TAP Portugal | 5 | 2026-05-29 |
| TAP088 | TAP Portugal | 5 | 2026-05-30 |
| TAP244 | TAP Portugal | 4 | 2026-04-16 |
| TAP243U | TAP Portugal | 4 | 2026-04-15 |
| TAP210 | TAP Portugal | 4 | 2026-05-05 |
| TAP209K | TAP Portugal | 4 | 2026-05-04 |
| TAP073 | TAP Portugal | 4 | 2026-05-28 |
| TAP072 | TAP Portugal | 4 | 2026-05-28 |
| TAP057 | TAP Portugal | 4 | 2026-05-11 |
| TAP036 | TAP Portugal | 4 | 2026-05-09 |
| TAP035 | TAP Portugal | 4 | 2026-05-08 |
| TAP90EH | TAP Portugal | 3 | 2026-05-26 |
| TAP22MI | TAP Portugal | 3 | 2026-04-30 |
| TAP224 | TAP Portugal | 3 | 2026-04-30 |
| TAP103 | TAP Portugal | 3 | 2026-05-10 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-30 | TAP088 | GRU → LIS | May 30, 00:15 UTC | May 30, 03:20 UTC | 3h 5m |
| 2026-05-29 | TAP089 | LIS → GRU | May 29, 12:35 UTC | May 29, 22:10 UTC | 9h 35m |
| 2026-05-28 | TAP072 | GIG → LIS | May 28, 23:40 UTC | May 29, 08:45 UTC | 9h 5m |
| 2026-05-28 | TAP073 | LIS → GIG | May 28, 09:15 UTC | May 28, 18:40 UTC | 9h 25m |
| 2026-05-27 | TAP082 | GRU → LIS | May 27, 18:55 UTC | May 28, 04:00 UTC | 9h 5m |
| 2026-05-26 | TAP087 | LIS → GRU | May 26, 22:59 UTC | May 27, 08:50 UTC | 9h 51m |
| 2026-05-26 | TAP90EH | FNC → LIS | May 26, 14:24 UTC | May 26, 15:54 UTC | 1h 30m |
| 2026-05-26 | TAP89WT | LIS → FNC | May 26, 13:00 UTC | May 26, 13:04 UTC | 5m |
| 2026-05-26 | TAP89WT | LIS → FNC | May 26, 11:30 UTC | May 26, 12:05 UTC | 35m |
| 2026-05-26 | TAP3178 | - | May 26, 07:24 UTC | May 26, 07:59 UTC | 35m |
| 2026-05-25 | TAP3177 | LIS → LIS | May 25, 11:30 UTC | May 26, 07:59 UTC | 20h 29m |
| 2026-05-24 | TAP011 | LIS → REC | May 24, 16:40 UTC | May 25, 08:20 UTC | 15h 40m |
| 2026-05-24 | TAP088 | GRU → LIS | May 24, 00:10 UTC | May 24, 09:10 UTC | 9h 0m |
| 2026-05-23 | TAP089 | LIS → GRU | May 23, 12:15 UTC | May 23, 21:55 UTC | 9h 40m |
| 2026-05-23 | TAP088 | GRU → LIS | May 23, 00:35 UTC | May 23, 09:40 UTC | 9h 5m |
| 2026-05-22 | TAP089 | LIS → GRU | May 22, 12:40 UTC | May 22, 22:40 UTC | 10h 0m |
| 2026-05-21 | TAP028 | FOR → LIS | May 21, 16:50 UTC | May 22, 10:30 UTC | 17h 40m |
| 2026-05-21 | TAP204A | EWR → LIS | May 21, 04:05 UTC | May 21, 10:15 UTC | 6h 10m |
| 2026-05-20 | TAP203 | LIS → EWR | May 20, 17:05 UTC | May 21, 01:05 UTC | 8h 0m |
| 2026-05-19 | TAP118 | POA → LIS | May 19, 23:00 UTC | May 20, 13:25 UTC | 14h 26m |
| 2026-05-19 | TAP118 | POA → LIS | May 19, 14:55 UTC | May 20, 13:25 UTC | 22h 31m |
| 2026-05-19 | TAP117 | LIS → POA | May 19, 13:55 UTC | May 20, 12:45 UTC | 22h 51m |
| 2026-05-19 | TAP088 | GRU → LIS | May 19, 00:10 UTC | May 19, 09:15 UTC | 9h 5m |
| 2026-05-18 | TAP089 | LIS → GRU | May 18, 12:15 UTC | May 18, 21:55 UTC | 9h 39m |
| 2026-05-17 | TAP011 | LIS → REC | May 17, 17:15 UTC | May 18, 09:10 UTC | 15h 55m |
| 2026-05-17 | TAP23SL | SFO → LIS | May 17, 04:20 UTC | May 17, 14:20 UTC | 10h 0m |
| 2026-05-16 | TAP237M | LIS → SFO | May 16, 13:15 UTC | May 17, 01:30 UTC | 12h 15m |
| 2026-05-15 | TAP012 | REC → LIS | May 15, 16:50 UTC | May 16, 08:51 UTC | 16h 1m |
| 2026-05-14 | TAP028 | FOR → LIS | May 14, 16:55 UTC | May 15, 10:50 UTC | 17h 55m |
| 2026-05-14 | TAP084 | GRU → LIS | May 14, 04:35 UTC | May 14, 13:30 UTC | 8h 55m |
| 2026-05-13 | TAP083 | LIS → GRU | May 13, 16:40 UTC | May 14, 02:35 UTC | 9h 55m |
| 2026-05-13 | TAP248 | LIS → ALG | May 13, 00:10 UTC | May 13, 10:50 UTC | 10h 40m |
| 2026-05-12 | TAP247 | LIS → LAX | May 12, 08:40 UTC | May 12, 20:05 UTC | 11h 25m |
| 2026-05-11 | TAP057 | LIS → BSB | May 11, 17:10 UTC | May 12, 05:40 UTC | 12h 30m |
| 2026-05-11 | TAP057 | LIS → BSB | May 11, 10:05 UTC | May 12, 05:40 UTC | 19h 35m |
| 2026-05-10 | TAP104 | CNF → LIS | May 10, 10:49 UTC | May 11, 05:40 UTC | 18h 50m |
| 2026-05-10 | TAP103 | LIS → CNF | May 10, 10:05 UTC | May 11, 05:40 UTC | 19h 35m |
| 2026-05-09 | TAP90EH | FNC → LIS | May 9, 14:45 UTC | May 9, 16:20 UTC | 1h 35m |
| 2026-05-09 | TAP89WT | LIS → FNC | May 9, 12:40 UTC | May 9, 12:50 UTC | 10m |
| 2026-05-09 | TAP89WT | LIS → FNC | May 9, 11:20 UTC | May 9, 11:50 UTC | 30m |
| 2026-05-09 | TAP036 | FOR → LIS | May 9, 02:00 UTC | May 9, 08:30 UTC | 6h 30m |
| 2026-05-08 | TAP035 | LIS → FOR | May 8, 17:05 UTC | May 9, 00:25 UTC | 7h 20m |
| 2026-05-08 | TAP084 | GRU → LIS | May 8, 04:25 UTC | May 8, 13:40 UTC | 9h 15m |
| 2026-05-07 | TAP083 | LIS → GRU | May 7, 17:40 UTC | May 8, 02:29 UTC | 8h 49m |
| 2026-05-07 | TAP083 | LIS → GRU | May 7, 16:30 UTC | May 7, 17:05 UTC | 35m |
| 2026-05-07 | TAP084 | GRU → LIS | May 7, 04:10 UTC | May 7, 13:20 UTC | 9h 10m |
| 2026-05-06 | TAP083 | LIS → GRU | May 6, 16:25 UTC | May 7, 02:25 UTC | 9h 59m |
| 2026-05-05 | TAP029 | LIS → SSA | May 5, 16:50 UTC | May 6, 10:20 UTC | 17h 30m |
| 2026-05-05 | TAP210 | JFK → LIS | May 5, 03:15 UTC | May 5, 09:15 UTC | 6h 0m |
| 2026-05-04 | TAP209K | LIS → JFK | May 4, 17:10 UTC | May 5, 00:25 UTC | 7h 16m |
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-TUK page for operator, model, and routing details .