sensors Mode-S transponder
4952A9
ICAO 24-bit transponder address · allocated to Portugal
Currently assigned to CS-TUI · AIRBUS A-330-900
- Hex
- 4952A9
- Octal
- 22251251
- Decimal
- 4,805,289
- Country
- PT
- Tail
- CS-TUI
- Type
- A339
- Flights observed
- 206
- Distinct callsigns
- 20
- Country
- PT
- Last broadcast
- Jul 26, 20:15 UTC
Last known position
Country allocation
The ICAO 24-bit address 4952A9 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 |
|---|---|---|---|
| TAP224 | - | 14 | 2026-07-12 |
| TAP22MI | - | 13 | 2026-07-12 |
| TAP104 | TAP Portugal | 11 | 2026-05-24 |
| TAP087 | TAP Portugal | 9 | 2026-07-17 |
| TAP298 | - | 8 | 2026-07-01 |
| TAP118 | TAP Portugal | 8 | 2026-07-25 |
| TAP297 | - | 7 | 2026-06-30 |
| TAP247 | TAP Portugal | 7 | 2026-07-24 |
| TAP082 | TAP Portugal | 7 | 2026-07-18 |
| TAP074 | TAP Portugal | 7 | 2026-07-23 |
| TAP058 | TAP Portugal | 7 | 2026-07-19 |
| TAP057 | - | 7 | 2026-07-19 |
| TAP248 | TAP Portugal | 6 | 2026-07-25 |
| TAP210 | - | 6 | 2026-07-07 |
| TAP209K | - | 6 | 2026-07-06 |
| TAP089 | - | 6 | 2026-07-14 |
| TAP088 | TAP Portugal | 6 | 2026-07-16 |
| TAP282 | TAP Portugal | 4 | 2026-05-16 |
| TAP244 | - | 4 | 2026-06-27 |
| TAP243U | - | 4 | 2026-06-27 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | TAP281 | LIS → MPM | Jul 26, 19:00 UTC | Jul 26, 20:15 UTC | 1h 15m |
| 2026-07-25 | TAP118 | POA → LIS | Jul 25, 21:05 UTC | Jul 26, 15:05 UTC | 18h 1m |
| 2026-07-25 | TAP117 | LIS → POA | Jul 25, 14:45 UTC | Jul 26, 14:15 UTC | 23h 31m |
| 2026-07-25 | TAP248 | LIS → ALG | Jul 25, 00:05 UTC | Jul 25, 10:35 UTC | 10h 30m |
| 2026-07-24 | TAP247 | LIS → LAX | Jul 24, 09:30 UTC | Jul 24, 20:55 UTC | 11h 25m |
| 2026-07-23 | TAP074 | GIG → LIS | Jul 23, 18:55 UTC | Jul 24, 04:00 UTC | 9h 5m |
| 2026-07-23 | TAP2545 | LIS → GIG | Jul 23, 07:40 UTC | Jul 23, 16:55 UTC | 9h 15m |
| 2026-07-22 | TAP074 | GIG → LIS | Jul 22, 19:20 UTC | Jul 23, 03:50 UTC | 8h 30m |
| 2026-07-22 | TAP074 | GIG → LIS | Jul 22, 02:45 UTC | Jul 23, 02:15 UTC | 23h 30m |
| 2026-07-22 | TAP074 | GIG → LIS | Jul 22, 00:25 UTC | Jul 22, 21:45 UTC | 21h 20m |
| 2026-07-21 | TAP075 | LIS → GIG | Jul 21, 23:10 UTC | Jul 22, 21:45 UTC | 22h 35m |
| 2026-07-19 | TAP058 | BSB → LIS | Jul 19, 10:35 UTC | Jul 20, 04:45 UTC | 18h 10m |
| 2026-07-19 | TAP057 | LIS → LIS | Jul 19, 09:20 UTC | Jul 20, 04:45 UTC | 19h 25m |
| 2026-07-18 | TAP082 | GRU → LIS | Jul 18, 18:40 UTC | Jul 19, 03:50 UTC | 9h 10m |
| 2026-07-17 | TAP087 | LIS → GRU | Jul 17, 23:35 UTC | Jul 18, 09:35 UTC | 10h 1m |
| 2026-07-16 | TAP088 | GRU → LIS | Jul 16, 23:59 UTC | Jul 17, 09:15 UTC | 9h 15m |
| 2026-07-16 | TAP093 | - | Jul 16, 18:44 UTC | Jul 16, 22:05 UTC | 3h 20m |
| 2026-07-16 | TAP093 | - | Jul 16, 11:54 UTC | Jul 16, 13:00 UTC | 1h 5m |
| 2026-07-15 | TAP294 | - | Jul 15, 22:35 UTC | Jul 16, 06:10 UTC | 7h 35m |
| 2026-07-15 | TAP293 | - | Jul 15, 12:40 UTC | Jul 15, 20:05 UTC | 7h 25m |
| 2026-07-15 | TAP094 | - | Jul 15, 00:35 UTC | Jul 15, 10:10 UTC | 9h 35m |
| 2026-07-14 | TAP089 | LIS → GRU | Jul 14, 12:35 UTC | Jul 14, 22:20 UTC | 9h 45m |
| 2026-07-13 | TAP3185 | - | Jul 13, 19:10 UTC | Jul 14, 10:20 UTC | 15h 10m |
| 2026-07-13 | TAP3185 | - | Jul 13, 12:20 UTC | Jul 14, 10:20 UTC | 22h 0m |
| 2026-07-13 | TAP3185 | - | Jul 13, 12:05 UTC | Jul 14, 10:15 UTC | 22h 10m |
| 2026-07-12 | TAP224 | - | Jul 12, 20:40 UTC | Jul 13, 04:15 UTC | 7h 35m |
| 2026-07-12 | TAP22MI | LIS → MIA | Jul 12, 10:05 UTC | Jul 12, 18:20 UTC | 8h 15m |
| 2026-07-11 | TAP103 | - | Jul 11, 10:20 UTC | Jul 12, 05:25 UTC | 19h 5m |
| 2026-07-11 | TAP103 | LIS → LIS | Jul 11, 09:45 UTC | Jul 12, 05:25 UTC | 19h 40m |
| 2026-07-09 | TAP029 | LIS → LIS | Jul 9, 17:20 UTC | Jul 10, 10:50 UTC | 17h 30m |
| 2026-07-09 | TAP084 | - | Jul 9, 04:00 UTC | Jul 9, 13:20 UTC | 9h 20m |
| 2026-07-08 | TAP083 | - | Jul 8, 16:25 UTC | Jul 9, 02:05 UTC | 9h 40m |
| 2026-07-08 | TAP118 | - | Jul 8, 03:35 UTC | Jul 8, 13:20 UTC | 9h 45m |
| 2026-07-07 | TAP117 | - | Jul 7, 14:15 UTC | Jul 8, 00:40 UTC | 10h 25m |
| 2026-07-07 | TAP210 | JFK → LIS | Jul 7, 03:25 UTC | Jul 7, 09:55 UTC | 6h 30m |
| 2026-07-06 | TAP209K | LIS → JFK | Jul 6, 16:45 UTC | Jul 6, 23:55 UTC | 7h 10m |
| 2026-07-06 | TAP210 | JFK → LIS | Jul 6, 04:55 UTC | Jul 6, 11:05 UTC | 6h 10m |
| 2026-07-05 | TAP209K | LIS → JFK | Jul 5, 16:45 UTC | Jul 5, 23:45 UTC | 7h 0m |
| 2026-07-05 | TAP248 | LAX → LIS | Jul 5, 00:55 UTC | Jul 5, 11:00 UTC | 10h 5m |
| 2026-07-04 | TAP247 | - | Jul 4, 10:20 UTC | Jul 4, 21:15 UTC | 10h 55m |
| 2026-07-03 | TAP074 | - | Jul 3, 18:50 UTC | Jul 4, 03:40 UTC | 8h 50m |
| 2026-07-02 | TAP075 | - | Jul 2, 22:55 UTC | Jul 3, 07:55 UTC | 9h 0m |
| 2026-07-02 | TAP226 | - | Jul 2, 08:05 UTC | Jul 2, 16:10 UTC | 8h 5m |
| 2026-07-01 | TAP225V | LIS → MIA | Jul 1, 18:30 UTC | Jul 2, 02:45 UTC | 8h 15m |
| 2026-07-01 | TAP298 | - | Jul 1, 08:35 UTC | Jul 1, 15:45 UTC | 7h 10m |
| 2026-06-30 | TAP297 | - | Jun 30, 23:05 UTC | Jul 1, 06:05 UTC | 7h 0m |
| 2026-06-30 | TAP298 | - | Jun 30, 09:35 UTC | Jun 30, 16:55 UTC | 7h 20m |
| 2026-06-29 | TAP297 | - | Jun 29, 22:55 UTC | Jun 30, 05:50 UTC | 6h 56m |
| 2026-06-29 | TAP298 | - | Jun 29, 09:29 UTC | Jun 29, 16:55 UTC | 7h 25m |
| 2026-06-28 | TAP297 | - | Jun 28, 22:49 UTC | Jun 29, 05:45 UTC | 6h 55m |
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-TUI page for operator, model, and routing details .