sensors Mode-S transponder
4952AD
ICAO 24-bit transponder address · allocated to Portugal
Currently assigned to CS-TUM · AIRBUS A-330-900
- Hex
- 4952AD
- Octal
- 22251255
- Decimal
- 4,805,293
- Country
- PT
- Tail
- CS-TUM
- Type
- A339
- Flights observed
- 105
- Distinct callsigns
- 20
- Country
- PT
- Last broadcast
- 30m ago
Last known position
Country allocation
The ICAO 24-bit address 4952AD 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 |
|---|---|---|---|
| TAP094 | TAP Portugal | 14 | 2026-05-06 |
| TAP093 | TAP Portugal | 7 | 2026-05-05 |
| TAP089 | TAP Portugal | 7 | 2026-05-27 |
| TAP204A | - | 5 | 2026-04-14 |
| TAP203 | TAP Portugal | 5 | 2026-04-13 |
| TAP078 | TAP Portugal | 5 | 2026-05-05 |
| TAP077 | TAP Portugal | 5 | 2026-05-04 |
| TAP298 | - | 4 | 2026-05-12 |
| TAP297 | - | 4 | 2026-05-12 |
| TAP087 | TAP Portugal | 4 | 2026-05-29 |
| TAP088 | TAP Portugal | 3 | 2026-05-28 |
| TAP082 | TAP Portugal | 3 | 2026-05-23 |
| TAP058 | TAP Portugal | 3 | 2026-05-14 |
| TAP057 | TAP Portugal | 3 | 2026-05-15 |
| TAP3929 | - | 2 | 2026-05-24 |
| TAP294 | - | 2 | 2026-05-03 |
| TAP293 | - | 2 | 2026-05-03 |
| TAP282 | TAP Portugal | 2 | 2026-05-11 |
| TAP22MI | TAP Portugal | 2 | 2026-05-13 |
| TAP224 | TAP Portugal | 2 | 2026-05-13 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | TAP087 | LIS → GRU | May 29, 22:55 UTC | May 30, 00:50 UTC | 1h 55m |
| 2026-05-28 | TAP118 | POA → LIS | May 28, 22:15 UTC | May 29, 12:05 UTC | 13h 50m |
| 2026-05-28 | TAP118 | POA → LIS | May 28, 13:20 UTC | May 29, 12:05 UTC | 22h 45m |
| 2026-05-28 | TAP117 | LIS → POA | May 28, 13:10 UTC | May 29, 11:00 UTC | 21h 50m |
| 2026-05-28 | TAP088 | GRU → LIS | May 28, 00:05 UTC | May 28, 09:30 UTC | 9h 25m |
| 2026-05-27 | TAP089 | LIS → GRU | May 27, 11:50 UTC | May 27, 21:40 UTC | 9h 50m |
| 2026-05-27 | TAP088 | GRU → LIS | May 27, 00:14 UTC | May 27, 09:10 UTC | 8h 55m |
| 2026-05-26 | TAP089 | LIS → GRU | May 26, 12:00 UTC | May 26, 21:55 UTC | 9h 55m |
| 2026-05-26 | TAP088 | GRU → LIS | May 26, 00:14 UTC | May 26, 08:59 UTC | 8h 45m |
| 2026-05-25 | TAP089 | LIS → GRU | May 25, 12:45 UTC | May 25, 22:25 UTC | 9h 39m |
| 2026-05-25 | TAP210 | JFK → LIS | May 25, 03:30 UTC | May 25, 10:00 UTC | 6h 30m |
| 2026-05-24 | TAP209K | LIS → JFK | May 24, 18:00 UTC | May 24, 23:46 UTC | 5h 46m |
| 2026-05-24 | TAP3928 | - | May 24, 14:00 UTC | May 24, 14:40 UTC | 40m |
| 2026-05-24 | TAP3929 | - | May 24, 10:30 UTC | May 24, 10:40 UTC | 10m |
| 2026-05-24 | TAP3929 | - | May 24, 08:40 UTC | May 24, 09:15 UTC | 35m |
| 2026-05-23 | TAP082 | GRU → LIS | May 23, 18:40 UTC | May 24, 03:40 UTC | 9h 0m |
| 2026-05-22 | TAP087 | LIS → GRU | May 22, 23:45 UTC | May 23, 09:50 UTC | 10h 4m |
| 2026-05-22 | TAP2624 | EWR → OPO | May 22, 08:10 UTC | May 22, 14:15 UTC | 6h 5m |
| 2026-05-21 | TAP209K | LIS → JFK | May 21, 16:30 UTC | May 21, 23:55 UTC | 7h 25m |
| 2026-05-20 | TAP011 | LIS → REC | May 20, 17:10 UTC | May 21, 09:10 UTC | 16h 0m |
| 2026-05-17 | TAP028 | FOR → LIS | May 17, 17:05 UTC | May 18, 10:55 UTC | 17h 50m |
| 2026-05-16 | TAP072 | GIG → LIS | May 16, 23:40 UTC | May 17, 08:30 UTC | 8h 50m |
| 2026-05-16 | TAP073 | LIS → GIG | May 16, 11:31 UTC | May 16, 21:15 UTC | 9h 44m |
| 2026-05-15 | TAP057 | LIS → BSB | May 15, 11:40 UTC | May 16, 06:06 UTC | 18h 25m |
| 2026-05-15 | TAP057 | LIS → BSB | May 15, 10:40 UTC | May 16, 06:06 UTC | 19h 25m |
| 2026-05-14 | TAP058 | BSB → LIS | May 14, 09:20 UTC | May 15, 05:05 UTC | 19h 45m |
| 2026-05-13 | TAP224 | MIA → LIS | May 13, 21:25 UTC | May 14, 04:55 UTC | 7h 30m |
| 2026-05-13 | TAP22MI | LIS → MIA | May 13, 09:50 UTC | May 13, 18:35 UTC | 8h 45m |
| 2026-05-12 | TAP298 | - | May 12, 09:25 UTC | May 12, 17:10 UTC | 7h 45m |
| 2026-05-12 | TAP297 | - | May 12, 04:05 UTC | May 12, 06:00 UTC | 1h 55m |
| 2026-05-11 | TAP282 | MPM → LIS | May 11, 16:15 UTC | May 11, 17:50 UTC | 1h 36m |
| 2026-05-10 | TAP282 | MPM → LIS | May 10, 19:30 UTC | May 11, 17:50 UTC | 22h 21m |
| 2026-05-10 | TAP83RS | FCO → LIS | May 10, 12:34 UTC | May 10, 15:29 UTC | 2h 55m |
| 2026-05-10 | TAP832 | LIS → FCO | May 10, 08:20 UTC | May 10, 10:45 UTC | 2h 25m |
| 2026-05-09 | TAP074 | GIG → LIS | May 9, 18:55 UTC | May 10, 03:30 UTC | 8h 35m |
| 2026-05-08 | TAP075 | LIS → GIG | May 8, 23:05 UTC | May 9, 08:40 UTC | 9h 35m |
| 2026-05-08 | TAP298 | - | May 8, 08:29 UTC | May 8, 16:00 UTC | 7h 30m |
| 2026-05-07 | TAP297 | - | May 7, 22:54 UTC | May 8, 05:54 UTC | 7h 0m |
| 2026-05-07 | TAP226 | MIA → LIS | May 7, 08:10 UTC | May 7, 15:55 UTC | 7h 45m |
| 2026-05-06 | TAP225V | LIS → MIA | May 6, 18:30 UTC | May 7, 03:30 UTC | 9h 0m |
| 2026-05-06 | TAP9242 | TLS → LIS | May 6, 11:55 UTC | May 6, 12:35 UTC | 40m |
| 2026-05-06 | TAP094 | GRU → OPO | May 6, 00:35 UTC | May 6, 09:50 UTC | 9h 15m |
| 2026-05-05 | TAP093 | OPO → GRU | May 5, 12:10 UTC | May 5, 22:40 UTC | 10h 30m |
| 2026-05-05 | TAP078 | GIG → OPO | May 5, 00:55 UTC | May 5, 09:40 UTC | 8h 45m |
| 2026-05-04 | TAP077 | OPO → GIG | May 4, 12:20 UTC | May 4, 22:25 UTC | 10h 6m |
| 2026-05-03 | TAP294 | - | May 3, 22:34 UTC | May 4, 06:15 UTC | 7h 40m |
| 2026-05-03 | TAP293 | - | May 3, 13:05 UTC | May 3, 20:15 UTC | 7h 10m |
| 2026-05-03 | TAP094 | GRU → OPO | May 3, 02:10 UTC | May 3, 09:45 UTC | 7h 34m |
| 2026-05-03 | TAP094 | GRU → OPO | May 3, 00:15 UTC | May 3, 02:05 UTC | 1h 50m |
| 2026-05-02 | TAP089 | LIS → GRU | May 2, 12:15 UTC | May 2, 22:00 UTC | 9h 45m |
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-TUM page for operator, model, and routing details .