Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

4952A8

ICAO 24-bit transponder address · allocated to Portugal

Currently assigned to CS-TUH · AIRBUS A-330-900

Hex
4952A8
Octal
22251250
Decimal
4,805,288
Country
PT
Tail
CS-TUH
Type
A339
No current signal · last broadcast 5h ago
Flights observed
189
Distinct callsigns
20
Country
PT
Last broadcast
5h ago

Last known position

Most recent position reported by Mode-S 4952A8.

Country allocation

The ICAO 24-bit address 4952A8 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
TAP089 - 11 2026-07-02
TAP088 - 11 2026-07-03
TAP057 - 11 2026-06-16
TAP104 - 8 2026-06-17
TAP058 - 8 2026-06-15
TAP89WT TAP Portugal 7 2026-05-31
TAP22MI - 6 2026-07-07
TAP224 - 6 2026-07-07
TAP3177 - 5 2026-06-22
TAP247 TAP Portugal 5 2026-04-17
TAP244 - 5 2026-07-08
TAP243U - 5 2026-07-08
TAP087 - 5 2026-07-12
TAP082 - 5 2026-07-13
TAP074 - 5 2026-07-09
TAP90EH TAP Portugal 4 2026-05-31
TAP204A TAP Portugal 4 2026-06-03
TAP203 TAP Portugal 4 2026-06-02
TAP011 - 4 2026-07-06
TAP3178 - 3 2026-06-22

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-13 TAP082 - Jul 13, 18:45 UTCJul 14, 03:55 UTC9h 10m
2026-07-12 TAP087 - Jul 12, 23:20 UTCJul 13, 09:15 UTC9h 55m
2026-07-12 TAP084 - Jul 12, 04:15 UTCJul 12, 13:45 UTC9h 30m
2026-07-11 TAP083 - Jul 11, 16:25 UTCJul 12, 02:15 UTC9h 50m
2026-07-11 TAP110 - Jul 11, 04:10 UTCJul 11, 13:45 UTC9h 35m
2026-07-10 TAP109 - Jul 10, 12:25 UTCJul 10, 23:00 UTC10h 35m
2026-07-09 TAP074 - Jul 9, 19:40 UTCJul 10, 04:30 UTC8h 50m
2026-07-09 TAP2543 - Jul 9, 08:25 UTCJul 9, 17:35 UTC9h 10m
2026-07-08 TAP244 PWK → LIS Jul 8, 22:50 UTCJul 9, 06:20 UTC7h 30m
2026-07-08 TAP243U LIS → ORD Jul 8, 10:55 UTCJul 8, 19:05 UTC8h 10m
2026-07-07 TAP224 - Jul 7, 20:55 UTCJul 8, 04:30 UTC7h 35m
2026-07-07 TAP22MI LIS → MIA Jul 7, 10:20 UTCJul 7, 18:25 UTC8h 5m
2026-07-07 TAP012 - Jul 7, 01:30 UTCJul 7, 08:15 UTC6h 45m
2026-07-06 TAP011 - Jul 6, 16:30 UTCJul 6, 23:35 UTC7h 5m
2026-07-06 TAP084 - Jul 6, 04:00 UTCJul 6, 13:00 UTC9h 0m
2026-07-05 TAP083 LIS → GRU Jul 5, 16:20 UTCJul 6, 02:05 UTC9h 45m
2026-07-04 TAP028 LIS → LIS Jul 4, 17:15 UTCJul 5, 10:50 UTC17h 35m
2026-07-04 TAP244 - Jul 4, 06:40 UTCJul 4, 07:00 UTC20m
2026-07-03 TAP244 - Jul 3, 23:30 UTCJul 4, 06:35 UTC7h 5m
2026-07-03 TAP243U LIS → ORD Jul 3, 11:55 UTCJul 3, 20:50 UTC8h 55m
2026-07-03 TAP088 - Jul 3, 00:15 UTCJul 3, 09:30 UTC9h 15m
2026-07-02 TAP089 - Jul 2, 12:35 UTCJul 2, 22:10 UTC9h 35m
2026-07-02 TAP088 - Jul 2, 00:00 UTCJul 2, 09:15 UTC9h 15m
2026-07-01 TAP089 - Jul 1, 11:45 UTCJul 1, 21:20 UTC9h 35m
2026-07-01 TAP088 - Jul 1, 00:00 UTCJul 1, 09:10 UTC9h 10m
2026-06-30 TAP089 - Jun 30, 12:00 UTCJun 30, 21:35 UTC9h 35m
2026-06-30 TAP088 - Jun 30, 00:00 UTCJun 30, 09:05 UTC9h 6m
2026-06-29 TAP089 - Jun 29, 12:24 UTCJun 29, 22:00 UTC9h 35m
2026-06-29 TAP088 - Jun 29, 00:00 UTCJun 29, 09:00 UTC9h 0m
2026-06-28 TAP089 - Jun 28, 11:50 UTCJun 28, 21:20 UTC9h 30m
2026-06-27 TAP224 - Jun 27, 20:49 UTCJun 28, 04:20 UTC7h 30m
2026-06-27 TAP22MI LIS → MIA Jun 27, 10:10 UTCJun 27, 18:20 UTC8h 10m
2026-06-26 TAP082 - Jun 26, 18:39 UTCJun 27, 03:55 UTC9h 15m
2026-06-25 TAP087 - Jun 25, 23:14 UTCJun 26, 09:00 UTC9h 45m
2026-06-25 TAP226 - Jun 25, 07:59 UTCJun 25, 15:54 UTC7h 55m
2026-06-24 TAP225V LIS → MIA Jun 24, 18:44 UTCJun 25, 03:04 UTC8h 20m
2026-06-24 TAP298 - Jun 24, 08:35 UTCJun 24, 15:59 UTC7h 25m
2026-06-23 TAP297 - Jun 23, 22:44 UTCJun 24, 05:49 UTC7h 5m
2026-06-22 TAP3178 - Jun 22, 18:19 UTCJun 23, 08:20 UTC14h 0m
2026-06-22 TAP3178 - Jun 22, 12:05 UTCJun 23, 08:20 UTC20h 15m
2026-06-22 TAP3177 - Jun 22, 11:35 UTCJun 23, 08:00 UTC20h 25m
2026-06-22 TAP012 - Jun 22, 02:10 UTCJun 22, 09:10 UTC7h 0m
2026-06-22 TAP011 - Jun 22, 00:04 UTCJun 22, 00:24 UTC20m
2026-06-21 TAP011 - Jun 21, 17:15 UTCJun 21, 19:09 UTC1h 55m
2026-06-20 TAP296 - Jun 20, 22:35 UTCJun 21, 05:49 UTC7h 15m
2026-06-20 TAP295 - Jun 20, 12:54 UTCJun 20, 14:14 UTC1h 20m
2026-06-20 TAP088 - Jun 20, 00:19 UTCJun 20, 09:54 UTC9h 35m
2026-06-19 TAP089 - Jun 19, 12:49 UTCJun 19, 22:30 UTC9h 40m
2026-06-19 TAP242 ORD → LIS Jun 19, 03:20 UTCJun 19, 10:19 UTC7h 0m
2026-06-18 TAP243U LIS → ORD Jun 18, 08:45 UTCJun 18, 17:15 UTC8h 30m

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-TUH page for operator, model, and routing details .

Mode-S 4952A8 frequently asked

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