sensors Mode-S transponder

4952A7

ICAO 24-bit transponder address · allocated to Portugal

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

Hex
4952A7
Octal
22251247
Decimal
4,805,287
Country
PT
Tail
CS-TUG
Type
A339
Broadcasting now · callsign TAP084 · 37,000 ft
Flights observed
176
Distinct callsigns
20
Country
PT
Last broadcast
1h ago

Current position

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

Country allocation

The ICAO 24-bit address 4952A7 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 - 9 2026-06-21
TAP237M TAP Portugal 7 2026-05-22
TAP075 - 7 2026-07-01
TAP89WT - 6 2026-06-17
TAP084 - 6 2026-07-14
TAP083 - 6 2026-07-13
TAP236 TAP Portugal 5 2026-05-23
TAP074 - 5 2026-07-02
TAP073 - 5 2026-06-29
TAP072 - 5 2026-06-29
TAP011 - 5 2026-06-26
TAP90EH TAP Portugal 4 2026-06-17
TAP22MI - 4 2026-07-08
TAP224 - 4 2026-07-08
TAP210 - 4 2026-06-29
TAP209K - 4 2026-06-28
TAP104 TAP Portugal 4 2026-05-18
TAP103 TAP Portugal 4 2026-06-13
TAP093 TAP Portugal 4 2026-06-11
TAP089 - 4 2026-06-20

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-14 TAP084 - Jul 14, 03:55 UTCJul 14, 05:15 UTC1h 20m
2026-07-13 TAP083 LIS → GRU Jul 13, 16:25 UTCJul 14, 02:05 UTC9h 40m
2026-07-13 TAP248 LAX → LIS Jul 13, 00:01 UTCJul 13, 10:50 UTC10h 50m
2026-07-12 TAP247 LIS → LAX Jul 12, 09:00 UTCJul 12, 20:10 UTC11h 10m
2026-07-11 TAP082 - Jul 11, 18:45 UTCJul 12, 03:50 UTC9h 5m
2026-07-10 TAP087 LIS → GRU Jul 10, 23:15 UTCJul 11, 09:25 UTC10h 10m
2026-07-08 TAP224 - Jul 8, 20:50 UTCJul 9, 04:30 UTC7h 40m
2026-07-08 TAP22MI LIS → MIA Jul 8, 10:20 UTCJul 8, 18:45 UTC8h 25m
2026-07-07 TAP082 - Jul 7, 18:50 UTCJul 8, 04:00 UTC9h 10m
2026-07-06 TAP087 - Jul 6, 23:10 UTCJul 7, 08:50 UTC9h 40m
2026-07-06 TAP282 - Jul 6, 16:40 UTCJul 6, 18:05 UTC1h 25m
2026-07-05 TAP282 LIS → LIS Jul 5, 19:55 UTCJul 6, 18:05 UTC22h 10m
2026-07-05 TAP118 - Jul 5, 00:45 UTCJul 5, 14:40 UTC13h 55m
2026-07-04 TAP118 - Jul 4, 15:50 UTCJul 5, 14:40 UTC22h 50m
2026-07-04 TAP248 - Jul 4, 00:45 UTCJul 4, 11:10 UTC10h 25m
2026-07-03 TAP247 - Jul 3, 09:20 UTCJul 3, 20:40 UTC11h 20m
2026-07-02 TAP074 - Jul 2, 19:10 UTCJul 3, 03:50 UTC8h 40m
2026-07-01 TAP075 - Jul 1, 23:05 UTCJul 2, 08:05 UTC9h 0m
2026-07-01 TAP226 - Jul 1, 08:10 UTCJul 1, 16:10 UTC8h 0m
2026-06-30 TAP221 - Jun 30, 18:35 UTCJul 1, 02:50 UTC8h 15m
2026-06-29 TAP072 - Jun 29, 23:19 UTCJun 30, 08:15 UTC8h 56m
2026-06-29 TAP073 LIS → GIG Jun 29, 11:35 UTCJun 29, 21:09 UTC9h 35m
2026-06-29 TAP210 - Jun 29, 03:10 UTCJun 29, 09:14 UTC6h 5m
2026-06-28 TAP209K LIS → JFK Jun 28, 16:49 UTCJun 29, 00:05 UTC7h 15m
2026-06-27 TAP029 LIS → LIS Jun 27, 17:44 UTCJun 28, 10:50 UTC17h 5m
2026-06-27 TAP012 - Jun 27, 01:44 UTCJun 27, 08:39 UTC6h 55m
2026-06-26 TAP011 - Jun 26, 23:19 UTCJun 26, 23:49 UTC30m
2026-06-26 TAP011 - Jun 26, 16:39 UTCJun 26, 17:19 UTC40m
2026-06-25 TAP028 LIS → LIS Jun 25, 17:20 UTCJun 26, 10:39 UTC17h 20m
2026-06-25 TAP084 - Jun 25, 04:40 UTCJun 25, 13:55 UTC9h 15m
2026-06-24 TAP083 - Jun 24, 16:34 UTCJun 25, 02:05 UTC9h 30m
2026-06-24 TAP248 - Jun 24, 00:15 UTCJun 24, 10:35 UTC10h 20m
2026-06-23 TAP247 - Jun 23, 09:45 UTCJun 23, 21:05 UTC11h 20m
2026-06-22 TAP084 - Jun 22, 04:15 UTCJun 22, 13:35 UTC9h 20m
2026-06-21 TAP083 - Jun 21, 16:44 UTCJun 22, 02:19 UTC9h 35m
2026-06-21 TAP088 - Jun 21, 00:10 UTCJun 21, 09:35 UTC9h 25m
2026-06-20 TAP089 - Jun 20, 12:09 UTCJun 20, 21:19 UTC9h 10m
2026-06-20 TAP210 JFK → LIS Jun 20, 03:04 UTCJun 20, 09:09 UTC6h 5m
2026-06-19 TAP209K LIS → JFK Jun 19, 16:34 UTCJun 20, 00:04 UTC7h 30m
2026-06-19 TAP084 - Jun 19, 04:10 UTCJun 19, 13:44 UTC9h 35m
2026-06-18 TAP083 LIS → GRU Jun 18, 16:55 UTCJun 19, 02:19 UTC9h 24m
2026-06-17 TAP028 LIS → LIS Jun 17, 16:55 UTCJun 18, 10:35 UTC17h 40m
2026-06-17 TAP90EH FNC → LIS Jun 17, 13:30 UTCJun 17, 14:55 UTC1h 25m
2026-06-17 TAP89WT LIS → FNC Jun 17, 10:50 UTCJun 17, 12:20 UTC1h 30m
2026-06-16 TAP072 - Jun 16, 23:15 UTCJun 17, 08:10 UTC8h 55m
2026-06-16 TAP073 LIS → GIG Jun 16, 10:55 UTCJun 16, 20:40 UTC9h 46m
2026-06-16 TAP012 - Jun 16, 04:50 UTCJun 16, 08:39 UTC3h 50m
2026-06-16 TAP012 - Jun 16, 01:40 UTCJun 16, 02:00 UTC20m
2026-06-15 TAP011 LIS → REC Jun 15, 23:39 UTCJun 15, 23:54 UTC15m
2026-06-15 TAP011 LIS → REC Jun 15, 16:49 UTCJun 15, 18:29 UTC1h 40m

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

Mode-S 4952A7 frequently asked

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