Apparatus

Try JFK, AAL1290, BAW, or N225AN.

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

Last known position

Most recent position reported by Mode-S 4952A5.

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 - 15 2026-07-11
TAP089 - 12 2026-07-10
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
TAP057 - 5 2026-07-03
TAP028 - 5 2026-07-13
TAP087 - 4 2026-07-01
TAP084 - 4 2026-07-13
TAP083 - 4 2026-07-12
TAP082 - 4 2026-07-02
TAP072 - 4 2026-06-19
TAP243U - 3 2026-07-09
TAP22MI - 3 2026-07-04
TAP224 - 3 2026-07-04

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-14 TAP117 - Jul 14, 13:55 UTCJul 14, 23:15 UTC9h 19m
2026-07-13 TAP028 LIS → LIS Jul 13, 17:40 UTCJul 14, 11:05 UTC17h 25m
2026-07-13 TAP084 - Jul 13, 04:00 UTCJul 13, 13:15 UTC9h 15m
2026-07-12 TAP083 - Jul 12, 16:45 UTCJul 13, 02:15 UTC9h 30m
2026-07-12 TAP23SL SFO → LIS Jul 12, 03:50 UTCJul 12, 14:15 UTC10h 25m
2026-07-11 TAP237M LIS → SFO Jul 11, 14:00 UTCJul 12, 01:15 UTC11h 15m
2026-07-11 TAP088 - Jul 11, 00:35 UTCJul 11, 09:25 UTC8h 50m
2026-07-10 TAP089 - Jul 10, 12:40 UTCJul 10, 22:35 UTC9h 55m
2026-07-09 TAP242 ORD → LIS Jul 9, 22:30 UTCJul 10, 06:00 UTC7h 30m
2026-07-09 TAP243U LIS → ORD Jul 9, 08:45 UTCJul 9, 17:15 UTC8h 30m
2026-07-08 TAP074 - Jul 8, 19:00 UTCJul 9, 04:05 UTC9h 5m
2026-07-08 TAP2543 LIS → GIG Jul 8, 07:35 UTCJul 8, 17:00 UTC9h 25m
2026-07-07 TAP074 - Jul 7, 19:35 UTCJul 8, 04:25 UTC8h 50m
2026-07-07 TAP2543 LIS → GIG Jul 7, 07:55 UTCJul 7, 17:20 UTC9h 25m
2026-07-06 TAP104 - Jul 6, 11:20 UTCJul 7, 05:45 UTC18h 25m
2026-07-06 TAP104 LIS → LIS Jul 6, 09:50 UTCJul 7, 05:45 UTC19h 55m
2026-07-05 TAP104 - Jul 5, 11:20 UTCJul 6, 05:30 UTC18h 10m
2026-07-05 TAP104 LIS → LIS Jul 5, 09:55 UTCJul 6, 05:30 UTC19h 35m
2026-07-04 TAP224 - Jul 4, 21:25 UTCJul 5, 05:15 UTC7h 50m
2026-07-04 TAP22MI LIS → MIA Jul 4, 10:25 UTCJul 4, 18:45 UTC8h 20m
2026-07-03 TAP058 - Jul 3, 11:35 UTCJul 4, 05:50 UTC18h 15m
2026-07-03 TAP057 LIS → LIS Jul 3, 10:25 UTCJul 4, 05:50 UTC19h 25m
2026-07-02 TAP082 - Jul 2, 18:40 UTCJul 3, 03:45 UTC9h 5m
2026-07-01 TAP087 LIS → GRU Jul 1, 23:10 UTCJul 2, 08:45 UTC9h 35m
2026-07-01 TAP240 SFO → TER Jul 1, 02:55 UTCJul 1, 16:35 UTC13h 40m
2026-06-30 TAP241 LIS → TER Jun 30, 08:40 UTCJul 1, 00:00 UTC15h 20m
2026-06-29 TAP057 LIS → LIS Jun 29, 09:40 UTCJun 30, 05:05 UTC19h 26m
2026-06-28 TAP104 - Jun 28, 11:19 UTCJun 29, 05:34 UTC18h 15m
2026-06-28 TAP104 LIS → LIS Jun 28, 09:50 UTCJun 29, 05:34 UTC19h 45m
2026-06-27 TAP082 - Jun 27, 18:39 UTCJun 28, 03:55 UTC9h 15m
2026-06-26 TAP087 - Jun 26, 23:25 UTCJun 27, 08:55 UTC9h 30m
2026-06-26 TAP298 - Jun 26, 08:50 UTCJun 26, 16:05 UTC7h 15m
2026-06-25 TAP297 - Jun 25, 23:19 UTCJun 26, 06:25 UTC7h 5m
2026-06-25 TAP298 - Jun 25, 09:40 UTCJun 25, 16:59 UTC7h 20m
2026-06-24 TAP297 - Jun 24, 22:49 UTCJun 25, 06:00 UTC7h 10m
2026-06-24 TAP226 - Jun 24, 08:14 UTCJun 24, 16:05 UTC7h 50m
2026-06-24 TAP221 LIS → VXE Jun 24, 03:40 UTCJun 24, 04:10 UTC30m
2026-06-23 TAP221 LIS → VXE Jun 23, 19:55 UTCJun 23, 20:40 UTC45m
2026-06-23 TAP088 - Jun 23, 01:04 UTCJun 23, 10:19 UTC9h 15m
2026-06-22 TAP089 - Jun 22, 12:40 UTCJun 22, 22:15 UTC9h 35m
2026-06-21 TAP088 - Jun 21, 23:55 UTCJun 22, 09:14 UTC9h 20m
2026-06-21 TAP089 - Jun 21, 11:40 UTCJun 21, 21:19 UTC9h 40m
2026-06-20 TAP057 - Jun 20, 09:19 UTCJun 21, 05:10 UTC19h 50m
2026-06-19 TAP057 - Jun 19, 11:20 UTCJun 20, 06:24 UTC19h 5m
2026-06-19 TAP057 LIS → LIS Jun 19, 11:04 UTCJun 20, 06:24 UTC19h 20m
2026-06-19 TAP072 - Jun 19, 00:05 UTCJun 19, 09:14 UTC9h 9m
2026-06-18 TAP073 - Jun 18, 08:30 UTCJun 18, 18:00 UTC9h 30m
2026-06-16 TAP23SL SFO → LIS Jun 16, 00:00 UTCJun 16, 10:40 UTC10h 40m
2026-06-15 TAP237M LIS → SFO Jun 15, 09:15 UTCJun 15, 20:20 UTC11h 5m
2026-06-14 TAP074 - Jun 14, 18:45 UTCJun 15, 03:40 UTC8h 54m

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 .

Mode-S 4952A5 frequently asked

What is Mode-S code 4952A5?
4952A5 is an ICAO 24-bit transponder address. Allocated to Portugal. Assigned to CS-TUE.
Where is Mode-S 4952A5 registered?
Mode-S code 4952A5 is allocated to Portugal (PT). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 4952A5 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 4952A5, octal 22251245, decimal 4,805,285.
What flights does 4952A5 operate?
Mode-S 4952A5 has broadcast 20 distinct callsigns, including TAP088, TAP089, TAP074, TAP104, TAP297.