sensors Mode-S transponder
4952A5
ICAO 24-bit transponder address · allocated to Portugal
Currently assigned to CS-TUE · AIRBUS A-330-900
- Hex
- 4952A5
- Octal
- 22251245
- Decimal
- 4,805,285
- Country
- PT
- Tail
- CS-TUE
- Type
- A339
- Flights observed
- 194
- Distinct callsigns
- 20
- Country
- PT
- Last broadcast
- Jul 26, 04:40 UTC
Current position
Country allocation
The ICAO 24-bit address 4952A5 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 |
|---|---|---|---|
| TAP088 | TAP Portugal | 17 | 2026-07-24 |
| TAP089 | TAP Portugal | 14 | 2026-07-21 |
| TAP074 | - | 12 | 2026-07-08 |
| TAP104 | - | 9 | 2026-07-06 |
| TAP297 | - | 8 | 2026-06-25 |
| TAP075 | - | 8 | 2026-06-13 |
| TAP298 | - | 7 | 2026-06-26 |
| TAP073 | - | 6 | 2026-06-18 |
| TAP210 | TAP Portugal | 5 | 2026-05-28 |
| TAP209K | TAP Portugal | 5 | 2026-05-27 |
| TAP087 | TAP Portugal | 5 | 2026-07-24 |
| TAP082 | TAP Portugal | 5 | 2026-07-25 |
| TAP057 | - | 5 | 2026-07-03 |
| TAP028 | - | 5 | 2026-07-13 |
| TAP243U | TAP Portugal | 4 | 2026-07-19 |
| TAP084 | - | 4 | 2026-07-13 |
| TAP083 | - | 4 | 2026-07-12 |
| TAP072 | - | 4 | 2026-06-19 |
| TAP011 | - | 4 | 2026-07-15 |
| TAP244 | TAP Portugal | 3 | 2026-07-20 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-25 | TAP082 | GRU → LIS | Jul 25, 18:50 UTC | Jul 26, 04:30 UTC | 9h 40m |
| 2026-07-24 | TAP087 | LIS → GRU | Jul 24, 22:45 UTC | Jul 25, 08:15 UTC | 9h 30m |
| 2026-07-24 | TAP088 | GRU → LIS | Jul 24, 00:25 UTC | Jul 24, 09:40 UTC | 9h 15m |
| 2026-07-23 | TAP093 | OPO → GRU | Jul 23, 12:30 UTC | Jul 23, 22:20 UTC | 9h 50m |
| 2026-07-22 | TAP294 | - | Jul 22, 22:35 UTC | Jul 23, 06:05 UTC | 7h 30m |
| 2026-07-22 | TAP293 | - | Jul 22, 12:40 UTC | Jul 22, 20:00 UTC | 7h 20m |
| 2026-07-22 | TAP094 | GRU → OPO | Jul 22, 00:20 UTC | Jul 22, 03:25 UTC | 3h 5m |
| 2026-07-21 | TAP089 | LIS → GRU | Jul 21, 11:50 UTC | Jul 21, 21:30 UTC | 9h 40m |
| 2026-07-21 | TAP3185 | LIS → VLN | Jul 21, 00:35 UTC | Jul 21, 09:00 UTC | 8h 25m |
| 2026-07-20 | TAP3185 | LIS → VLN | Jul 20, 12:00 UTC | Jul 21, 09:00 UTC | 20h 59m |
| 2026-07-20 | TAP244 | LIS → RAK | Jul 20, 00:20 UTC | Jul 20, 08:05 UTC | 7h 45m |
| 2026-07-19 | TAP243U | LIS → ORD | Jul 19, 12:25 UTC | Jul 19, 20:50 UTC | 8h 25m |
| 2026-07-19 | TAP088 | GRU → LIS | Jul 19, 00:55 UTC | Jul 19, 09:55 UTC | 9h 0m |
| 2026-07-18 | TAP093 | - | Jul 18, 12:55 UTC | Jul 18, 23:00 UTC | 10h 5m |
| 2026-07-18 | TAP078 | GIG → OPO | Jul 18, 01:30 UTC | Jul 18, 10:45 UTC | 9h 16m |
| 2026-07-17 | TAP077 | OPO → GIG | Jul 17, 13:29 UTC | Jul 17, 23:30 UTC | 10h 0m |
| 2026-07-17 | TAP094 | - | Jul 17, 00:30 UTC | Jul 17, 10:00 UTC | 9h 30m |
| 2026-07-16 | TAP089 | LIS → GRU | Jul 16, 12:44 UTC | Jul 16, 22:19 UTC | 9h 35m |
| 2026-07-16 | TAP012 | - | Jul 16, 01:40 UTC | Jul 16, 08:40 UTC | 7h 0m |
| 2026-07-15 | TAP011 | - | Jul 15, 23:25 UTC | Jul 15, 23:45 UTC | 20m |
| 2026-07-15 | TAP011 | - | Jul 15, 16:50 UTC | Jul 15, 18:35 UTC | 1h 45m |
| 2026-07-14 | TAP118 | - | Jul 14, 20:25 UTC | Jul 15, 13:30 UTC | 17h 4m |
| 2026-07-14 | TAP117 | - | Jul 14, 13:55 UTC | Jul 15, 13:15 UTC | 23h 19m |
| 2026-07-13 | TAP028 | LIS → LIS | Jul 13, 17:40 UTC | Jul 14, 11:05 UTC | 17h 25m |
| 2026-07-13 | TAP084 | - | Jul 13, 04:00 UTC | Jul 13, 13:15 UTC | 9h 15m |
| 2026-07-12 | TAP083 | - | Jul 12, 16:45 UTC | Jul 13, 02:15 UTC | 9h 30m |
| 2026-07-12 | TAP23SL | SFO → LIS | Jul 12, 03:50 UTC | Jul 12, 14:15 UTC | 10h 25m |
| 2026-07-11 | TAP237M | LIS → SFO | Jul 11, 14:00 UTC | Jul 12, 01:15 UTC | 11h 15m |
| 2026-07-11 | TAP088 | - | Jul 11, 00:35 UTC | Jul 11, 09:25 UTC | 8h 50m |
| 2026-07-10 | TAP089 | - | Jul 10, 12:40 UTC | Jul 10, 22:35 UTC | 9h 55m |
| 2026-07-09 | TAP242 | ORD → LIS | Jul 9, 22:30 UTC | Jul 10, 06:00 UTC | 7h 30m |
| 2026-07-09 | TAP243U | LIS → ORD | Jul 9, 08:45 UTC | Jul 9, 17:15 UTC | 8h 30m |
| 2026-07-08 | TAP074 | - | Jul 8, 19:00 UTC | Jul 9, 04:05 UTC | 9h 5m |
| 2026-07-08 | TAP2543 | LIS → GIG | Jul 8, 07:35 UTC | Jul 8, 17:00 UTC | 9h 25m |
| 2026-07-07 | TAP074 | - | Jul 7, 19:35 UTC | Jul 8, 04:25 UTC | 8h 50m |
| 2026-07-07 | TAP2543 | LIS → GIG | Jul 7, 07:55 UTC | Jul 7, 17:20 UTC | 9h 25m |
| 2026-07-06 | TAP104 | - | Jul 6, 11:20 UTC | Jul 7, 05:45 UTC | 18h 25m |
| 2026-07-06 | TAP104 | LIS → LIS | Jul 6, 09:50 UTC | Jul 7, 05:45 UTC | 19h 55m |
| 2026-07-05 | TAP104 | - | Jul 5, 11:20 UTC | Jul 6, 05:30 UTC | 18h 10m |
| 2026-07-05 | TAP104 | LIS → LIS | Jul 5, 09:55 UTC | Jul 6, 05:30 UTC | 19h 35m |
| 2026-07-04 | TAP224 | - | Jul 4, 21:25 UTC | Jul 5, 05:15 UTC | 7h 50m |
| 2026-07-04 | TAP22MI | LIS → MIA | Jul 4, 10:25 UTC | Jul 4, 18:45 UTC | 8h 20m |
| 2026-07-03 | TAP058 | - | Jul 3, 11:35 UTC | Jul 4, 05:50 UTC | 18h 15m |
| 2026-07-03 | TAP057 | LIS → LIS | Jul 3, 10:25 UTC | Jul 4, 05:50 UTC | 19h 25m |
| 2026-07-02 | TAP082 | - | Jul 2, 18:40 UTC | Jul 3, 03:45 UTC | 9h 5m |
| 2026-07-01 | TAP087 | LIS → GRU | Jul 1, 23:10 UTC | Jul 2, 08:45 UTC | 9h 35m |
| 2026-07-01 | TAP240 | SFO → TER | Jul 1, 02:55 UTC | Jul 1, 16:35 UTC | 13h 40m |
| 2026-06-30 | TAP241 | LIS → TER | Jun 30, 08:40 UTC | Jul 1, 00:00 UTC | 15h 20m |
| 2026-06-29 | TAP057 | LIS → LIS | Jun 29, 09:40 UTC | Jun 30, 05:05 UTC | 19h 26m |
| 2026-06-28 | TAP104 | - | Jun 28, 11:19 UTC | Jun 29, 05:34 UTC | 18h 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-TUE page for operator, model, and routing details .