Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

4952CF

ICAO 24-bit transponder address · allocated to Portugal

Currently assigned to CS-TVO · AIRBUS A-320neo

Hex
4952CF
Octal
22251317
Decimal
4,805,327
Country
PT
Tail
CS-TVO
Type
A20N
Broadcasting now · callsign TAP1356 · 34,025 ft
Flights observed
431
Distinct callsigns
20
Country
PT
Last broadcast
Jul 26, 21:45 UTC

Current position

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

Country allocation

The ICAO 24-bit address 4952CF 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
TAP1687 TAP Portugal 10 2026-07-20
TAP75CH - 8 2026-07-15
TAP752 - 8 2026-07-15
TAP88TM TAP Portugal 7 2026-07-20
TAP435 - 7 2026-07-05
TAP64BR TAP Portugal 6 2026-07-21
TAP643 TAP Portugal 6 2026-07-21
TAP43TR - 6 2026-07-05
TAP98CX - 5 2026-07-10
TAP97LS - 5 2026-07-09
TAP76EN TAP Portugal 5 2026-06-17
TAP764 TAP Portugal 5 2026-06-17
TAP67U - 5 2026-07-13
TAP67NP TAP Portugal 5 2026-07-24
TAP67AM - 5 2026-07-13
TAP675 TAP Portugal 5 2026-07-25
TAP43M - 5 2026-07-19
TAP13HL TAP Portugal 5 2026-06-16
TAP1369 TAP Portugal 5 2026-06-16
TAP1356 - 5 2026-06-16

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-26 TAP9036 - Jul 26, 21:40 UTCJul 26, 21:45 UTC5m
2026-07-26 TAP57W LHR → LIS Jul 26, 18:05 UTCJul 26, 20:15 UTC2h 10m
2026-07-26 TAP50Y LIS → LHR Jul 26, 14:30 UTCJul 26, 16:45 UTC2h 15m
2026-07-26 TAP823 MXP → LIS Jul 26, 10:50 UTCJul 26, 13:10 UTC2h 20m
2026-07-26 TAP22MX LIS → MXP Jul 26, 07:00 UTCJul 26, 09:25 UTC2h 25m
2026-07-25 TAP863Y VCE → LIS Jul 25, 18:35 UTCJul 25, 21:30 UTC2h 55m
2026-07-25 TAP86VR LIS → VCE Jul 25, 14:35 UTCJul 25, 16:50 UTC2h 15m
2026-07-25 TAP675 LUX → LIS Jul 25, 05:25 UTCJul 25, 08:00 UTC2h 35m
2026-07-24 TAP67NP LIS → LIS Jul 24, 17:50 UTCJul 24, 20:10 UTC2h 20m
2026-07-24 TAP83RS FCO → LIS Jul 24, 12:25 UTCJul 24, 15:20 UTC2h 55m
2026-07-24 TAP832 LIS → FCO Jul 24, 07:50 UTCJul 24, 10:15 UTC2h 25m
2026-07-24 TAP1937 OPO → LIS Jul 24, 04:20 UTCJul 24, 05:05 UTC45m
2026-07-23 TAP1938 LIS → OPO Jul 23, 23:05 UTCJul 23, 23:40 UTC35m
2026-07-23 TAP53ED BER → LIS Jul 23, 16:15 UTCJul 23, 19:35 UTC3h 20m
2026-07-23 TAP532B LIS → BER Jul 23, 11:30 UTCJul 23, 14:35 UTC3h 5m
2026-07-23 TAP757P CPH → LIS Jul 23, 04:30 UTCJul 23, 08:00 UTC3h 30m
2026-07-22 TAP6CY LIS → CPH Jul 22, 18:10 UTCJul 22, 21:20 UTC3h 10m
2026-07-22 TAP433 ORY → LIS Jul 22, 13:25 UTCJul 22, 15:45 UTC2h 20m
2026-07-22 TAP432 LIS → ORY Jul 22, 11:10 UTCJul 22, 11:50 UTC40m
2026-07-21 TAP442 LIS → ORY Jul 21, 19:00 UTCJul 21, 20:55 UTC1h 55m
2026-07-21 TAP643 BRU → LIS Jul 21, 14:05 UTCJul 21, 16:30 UTC2h 25m
2026-07-21 TAP64BR LIS → BRU Jul 21, 10:30 UTCJul 21, 12:50 UTC2h 20m
2026-07-21 TAP675 LUX → LIS Jul 21, 05:30 UTCJul 21, 08:00 UTC2h 30m
2026-07-20 TAP67NP LIS → AMS Jul 20, 17:45 UTCJul 20, 20:05 UTC2h 20m
2026-07-20 TAP88TM FNC → LIS Jul 20, 11:55 UTCJul 20, 13:15 UTC1h 20m
2026-07-20 TAP1687 LIS → FNC Jul 20, 09:25 UTCJul 20, 11:00 UTC1h 35m
2026-07-19 TAP43M LIS → LIS Jul 19, 21:20 UTCJul 20, 06:15 UTC8h 55m
2026-07-19 TAP155A LIS → LIS Jul 19, 08:35 UTCJul 19, 16:55 UTC8h 20m
2026-07-18 TAP43M LIS → LIS Jul 18, 20:15 UTCJul 19, 05:00 UTC8h 45m
2026-07-18 TAP1541 LIS → LIS Jul 18, 08:40 UTCJul 18, 17:50 UTC9h 10m
2026-07-18 TAP9004 - Jul 18, 02:45 UTCJul 18, 05:35 UTC2h 51m
2026-07-17 TAP9003 - Jul 17, 22:45 UTCJul 18, 01:15 UTC2h 30m
2026-07-17 TAP57W - Jul 17, 18:15 UTCJul 17, 20:29 UTC2h 15m
2026-07-17 TAP50Y LIS → LHR Jul 17, 14:50 UTCJul 17, 16:55 UTC2h 5m
2026-07-17 TAP88TM FNC → LIS Jul 17, 11:55 UTCJul 17, 13:29 UTC1h 35m
2026-07-17 TAP1687 LIS → FNC Jul 17, 09:15 UTCJul 17, 10:40 UTC1h 25m
2026-07-17 TAP557H MUC → LIS Jul 17, 04:39 UTCJul 17, 07:44 UTC3h 5m
2026-07-16 TAP556 LIS → MUC Jul 16, 18:34 UTCJul 16, 21:19 UTC2h 45m
2026-07-16 TAP643 - Jul 16, 14:15 UTCJul 16, 16:49 UTC2h 35m
2026-07-16 TAP64BR LIS → BRU Jul 16, 10:45 UTCJul 16, 12:55 UTC2h 10m
2026-07-16 TAP1921 OPO → LIS Jul 16, 08:35 UTCJul 16, 09:20 UTC45m
2026-07-16 TAP457 ORY → OPO Jul 16, 05:15 UTCJul 16, 07:15 UTC2h 0m
2026-07-15 TAP56UG OPO → ORY Jul 15, 19:25 UTCJul 15, 21:00 UTC1h 35m
2026-07-15 TAP1932 LIS → OPO Jul 15, 17:25 UTCJul 15, 17:55 UTC30m
2026-07-15 TAP75CH CPH → LIS Jul 15, 11:10 UTCJul 15, 14:35 UTC3h 25m
2026-07-15 TAP752 LIS → CPH Jul 15, 06:40 UTCJul 15, 09:50 UTC3h 10m
2026-07-14 TAP555 MUC → LIS Jul 14, 19:25 UTCJul 14, 22:40 UTC3h 15m
2026-07-14 TAP554M LIS → MUC Jul 14, 15:20 UTCJul 14, 18:00 UTC2h 40m
2026-07-14 TAP641 BRU → LIS Jul 14, 10:05 UTCJul 14, 12:50 UTC2h 45m
2026-07-14 TAP640 LIS → BRU Jul 14, 06:30 UTCJul 14, 08:40 UTC2h 10m

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

Mode-S 4952CF frequently asked

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