sensors Mode-S transponder

4952AE

ICAO 24-bit transponder address · allocated to Portugal

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

Hex
4952AE
Octal
22251256
Decimal
4,805,294
Country
PT
Tail
CS-TUN
Type
A339
Broadcasting now · callsign TAP204A · 13,900 ft
Flights observed
174
Distinct callsigns
20
Country
PT
Last broadcast
4m ago

Current position

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

Country allocation

The ICAO 24-bit address 4952AE 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
TAP074 - 13 2026-06-28
TAP075 - 12 2026-06-27
TAP118 - 11 2026-06-30
TAP237M - 7 2026-06-29
TAP084 - 7 2026-07-11
TAP104 - 6 2026-06-22
TAP083 - 6 2026-07-10
TAP011 - 6 2026-07-12
TAP298 - 5 2026-06-17
TAP244 - 5 2026-06-21
TAP243U - 5 2026-06-21
TAP23SL - 5 2026-06-30
TAP204A - 5 2026-07-14
TAP203 - 5 2026-07-13
TAP3178 - 4 2026-05-12
TAP297 - 4 2026-06-16
TAP282 TAP Portugal 4 2026-06-03
TAP236 TAP Portugal 4 2026-04-18
TAP210 - 4 2026-07-05
TAP209K - 4 2026-07-04

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-14 TAP204A - Jul 14, 03:20 UTCJul 14, 09:30 UTC6h 10m
2026-07-13 TAP203 LIS → EWR Jul 13, 17:45 UTCJul 14, 00:50 UTC7h 5m
2026-07-13 TAP90EH FNC → LIS Jul 13, 13:55 UTCJul 13, 15:15 UTC1h 20m
2026-07-13 TAP89WT LIS → FNC Jul 13, 11:15 UTCJul 13, 12:40 UTC1h 25m
2026-07-13 TAP012 - Jul 13, 02:20 UTCJul 13, 09:15 UTC6h 55m
2026-07-12 TAP011 - Jul 12, 23:35 UTCJul 12, 23:55 UTC20m
2026-07-12 TAP011 - Jul 12, 16:45 UTCJul 12, 18:40 UTC1h 55m
2026-07-11 TAP029 LIS → LIS Jul 11, 16:50 UTCJul 12, 10:20 UTC17h 30m
2026-07-11 TAP084 LIS → LIS Jul 11, 15:00 UTCJul 11, 15:15 UTC15m
2026-07-11 TAP084 - Jul 11, 05:25 UTCJul 11, 14:30 UTC9h 5m
2026-07-10 TAP083 - Jul 10, 16:25 UTCJul 11, 02:10 UTC9h 46m
2026-07-10 TAP084 - Jul 10, 04:20 UTCJul 10, 13:30 UTC9h 10m
2026-07-09 TAP083 - Jul 9, 16:45 UTCJul 10, 02:25 UTC9h 40m
2026-07-09 TAP110 - Jul 9, 01:25 UTCJul 9, 11:15 UTC9h 50m
2026-07-08 TAP109 - Jul 8, 13:05 UTCJul 8, 23:20 UTC10h 15m
2026-07-08 TAP204A EWR → LIS Jul 8, 03:50 UTCJul 8, 10:10 UTC6h 20m
2026-07-07 TAP203 LIS → EWR Jul 7, 17:05 UTCJul 8, 00:10 UTC7h 5m
2026-07-07 TAP084 - Jul 7, 04:00 UTCJul 7, 13:20 UTC9h 20m
2026-07-06 TAP083 - Jul 6, 16:40 UTCJul 7, 02:10 UTC9h 30m
2026-07-06 TAP112 - Jul 6, 03:30 UTCJul 6, 13:20 UTC9h 50m
2026-07-05 TAP109 - Jul 5, 11:40 UTCJul 5, 22:00 UTC10h 20m
2026-07-05 TAP210 JFK → LIS Jul 5, 03:15 UTCJul 5, 09:30 UTC6h 15m
2026-07-04 TAP209K LIS → JFK Jul 4, 16:45 UTCJul 4, 23:50 UTC7h 5m
2026-07-03 TAP088 - Jul 3, 23:55 UTCJul 4, 08:50 UTC8h 55m
2026-07-03 TAP089 - Jul 3, 12:20 UTCJul 3, 22:05 UTC9h 45m
2026-07-03 TAP204A EWR → LIS Jul 3, 03:50 UTCJul 3, 10:20 UTC6h 30m
2026-07-02 TAP203 LIS → EWR Jul 2, 17:20 UTCJul 3, 00:15 UTC6h 55m
2026-07-02 TAP084 - Jul 2, 03:55 UTCJul 2, 13:20 UTC9h 25m
2026-07-01 TAP083 LIS → GRU Jul 1, 16:25 UTCJul 2, 02:05 UTC9h 40m
2026-06-30 TAP118 - Jun 30, 20:55 UTCJul 1, 13:35 UTC16h 40m
2026-06-30 TAP118 - Jun 30, 15:35 UTCJul 1, 13:35 UTC22h 0m
2026-06-30 TAP118 - Jun 30, 15:15 UTCJul 1, 13:30 UTC22h 15m
2026-06-30 TAP117 - Jun 30, 14:30 UTCJun 30, 15:10 UTC40m
2026-06-30 TAP23SL SFO → LIS Jun 30, 00:00 UTCJun 30, 10:25 UTC10h 26m
2026-06-29 TAP237M LIS → SFO Jun 29, 09:05 UTCJun 29, 20:35 UTC11h 30m
2026-06-28 TAP074 - Jun 28, 18:44 UTCJun 29, 03:44 UTC9h 0m
2026-06-27 TAP075 - Jun 27, 22:45 UTCJun 28, 07:54 UTC9h 10m
2026-06-27 TAP23SL SFO → LIS Jun 27, 05:19 UTCJun 27, 15:34 UTC10h 15m
2026-06-26 TAP237M LIS → SFO Jun 26, 08:54 UTCJun 26, 20:34 UTC11h 40m
2026-06-25 TAP082 - Jun 25, 18:50 UTCJun 26, 03:50 UTC9h 0m
2026-06-24 TAP087 - Jun 24, 23:00 UTCJun 25, 08:40 UTC9h 40m
2026-06-24 TAP240 SFO → TER Jun 24, 03:00 UTCJun 24, 16:29 UTC13h 30m
2026-06-23 TAP241 LIS → TER Jun 23, 08:45 UTCJun 24, 00:09 UTC15h 25m
2026-06-22 TAP104 LIS → LIS Jun 22, 09:54 UTCJun 23, 05:29 UTC19h 35m
2026-06-21 TAP244 ORD → LIS Jun 21, 23:40 UTCJun 22, 06:49 UTC7h 10m
2026-06-21 TAP243U LIS → ORD Jun 21, 12:04 UTCJun 21, 20:40 UTC8h 35m
2026-06-20 TAP104 LIS → LIS Jun 20, 09:39 UTCJun 21, 05:20 UTC19h 40m
2026-06-19 TAP104 - Jun 19, 21:24 UTCJun 20, 05:49 UTC8h 25m
2026-06-19 TAP104 - Jun 19, 09:34 UTCJun 20, 05:49 UTC20h 15m
2026-06-18 TAP074 - Jun 18, 18:40 UTCJun 19, 03:39 UTC8h 59m

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

Mode-S 4952AE frequently asked

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