Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

4952B2

ICAO 24-bit transponder address · allocated to Portugal

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

Hex
4952B2
Octal
22251262
Decimal
4,805,298
Country
PT
Tail
CS-TUR
Type
A339
No current signal · last broadcast 1h ago
Flights observed
171
Distinct callsigns
20
Country
PT
Last broadcast
1h ago

Last known position

Most recent position reported by Mode-S 4952B2.

Country allocation

The ICAO 24-bit address 4952B2 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
TAP118 - 13 2026-07-11
TAP104 - 12 2026-07-09
TAP298 - 9 2026-07-14
TAP297 - 9 2026-07-13
TAP028 - 9 2026-07-05
TAP083 - 8 2026-07-03
TAP117 - 7 2026-07-11
TAP084 - 7 2026-07-04
TAP075 - 7 2026-06-23
TAP074 - 7 2026-06-24
TAP282 TAP Portugal 6 2026-06-10
TAP248 - 6 2026-07-11
TAP247 - 5 2026-07-10
TAP029 - 5 2026-07-01
TAP244 TAP Portugal 3 2026-05-08
TAP243U TAP Portugal 3 2026-05-08
TAP23SL - 3 2026-06-22
TAP237M - 3 2026-06-22
TAP22MI - 3 2026-06-13
TAP224 - 3 2026-06-13

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-14 TAP298 - Jul 14, 09:25 UTCJul 14, 10:00 UTC35m
2026-07-13 TAP297 - Jul 13, 22:40 UTCJul 14, 05:45 UTC7h 5m
2026-07-13 TAP298 - Jul 13, 09:35 UTCJul 13, 16:50 UTC7h 15m
2026-07-12 TAP297 - Jul 12, 23:05 UTCJul 13, 06:10 UTC7h 5m
2026-07-11 TAP118 - Jul 11, 21:25 UTCJul 12, 15:01 UTC17h 35m
2026-07-11 TAP118 - Jul 11, 16:35 UTCJul 12, 15:01 UTC22h 25m
2026-07-11 TAP117 - Jul 11, 14:50 UTCJul 12, 14:30 UTC23h 40m
2026-07-11 TAP248 LAX → LIS Jul 11, 00:05 UTCJul 11, 10:20 UTC10h 15m
2026-07-10 TAP247 LIS → LAX Jul 10, 09:40 UTCJul 10, 21:00 UTC11h 20m
2026-07-09 TAP104 - Jul 9, 10:45 UTCJul 10, 05:10 UTC18h 25m
2026-07-09 TAP104 LIS → LIS Jul 9, 09:40 UTCJul 10, 05:10 UTC19h 30m
2026-07-08 TAP082 - Jul 8, 18:40 UTCJul 9, 03:55 UTC9h 15m
2026-07-08 TAP087 LIS → GRU Jul 8, 01:35 UTCJul 8, 11:25 UTC9h 50m
2026-07-07 TAP204A EWR → LIS Jul 7, 03:40 UTCJul 7, 10:05 UTC6h 25m
2026-07-06 TAP203 LIS → EWR Jul 6, 17:30 UTCJul 7, 00:50 UTC7h 20m
2026-07-05 TAP028 LIS → LIS Jul 5, 19:15 UTCJul 6, 12:30 UTC17h 15m
2026-07-05 TAP204A - Jul 5, 04:20 UTCJul 5, 10:30 UTC6h 10m
2026-07-04 TAP203 LIS → EWR Jul 4, 17:40 UTCJul 5, 01:15 UTC7h 35m
2026-07-04 TAP084 - Jul 4, 05:25 UTCJul 4, 14:55 UTC9h 30m
2026-07-03 TAP083 - Jul 3, 18:05 UTCJul 4, 02:40 UTC8h 35m
2026-07-03 TAP083 - Jul 3, 16:55 UTCJul 3, 17:35 UTC40m
2026-07-03 TAP084 - Jul 3, 04:35 UTCJul 3, 13:50 UTC9h 15m
2026-07-02 TAP083 LIS → GRU Jul 2, 17:00 UTCJul 3, 02:50 UTC9h 50m
2026-07-01 TAP029 LIS → LIS Jul 1, 17:25 UTCJul 2, 10:55 UTC17h 30m
2026-07-01 TAP084 - Jul 1, 04:00 UTCJul 1, 13:20 UTC9h 20m
2026-06-30 TAP083 - Jun 30, 16:35 UTCJul 1, 02:10 UTC9h 35m
2026-06-30 TAP084 - Jun 30, 04:20 UTCJun 30, 13:30 UTC9h 10m
2026-06-29 TAP083 - Jun 29, 16:35 UTCJun 30, 02:15 UTC9h 41m
2026-06-29 TAP248 - Jun 29, 00:10 UTCJun 29, 10:20 UTC10h 10m
2026-06-28 TAP247 - Jun 28, 09:20 UTCJun 28, 21:24 UTC12h 5m
2026-06-27 TAP296 - Jun 27, 22:20 UTCJun 28, 05:40 UTC7h 20m
2026-06-27 TAP295 - Jun 27, 13:00 UTCJun 27, 20:04 UTC7h 5m
2026-06-24 TAP074 - Jun 24, 18:50 UTCJun 25, 04:10 UTC9h 20m
2026-06-23 TAP075 - Jun 23, 23:05 UTCJun 24, 08:30 UTC9h 25m
2026-06-22 TAP23SL - Jun 22, 23:55 UTCJun 23, 10:19 UTC10h 25m
2026-06-22 TAP237M LIS → SFO Jun 22, 09:19 UTCJun 22, 20:49 UTC11h 30m
2026-06-21 TAP104 - Jun 21, 10:34 UTCJun 22, 05:29 UTC18h 55m
2026-06-21 TAP104 LIS → LIS Jun 21, 09:49 UTCJun 22, 05:29 UTC19h 40m
2026-06-20 TAP074 - Jun 20, 18:45 UTCJun 21, 03:49 UTC9h 5m
2026-06-19 TAP075 - Jun 19, 22:55 UTCJun 20, 08:09 UTC9h 15m
2026-06-18 TAP118 - Jun 18, 19:30 UTCJun 19, 11:54 UTC16h 24m
2026-06-18 TAP118 - Jun 18, 13:50 UTCJun 19, 11:54 UTC22h 4m
2026-06-18 TAP117 - Jun 18, 13:05 UTCJun 18, 13:45 UTC40m
2026-06-17 TAP074 GIG → LIS Jun 17, 18:56 UTCJun 18, 03:45 UTC8h 50m
2026-06-16 TAP075 - Jun 16, 23:00 UTCJun 17, 08:35 UTC9h 35m
2026-06-16 TAP298 - Jun 16, 10:00 UTCJun 16, 17:10 UTC7h 10m
2026-06-15 TAP297 - Jun 15, 22:59 UTCJun 16, 05:59 UTC7h 0m
2026-06-15 TAP298 - Jun 15, 09:30 UTCJun 15, 16:55 UTC7h 25m
2026-06-14 TAP297 - Jun 14, 23:10 UTCJun 15, 06:00 UTC6h 50m
2026-06-14 TAP90EH FNC → LIS Jun 14, 16:15 UTCJun 14, 17:35 UTC1h 20m

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

Mode-S 4952B2 frequently asked

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