sensors Mode-S transponder
4952AA
ICAO 24-bit transponder address · allocated to Portugal
Currently assigned to CS-TUJ · AIRBUS A-330-900
- Hex
- 4952AA
- Octal
- 22251252
- Decimal
- 4,805,290
- Country
- PT
- Tail
- CS-TUJ
- Type
- A339
- Flights observed
- 183
- Distinct callsigns
- 20
- Country
- PT
- Last broadcast
- 52m ago
Last known position
Country allocation
The ICAO 24-bit address 4952AA 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 |
|---|---|---|---|
| TAP082 | - | 11 | 2026-07-06 |
| TAP087 | - | 9 | 2026-07-05 |
| TAP104 | - | 8 | 2026-07-03 |
| TAP089 | - | 8 | 2026-07-12 |
| TAP088 | - | 8 | 2026-07-13 |
| TAP075 | - | 8 | 2026-07-11 |
| TAP89WT | - | 6 | 2026-07-14 |
| TAP23SL | - | 6 | 2026-07-05 |
| TAP237M | - | 6 | 2026-07-04 |
| TAP118 | TAP Portugal | 6 | 2026-05-10 |
| TAP074 | - | 6 | 2026-07-11 |
| TAP058 | - | 6 | 2026-07-02 |
| TAP22MI | - | 5 | 2026-06-14 |
| TAP224 | - | 5 | 2026-06-14 |
| TAP204A | TAP Portugal | 5 | 2026-06-12 |
| TAP203 | - | 5 | 2026-06-11 |
| TAP084 | TAP Portugal | 5 | 2026-05-26 |
| TAP057 | - | 5 | 2026-07-02 |
| TAP90EH | - | 4 | 2026-07-14 |
| TAP248 | - | 4 | 2026-07-07 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | TAP90EH | - | Jul 14, 13:40 UTC | Jul 14, 14:30 UTC | 50m |
| 2026-07-14 | TAP89WT | LIS → FNC | Jul 14, 10:55 UTC | Jul 14, 12:30 UTC | 1h 35m |
| 2026-07-13 | TAP072 | - | Jul 13, 23:35 UTC | Jul 14, 08:35 UTC | 9h 0m |
| 2026-07-13 | TAP073 | LIS → GIG | Jul 13, 11:30 UTC | Jul 13, 20:55 UTC | 9h 25m |
| 2026-07-13 | TAP088 | - | Jul 13, 00:05 UTC | Jul 13, 09:30 UTC | 9h 25m |
| 2026-07-12 | TAP089 | - | Jul 12, 11:40 UTC | Jul 12, 21:25 UTC | 9h 45m |
| 2026-07-11 | TAP074 | - | Jul 11, 18:50 UTC | Jul 12, 03:40 UTC | 8h 50m |
| 2026-07-11 | TAP075 | - | Jul 11, 08:10 UTC | Jul 11, 08:25 UTC | 15m |
| 2026-07-10 | TAP075 | - | Jul 10, 22:45 UTC | Jul 11, 07:20 UTC | 8h 35m |
| 2026-07-10 | TAP298 | - | Jul 10, 08:25 UTC | Jul 10, 15:45 UTC | 7h 20m |
| 2026-07-09 | TAP297 | - | Jul 9, 22:55 UTC | Jul 10, 05:50 UTC | 6h 55m |
| 2026-07-09 | TAP210 | - | Jul 9, 02:55 UTC | Jul 9, 09:05 UTC | 6h 10m |
| 2026-07-08 | TAP209K | LIS → JFK | Jul 8, 16:35 UTC | Jul 8, 23:25 UTC | 6h 50m |
| 2026-07-07 | TAP248 | LAX → LIS | Jul 7, 23:50 UTC | Jul 8, 10:20 UTC | 10h 30m |
| 2026-07-07 | TAP247 | LIS → LAX | Jul 7, 09:45 UTC | Jul 7, 21:00 UTC | 11h 15m |
| 2026-07-06 | TAP082 | - | Jul 6, 18:55 UTC | Jul 7, 04:05 UTC | 9h 10m |
| 2026-07-05 | TAP087 | - | Jul 5, 23:40 UTC | Jul 6, 09:35 UTC | 9h 55m |
| 2026-07-05 | TAP23SL | SFO → LIS | Jul 5, 02:50 UTC | Jul 5, 13:00 UTC | 10h 10m |
| 2026-07-04 | TAP237M | LIS → SFO | Jul 4, 13:00 UTC | Jul 5, 00:10 UTC | 11h 10m |
| 2026-07-03 | TAP104 | - | Jul 3, 10:35 UTC | Jul 4, 05:10 UTC | 18h 35m |
| 2026-07-03 | TAP104 | LIS → LIS | Jul 3, 09:20 UTC | Jul 4, 05:10 UTC | 19h 50m |
| 2026-07-02 | TAP058 | - | Jul 2, 10:35 UTC | Jul 3, 04:45 UTC | 18h 10m |
| 2026-07-02 | TAP057 | LIS → LIS | Jul 2, 09:30 UTC | Jul 3, 04:45 UTC | 19h 15m |
| 2026-07-01 | TAP082 | - | Jul 1, 18:50 UTC | Jul 2, 04:00 UTC | 9h 10m |
| 2026-06-30 | TAP087 | - | Jun 30, 23:40 UTC | Jul 1, 09:30 UTC | 9h 50m |
| 2026-06-29 | TAP074 | - | Jun 29, 19:05 UTC | Jun 30, 04:00 UTC | 8h 56m |
| 2026-06-28 | TAP075 | - | Jun 28, 23:44 UTC | Jun 29, 09:10 UTC | 9h 25m |
| 2026-06-27 | TAP074 | - | Jun 27, 18:49 UTC | Jun 28, 03:59 UTC | 9h 10m |
| 2026-06-27 | TAP075 | - | Jun 27, 13:49 UTC | Jun 27, 14:20 UTC | 30m |
| 2026-06-26 | TAP075 | - | Jun 26, 23:00 UTC | Jun 27, 08:05 UTC | 9h 5m |
| 2026-06-26 | TAP236 | - | Jun 26, 03:24 UTC | Jun 26, 13:30 UTC | 10h 5m |
| 2026-06-25 | TAP237M | LIS → SFO | Jun 25, 09:45 UTC | Jun 25, 21:25 UTC | 11h 40m |
| 2026-06-24 | TAP282 | - | Jun 24, 04:44 UTC | Jun 24, 17:45 UTC | 13h 0m |
| 2026-06-23 | TAP282 | - | Jun 23, 20:34 UTC | Jun 24, 17:45 UTC | 21h 10m |
| 2026-06-23 | TAP281 | LIS → LIS | Jun 23, 19:34 UTC | Jun 24, 17:45 UTC | 22h 10m |
| 2026-06-22 | TAP028 | LIS → LIS | Jun 22, 18:35 UTC | Jun 23, 11:59 UTC | 17h 25m |
| 2026-06-20 | TAP028 | LIS → LIS | Jun 20, 16:59 UTC | Jun 21, 10:49 UTC | 17h 50m |
| 2026-06-20 | TAP226 | - | Jun 20, 04:34 UTC | Jun 20, 12:09 UTC | 7h 35m |
| 2026-06-19 | TAP225V | LIS → MIA | Jun 19, 17:04 UTC | Jun 20, 01:34 UTC | 8h 30m |
| 2026-06-19 | TAP9034 | - | Jun 19, 02:09 UTC | Jun 19, 10:35 UTC | 8h 25m |
| 2026-06-18 | TAP9289 | - | Jun 18, 22:00 UTC | Jun 19, 00:10 UTC | 2h 9m |
| 2026-06-18 | TAP3201 | - | Jun 18, 06:10 UTC | Jun 18, 14:30 UTC | 8h 20m |
| 2026-06-17 | TAP282 | - | Jun 17, 16:00 UTC | Jun 17, 17:30 UTC | 1h 30m |
| 2026-06-16 | TAP281 | LIS → MPM | Jun 16, 18:55 UTC | Jun 17, 17:30 UTC | 22h 36m |
| 2026-06-16 | TAP3200 | - | Jun 16, 07:45 UTC | Jun 16, 15:40 UTC | 7h 55m |
| 2026-06-15 | TAP9288 | - | Jun 15, 21:35 UTC | Jun 15, 23:39 UTC | 2h 5m |
| 2026-06-15 | TAP9033 | - | Jun 15, 08:10 UTC | Jun 15, 18:35 UTC | 10h 25m |
| 2026-06-14 | TAP224 | - | Jun 14, 21:10 UTC | Jun 15, 04:50 UTC | 7h 40m |
| 2026-06-14 | TAP22MI | LIS → MIA | Jun 14, 10:10 UTC | Jun 14, 18:30 UTC | 8h 20m |
| 2026-06-13 | TAP082 | - | Jun 13, 18:45 UTC | Jun 14, 04:00 UTC | 9h 15m |
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-TUJ page for operator, model, and routing details .