sensors Mode-S transponder

4952AC

ICAO 24-bit transponder address · allocated to Portugal

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

Hex
4952AC
Octal
22251254
Decimal
4,805,292
Country
PT
Tail
CS-TUL
Type
A339
Broadcasting now · callsign TAP281 · 35,000 ft
Flights observed
193
Distinct callsigns
20
Country
PT
Last broadcast
1d ago

Current position

4952AC is currently broadcasting. Map zoomed to live position.

Country allocation

The ICAO 24-bit address 4952AC 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
TAP104 - 11 2026-07-10
TAP22MI - 9 2026-06-26
TAP224 - 9 2026-06-26
TAP89WT - 7 2026-07-11
TAP248 - 7 2026-07-06
TAP296 - 6 2026-05-01
TAP247 - 6 2026-07-05
TAP226 - 6 2026-07-09
TAP075 - 6 2026-07-11
TAP074 - 6 2026-07-12
TAP90EH - 5 2026-07-11
TAP295 - 5 2026-05-01
TAP244 TAP Portugal 5 2026-05-16
TAP204A - 5 2026-07-02
TAP203 - 5 2026-07-01
TAP084 TAP Portugal 5 2026-06-12
TAP083 TAP Portugal 5 2026-06-11
TAP282 - 4 2026-06-22
TAP243U TAP Portugal 4 2026-05-15
TAP225V - 4 2026-07-08

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-12 TAP074 - Jul 12, 18:50 UTCJul 13, 03:50 UTC9h 0m
2026-07-11 TAP075 - Jul 11, 23:05 UTCJul 12, 08:50 UTC9h 45m
2026-07-11 TAP90EH FNC → LIS Jul 11, 13:30 UTCJul 11, 14:55 UTC1h 25m
2026-07-11 TAP89WT LIS → FNC Jul 11, 10:55 UTCJul 11, 12:20 UTC1h 25m
2026-07-10 TAP104 - Jul 10, 11:05 UTCJul 11, 05:05 UTC18h 0m
2026-07-10 TAP104 LIS → LIS Jul 10, 09:40 UTCJul 11, 05:05 UTC19h 25m
2026-07-09 TAP226 - Jul 9, 08:10 UTCJul 9, 16:15 UTC8h 5m
2026-07-08 TAP225V - Jul 8, 18:45 UTCJul 9, 03:05 UTC8h 20m
2026-07-08 TAP070 GIG → LIS Jul 8, 07:25 UTCJul 8, 16:25 UTC9h 0m
2026-07-07 TAP071 LIS → GIG Jul 7, 18:15 UTCJul 8, 03:35 UTC9h 20m
2026-07-06 TAP118 - Jul 6, 20:45 UTCJul 7, 14:25 UTC17h 40m
2026-07-06 TAP118 - Jul 6, 15:05 UTCJul 7, 14:25 UTC23h 20m
2026-07-06 TAP117 - Jul 6, 14:15 UTCJul 7, 13:00 UTC22h 45m
2026-07-06 TAP248 - Jul 6, 00:30 UTCJul 6, 10:55 UTC10h 25m
2026-07-05 TAP247 LIS → LAX Jul 5, 08:25 UTCJul 5, 19:40 UTC11h 15m
2026-07-04 TAP104 - Jul 4, 11:20 UTCJul 5, 05:30 UTC18h 10m
2026-07-04 TAP104 LIS → LIS Jul 4, 10:10 UTCJul 5, 05:30 UTC19h 20m
2026-07-03 TAP082 - Jul 3, 19:00 UTCJul 4, 04:00 UTC9h 0m
2026-07-02 TAP087 - Jul 2, 23:40 UTCJul 3, 09:15 UTC9h 35m
2026-07-02 TAP204A EWR → LIS Jul 2, 03:35 UTCJul 2, 10:05 UTC6h 30m
2026-07-01 TAP203 LIS → EWR Jul 1, 17:40 UTCJul 2, 00:55 UTC7h 15m
2026-07-01 TAP204A - Jul 1, 03:50 UTCJul 1, 10:25 UTC6h 35m
2026-06-30 TAP203 - Jun 30, 18:20 UTCJul 1, 01:25 UTC7h 5m
2026-06-30 TAP90EH FNC → LIS Jun 30, 14:30 UTCJun 30, 15:55 UTC1h 25m
2026-06-30 TAP89WT - Jun 30, 12:45 UTCJun 30, 13:15 UTC30m
2026-06-30 TAP89WT - Jun 30, 11:20 UTCJun 30, 12:05 UTC45m
2026-06-30 TAP210 JFK → LIS Jun 30, 03:00 UTCJun 30, 09:20 UTC6h 20m
2026-06-29 TAP209K LIS → JFK Jun 29, 16:50 UTCJun 30, 00:00 UTC7h 10m
2026-06-29 TAP226 - Jun 29, 12:29 UTCJun 29, 13:04 UTC35m
2026-06-29 TAP226 - Jun 29, 05:00 UTCJun 29, 07:55 UTC2h 55m
2026-06-28 TAP225V LIS → MIA Jun 28, 17:39 UTCJun 29, 01:55 UTC8h 15m
2026-06-28 TAP088 - Jun 28, 00:15 UTCJun 28, 09:25 UTC9h 10m
2026-06-27 TAP089 - Jun 27, 12:04 UTCJun 27, 21:25 UTC9h 20m
2026-06-26 TAP224 - Jun 26, 20:59 UTCJun 27, 04:44 UTC7h 45m
2026-06-26 TAP22MI - Jun 26, 10:10 UTCJun 26, 18:15 UTC8h 5m
2026-06-25 TAP104 - Jun 25, 11:10 UTCJun 26, 05:39 UTC18h 30m
2026-06-25 TAP104 LIS → LIS Jun 25, 09:59 UTCJun 26, 05:39 UTC19h 40m
2026-06-24 TAP104 - Jun 24, 11:20 UTCJun 25, 06:00 UTC18h 40m
2026-06-24 TAP104 LIS → LIS Jun 24, 10:10 UTCJun 25, 06:00 UTC19h 50m
2026-06-23 TAP082 - Jun 23, 19:00 UTCJun 24, 04:05 UTC9h 5m
2026-06-22 TAP087 - Jun 22, 23:05 UTCJun 23, 08:39 UTC9h 35m
2026-06-22 TAP282 - Jun 22, 16:05 UTCJun 22, 17:25 UTC1h 20m
2026-06-21 TAP282 - Jun 21, 19:05 UTCJun 22, 17:25 UTC22h 20m
2026-06-21 TAP204A - Jun 21, 03:34 UTCJun 21, 09:44 UTC6h 10m
2026-06-20 TAP203 LIS → EWR Jun 20, 17:29 UTCJun 21, 00:49 UTC7h 20m
2026-06-20 TAP90EH FNC → LIS Jun 20, 13:44 UTCJun 20, 15:04 UTC1h 20m
2026-06-20 TAP89WT LIS → FNC Jun 20, 11:05 UTCJun 20, 12:30 UTC1h 25m
2026-06-19 TAP224 - Jun 19, 21:34 UTCJun 20, 05:09 UTC7h 35m
2026-06-19 TAP22MI - Jun 19, 10:29 UTCJun 19, 19:14 UTC8h 45m
2026-06-18 TAP224 - Jun 18, 20:50 UTCJun 19, 04:25 UTC7h 34m

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

Mode-S 4952AC frequently asked

What is Mode-S code 4952AC?
4952AC is an ICAO 24-bit transponder address. Allocated to Portugal. Assigned to CS-TUL.
Where is Mode-S 4952AC registered?
Mode-S code 4952AC is allocated to Portugal (PT). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 4952AC broadcasting right now?
Yes. Mode-S 4952AC is currently airborne.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 4952AC, octal 22251254, decimal 4,805,292.
What flights does 4952AC operate?
Mode-S 4952AC has broadcast 20 distinct callsigns, including TAP104, TAP22MI, TAP224, TAP89WT, TAP248.