sensors Mode-S transponder

4952A3

ICAO 24-bit transponder address · allocated to Portugal

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

Hex
4952A3
Octal
22251243
Decimal
4,805,283
Country
PT
Tail
CS-TUC
Type
A339
No current signal · last broadcast 1h ago
Flights observed
153
Distinct callsigns
20
Country
PT
Last broadcast
1h ago

Last known position

Most recent position reported by Mode-S 4952A3.

Country allocation

The ICAO 24-bit address 4952A3 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
TAP298 - 11 2026-07-09
TAP087 - 11 2026-07-09
TAP082 - 9 2026-07-10
TAP297 - 8 2026-07-08
TAP057 - 8 2026-06-26
TAP243U - 7 2026-07-12
TAP104 - 7 2026-06-27
TAP282 - 6 2026-07-04
TAP244 - 6 2026-07-13
TAP075 TAP Portugal 6 2026-05-31
TAP074 - 6 2026-07-06
TAP073 TAP Portugal 5 2026-06-09
TAP072 TAP Portugal 5 2026-06-09
TAP012 - 5 2026-06-15
TAP89WT TAP Portugal 4 2026-05-11
TAP011 TAP Portugal 4 2026-06-14
TAP226 TAP Portugal 3 2026-05-27
TAP210 TAP Portugal 3 2026-06-13
TAP209K - 3 2026-06-12
TAP058 - 3 2026-06-26

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-13 TAP224 - Jul 13, 21:00 UTCJul 14, 04:40 UTC7h 40m
2026-07-13 TAP22MI - Jul 13, 10:15 UTCJul 13, 18:40 UTC8h 25m
2026-07-13 TAP244 - Jul 13, 00:05 UTCJul 13, 07:35 UTC7h 30m
2026-07-12 TAP243U LIS → ORD Jul 12, 12:10 UTCJul 12, 20:15 UTC8h 5m
2026-07-11 TAP244 - Jul 11, 23:35 UTCJul 12, 07:10 UTC7h 35m
2026-07-11 TAP243U LIS → ORD Jul 11, 12:10 UTCJul 11, 20:15 UTC8h 5m
2026-07-10 TAP082 - Jul 10, 18:50 UTCJul 11, 03:45 UTC8h 55m
2026-07-09 TAP087 LIS → GRU Jul 9, 23:05 UTCJul 10, 09:05 UTC10h 0m
2026-07-09 TAP298 - Jul 9, 09:25 UTCJul 9, 16:55 UTC7h 30m
2026-07-08 TAP297 - Jul 8, 22:40 UTCJul 9, 05:30 UTC6h 50m
2026-07-08 TAP240 - Jul 8, 02:50 UTCJul 8, 17:00 UTC14h 10m
2026-07-07 TAP241 LIS → SFO Jul 7, 08:55 UTCJul 7, 23:50 UTC14h 55m
2026-07-06 TAP074 - Jul 6, 18:55 UTCJul 7, 03:50 UTC8h 55m
2026-07-06 TAP2543 - Jul 6, 07:35 UTCJul 6, 17:05 UTC9h 30m
2026-07-05 TAP082 - Jul 5, 18:45 UTCJul 6, 03:40 UTC8h 55m
2026-07-04 TAP087 - Jul 4, 23:10 UTCJul 5, 08:50 UTC9h 40m
2026-07-04 TAP282 - Jul 4, 16:00 UTCJul 4, 17:35 UTC1h 35m
2026-07-03 TAP282 LIS → LIS Jul 3, 19:05 UTCJul 4, 17:35 UTC22h 30m
2026-07-03 TAP298 - Jul 3, 08:20 UTCJul 3, 15:45 UTC7h 25m
2026-07-02 TAP297 - Jul 2, 22:50 UTCJul 3, 05:55 UTC7h 5m
2026-07-02 TAP298 - Jul 2, 09:25 UTCJul 2, 16:35 UTC7h 10m
2026-07-01 TAP297 - Jul 1, 22:50 UTCJul 2, 05:55 UTC7h 5m
2026-07-01 TAP282 - Jul 1, 16:20 UTCJul 1, 17:45 UTC1h 25m
2026-06-30 TAP282 - Jun 30, 18:50 UTCJul 1, 17:45 UTC22h 55m
2026-06-30 TAP070 GIG → LIS Jun 30, 07:15 UTCJun 30, 16:05 UTC8h 50m
2026-06-29 TAP071 - Jun 29, 19:29 UTCJun 30, 05:00 UTC9h 31m
2026-06-28 TAP244 - Jun 28, 23:50 UTCJun 29, 06:59 UTC7h 10m
2026-06-28 TAP243U YRI → ORD Jun 28, 18:34 UTCJun 28, 20:50 UTC2h 15m
2026-06-28 TAP243U - Jun 28, 12:19 UTCJun 28, 18:29 UTC6h 10m
2026-06-27 TAP104 - Jun 27, 10:50 UTCJun 28, 05:34 UTC18h 45m
2026-06-27 TAP103 LIS → LIS Jun 27, 09:50 UTCJun 28, 05:34 UTC19h 45m
2026-06-26 TAP058 - Jun 26, 16:49 UTCJun 27, 05:59 UTC13h 10m
2026-06-26 TAP057 - Jun 26, 10:25 UTCJun 26, 11:09 UTC45m
2026-06-25 TAP058 - Jun 25, 10:50 UTCJun 26, 05:35 UTC18h 45m
2026-06-25 TAP057 LIS → LIS Jun 25, 10:04 UTCJun 26, 05:35 UTC19h 30m
2026-06-24 TAP057 - Jun 24, 10:49 UTCJun 25, 06:20 UTC19h 30m
2026-06-24 TAP057 LIS → LIS Jun 24, 10:30 UTCJun 25, 06:20 UTC19h 50m
2026-06-23 TAP104 - Jun 23, 15:24 UTCJun 24, 05:29 UTC14h 5m
2026-06-23 TAP104 LIS → LIS Jun 23, 08:54 UTCJun 24, 05:29 UTC20h 35m
2026-06-22 TAP082 - Jun 22, 18:44 UTCJun 23, 03:54 UTC9h 10m
2026-06-22 TAP087 - Jun 22, 00:10 UTCJun 22, 09:45 UTC9h 35m
2026-06-19 TAP9748 - Jun 19, 20:24 UTCJun 20, 04:44 UTC8h 20m
2026-06-18 TAP087 - Jun 18, 05:35 UTCJun 18, 09:20 UTC3h 45m
2026-06-17 TAP087 - Jun 17, 23:05 UTCJun 17, 23:50 UTC45m
2026-06-15 TAP012 - Jun 15, 02:10 UTCJun 15, 09:05 UTC6h 55m
2026-06-14 TAP011 LIS → REC Jun 14, 23:50 UTCJun 15, 00:10 UTC20m
2026-06-14 TAP011 LIS → REC Jun 14, 17:05 UTCJun 14, 18:50 UTC1h 45m
2026-06-13 TAP3178 - Jun 13, 12:50 UTCJun 14, 08:25 UTC19h 35m
2026-06-13 TAP3178 LIS → LIS Jun 13, 11:40 UTCJun 14, 08:25 UTC20h 45m
2026-06-13 TAP210 JFK → LIS Jun 13, 02:50 UTCJun 13, 09:15 UTC6h 24m

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

Mode-S 4952A3 frequently asked

What is Mode-S code 4952A3?
4952A3 is an ICAO 24-bit transponder address. Allocated to Portugal. Assigned to CS-TUC.
Where is Mode-S 4952A3 registered?
Mode-S code 4952A3 is allocated to Portugal (PT). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 4952A3 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 4952A3, octal 22251243, decimal 4,805,283.
What flights does 4952A3 operate?
Mode-S 4952A3 has broadcast 20 distinct callsigns, including TAP298, TAP087, TAP082, TAP297, TAP057.