Apparatus

Try JFK, AAL1290, BAW, or N225AN.

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
No current signal · last broadcast 1h ago
Flights observed
175
Distinct callsigns
20
Country
PT
Last broadcast
1h ago

Last known position

Most recent position reported by Mode-S 4952AD.

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
TAP057 - 11 2026-07-11
TAP22MI - 9 2026-07-10
TAP224 - 8 2026-07-10
TAP089 TAP Portugal 8 2026-06-15
TAP093 TAP Portugal 7 2026-05-05
TAP298 - 5 2026-06-19
TAP297 - 5 2026-06-18
TAP204A - 5 2026-04-14
TAP203 TAP Portugal 5 2026-04-13
TAP087 - 5 2026-06-20
TAP082 - 5 2026-06-21
TAP078 TAP Portugal 5 2026-05-05
TAP077 TAP Portugal 5 2026-05-04
TAP209K - 4 2026-06-13
TAP118 - 4 2026-06-16
TAP088 - 4 2026-06-16
TAP058 - 4 2026-07-09
TAP89WT - 3 2026-07-12
TAP282 - 3 2026-06-20

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-14 TAP012 - Jul 14, 01:20 UTCJul 14, 01:45 UTC25m
2026-07-13 TAP011 - Jul 13, 16:20 UTCJul 13, 23:30 UTC7h 10m
2026-07-13 TAP226 - Jul 13, 05:01 UTCJul 13, 12:45 UTC7h 45m
2026-07-12 TAP225V - Jul 12, 18:05 UTCJul 13, 02:20 UTC8h 15m
2026-07-12 TAP90EH - Jul 12, 14:30 UTCJul 12, 15:25 UTC55m
2026-07-12 TAP89WT - Jul 12, 11:05 UTCJul 12, 11:50 UTC45m
2026-07-11 TAP057 - Jul 11, 09:20 UTCJul 12, 04:55 UTC19h 35m
2026-07-11 TAP057 LIS → LIS Jul 11, 09:05 UTCJul 12, 04:55 UTC19h 50m
2026-07-10 TAP224 - Jul 10, 21:15 UTCJul 11, 05:01 UTC7h 45m
2026-07-10 TAP22MI LIS → MIA Jul 10, 10:10 UTCJul 10, 18:35 UTC8h 25m
2026-07-09 TAP058 - Jul 9, 11:20 UTCJul 10, 05:20 UTC18h 0m
2026-07-09 TAP057 LIS → LIS Jul 9, 09:30 UTCJul 10, 05:20 UTC19h 50m
2026-07-08 TAP057 - Jul 8, 11:20 UTCJul 9, 05:50 UTC18h 30m
2026-07-08 TAP057 LIS → LIS Jul 8, 10:40 UTCJul 9, 05:50 UTC19h 10m
2026-07-07 TAP9140 DFW → LIS Jul 7, 20:50 UTCJul 8, 05:15 UTC8h 25m
2026-07-07 TAP9361 LIS → DFW Jul 7, 08:10 UTCJul 7, 17:40 UTC9h 30m
2026-07-06 TAP057 LIS → LIS Jul 6, 09:20 UTCJul 7, 05:15 UTC19h 55m
2026-07-05 TAP224 - Jul 5, 21:20 UTCJul 6, 05:10 UTC7h 50m
2026-07-05 TAP22MI - Jul 5, 17:45 UTCJul 5, 18:10 UTC25m
2026-07-05 TAP22MI - Jul 5, 10:10 UTCJul 5, 10:45 UTC35m
2026-07-04 TAP296 - Jul 4, 22:40 UTCJul 5, 05:45 UTC7h 5m
2026-07-04 TAP295 - Jul 4, 12:50 UTCJul 4, 20:00 UTC7h 10m
2026-07-03 TAP296 - Jul 3, 22:35 UTCJul 4, 05:45 UTC7h 10m
2026-07-03 TAP295 - Jul 3, 13:10 UTCJul 3, 20:15 UTC7h 5m
2026-07-02 TAP23SL SFO → LIS Jul 2, 00:35 UTCJul 2, 10:50 UTC10h 15m
2026-07-01 TAP237M LIS → SFO Jul 1, 09:10 UTCJul 1, 20:35 UTC11h 25m
2026-06-30 TAP224 - Jun 30, 20:50 UTCJul 1, 04:35 UTC7h 45m
2026-06-30 TAP22MI LIS → MIA Jun 30, 09:55 UTCJun 30, 18:15 UTC8h 20m
2026-06-29 TAP224 - Jun 29, 20:49 UTCJun 30, 04:30 UTC7h 41m
2026-06-29 TAP22MI LIS → MIA Jun 29, 10:10 UTCJun 29, 18:34 UTC8h 25m
2026-06-28 TAP9038 - Jun 28, 21:24 UTCJun 29, 05:15 UTC7h 50m
2026-06-25 TAP9037 LIS → MIA Jun 25, 08:40 UTCJun 25, 16:55 UTC8h 15m
2026-06-24 TAP224 - Jun 24, 20:54 UTCJun 25, 04:29 UTC7h 35m
2026-06-24 TAP22MI LIS → MIA Jun 24, 09:55 UTCJun 24, 18:09 UTC8h 15m
2026-06-23 TAP057 - Jun 23, 09:20 UTCJun 24, 05:09 UTC19h 50m
2026-06-22 TAP057 LIS → LIS Jun 22, 09:30 UTCJun 23, 05:09 UTC19h 40m
2026-06-21 TAP082 - Jun 21, 18:44 UTCJun 22, 04:00 UTC9h 15m
2026-06-20 TAP087 - Jun 20, 22:45 UTCJun 21, 08:15 UTC9h 30m
2026-06-20 TAP282 - Jun 20, 16:55 UTCJun 20, 18:14 UTC1h 20m
2026-06-19 TAP281 LIS → LIS Jun 19, 19:49 UTCJun 20, 18:14 UTC22h 25m
2026-06-19 TAP298 - Jun 19, 08:20 UTCJun 19, 15:49 UTC7h 30m
2026-06-18 TAP297 - Jun 18, 22:55 UTCJun 19, 05:59 UTC7h 4m
2026-06-18 TAP084 - Jun 18, 04:05 UTCJun 18, 13:15 UTC9h 10m
2026-06-17 TAP083 - Jun 17, 16:20 UTCJun 18, 02:10 UTC9h 50m
2026-06-16 TAP118 - Jun 16, 20:10 UTCJun 17, 13:25 UTC17h 15m
2026-06-16 TAP118 - Jun 16, 15:20 UTCJun 17, 13:25 UTC22h 6m
2026-06-16 TAP117 - Jun 16, 13:44 UTCJun 17, 13:15 UTC23h 31m
2026-06-16 TAP088 - Jun 16, 00:29 UTCJun 16, 09:50 UTC9h 20m
2026-06-15 TAP089 LIS → GRU Jun 15, 12:35 UTCJun 15, 22:25 UTC9h 50m
2026-06-14 TAP210 JFK → LIS Jun 14, 02:55 UTCJun 14, 09:00 UTC6h 6m

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 .

Mode-S 4952AD frequently asked

What is Mode-S code 4952AD?
4952AD is an ICAO 24-bit transponder address. Allocated to Portugal. Assigned to CS-TUM.
Where is Mode-S 4952AD registered?
Mode-S code 4952AD is allocated to Portugal (PT). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 4952AD broadcasting right now?
No active broadcast right now. Last signal was 1h ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 4952AD, octal 22251255, decimal 4,805,293.
What flights does 4952AD operate?
Mode-S 4952AD has broadcast 20 distinct callsigns, including TAP094, TAP057, TAP22MI, TAP224, TAP089.