sensors Mode-S transponder

4952B1

ICAO 24-bit transponder address · allocated to Portugal

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

Hex
4952B1
Octal
22251261
Decimal
4,805,297
Country
PT
Tail
CS-TUQ
Type
A339
No current signal · last broadcast 1h ago
Flights observed
159
Distinct callsigns
20
Country
PT
Last broadcast
1h ago

Last known position

Most recent position reported by Mode-S 4952B1.

Country allocation

The ICAO 24-bit address 4952B1 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
TAP082 - 16 2026-06-29
TAP075 - 14 2026-06-20
TAP087 - 13 2026-06-28
TAP074 - 10 2026-06-21
TAP22MI - 8 2026-07-03
TAP104 - 8 2026-06-30
TAP089 - 8 2026-07-08
TAP224 - 7 2026-07-03
TAP088 - 7 2026-07-09
TAP058 - 6 2026-07-04
TAP237M - 4 2026-06-24
TAP083 - 4 2026-06-25
TAP057 - 4 2026-07-01
TAP23SL - 3 2026-06-25
TAP204A - 3 2026-07-12
TAP203 - 3 2026-07-11
TAP084 - 3 2026-06-26
TAP073 TAP Portugal 3 2026-06-04
TAP91SR TAP Portugal 2 2026-04-23
TAP298 - 2 2026-06-02

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-13 TAP117 - Jul 13, 14:45 UTCJul 14, 01:15 UTC10h 30m
2026-07-12 TAP028 LIS → LIS Jul 12, 17:05 UTCJul 13, 10:35 UTC17h 30m
2026-07-12 TAP204A EWR → LIS Jul 12, 03:25 UTCJul 12, 09:45 UTC6h 20m
2026-07-11 TAP203 LIS → EWR Jul 11, 17:15 UTCJul 12, 00:40 UTC7h 25m
2026-07-11 TAP226 - Jul 11, 05:50 UTCJul 11, 13:35 UTC7h 45m
2026-07-10 TAP225V - Jul 10, 16:55 UTCJul 11, 01:10 UTC8h 15m
2026-07-10 TAP204A - Jul 10, 06:10 UTCJul 10, 12:20 UTC6h 10m
2026-07-09 TAP203 LIS → EWR Jul 9, 17:50 UTCJul 10, 01:10 UTC7h 20m
2026-07-09 TAP088 - Jul 9, 00:10 UTCJul 9, 09:40 UTC9h 30m
2026-07-08 TAP089 - Jul 8, 12:05 UTCJul 8, 21:45 UTC9h 40m
2026-07-07 TAP088 - Jul 7, 23:50 UTCJul 8, 09:05 UTC9h 15m
2026-07-07 TAP089 - Jul 7, 11:45 UTCJul 7, 21:35 UTC9h 50m
2026-07-07 TAP088 - Jul 7, 00:10 UTCJul 7, 09:30 UTC9h 20m
2026-07-06 TAP089 - Jul 6, 21:40 UTCJul 6, 22:00 UTC20m
2026-07-06 TAP089 - Jul 6, 12:30 UTCJul 6, 19:00 UTC6h 30m
2026-07-05 TAP088 - Jul 5, 23:50 UTCJul 6, 09:05 UTC9h 15m
2026-07-05 TAP089 - Jul 5, 12:15 UTCJul 5, 21:55 UTC9h 40m
2026-07-04 TAP058 - Jul 4, 10:20 UTCJul 5, 05:20 UTC19h 0m
2026-07-04 TAP058 LIS → LIS Jul 4, 10:00 UTCJul 5, 05:20 UTC19h 20m
2026-07-03 TAP224 - Jul 3, 20:55 UTCJul 4, 04:40 UTC7h 45m
2026-07-03 TAP22MI - Jul 3, 17:15 UTCJul 3, 17:50 UTC35m
2026-07-03 TAP22MI - Jul 3, 09:50 UTCJul 3, 10:25 UTC35m
2026-07-02 TAP224 - Jul 2, 21:05 UTCJul 3, 05:00 UTC7h 55m
2026-07-02 TAP22MI - Jul 2, 10:05 UTCJul 2, 18:10 UTC8h 5m
2026-07-01 TAP057 - Jul 1, 10:20 UTCJul 2, 06:00 UTC19h 40m
2026-06-30 TAP104 - Jun 30, 10:20 UTCJul 1, 05:35 UTC19h 15m
2026-06-30 TAP104 LIS → LIS Jun 30, 09:05 UTCJul 1, 05:35 UTC20h 30m
2026-06-29 TAP082 - Jun 29, 19:05 UTCJun 30, 04:15 UTC9h 11m
2026-06-28 TAP087 - Jun 28, 23:50 UTCJun 29, 09:25 UTC9h 35m
2026-06-27 TAP118 - Jun 27, 21:10 UTCJun 28, 15:05 UTC17h 55m
2026-06-27 TAP117 - Jun 27, 14:54 UTCJun 28, 14:14 UTC23h 20m
2026-06-27 TAP204A EWR → LIS Jun 27, 03:20 UTCJun 27, 09:24 UTC6h 5m
2026-06-26 TAP203 LIS → EWR Jun 26, 17:29 UTCJun 27, 01:00 UTC7h 30m
2026-06-26 TAP084 - Jun 26, 04:50 UTCJun 26, 13:59 UTC9h 10m
2026-06-25 TAP083 - Jun 25, 16:55 UTCJun 26, 02:40 UTC9h 45m
2026-06-25 TAP23SL - Jun 25, 00:05 UTCJun 25, 10:20 UTC10h 15m
2026-06-24 TAP237M LIS → SFO Jun 24, 09:15 UTCJun 24, 21:00 UTC11h 45m
2026-06-24 TAP224 - Jun 24, 04:15 UTCJun 24, 04:50 UTC35m
2026-06-23 TAP224 - Jun 23, 21:10 UTCJun 23, 21:45 UTC35m
2026-06-23 TAP22MI LIS → MIA Jun 23, 09:45 UTCJun 23, 18:04 UTC8h 20m
2026-06-22 TAP224 - Jun 22, 20:55 UTCJun 23, 04:35 UTC7h 40m
2026-06-22 TAP22MI - Jun 22, 10:25 UTCJun 22, 18:44 UTC8h 20m
2026-06-21 TAP074 - Jun 21, 18:54 UTCJun 22, 03:50 UTC8h 55m
2026-06-20 TAP075 LIS → GIG Jun 20, 22:54 UTCJun 21, 08:04 UTC9h 10m
2026-06-20 TAP23SL SFO → LIS Jun 20, 05:14 UTCJun 20, 15:19 UTC10h 5m
2026-06-19 TAP237M LIS → SFO Jun 19, 08:34 UTCJun 19, 20:19 UTC11h 45m
2026-06-18 TAP058 - Jun 18, 10:20 UTCJun 19, 05:05 UTC18h 44m
2026-06-18 TAP058 LIS → LIS Jun 18, 09:15 UTCJun 19, 05:05 UTC19h 49m
2026-06-17 TAP082 - Jun 17, 18:45 UTCJun 18, 03:40 UTC8h 55m
2026-06-16 TAP087 - Jun 16, 23:05 UTCJun 17, 08:55 UTC9h 50m

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

Mode-S 4952B1 frequently asked

What is Mode-S code 4952B1?
4952B1 is an ICAO 24-bit transponder address. Allocated to Portugal. Assigned to CS-TUQ.
Where is Mode-S 4952B1 registered?
Mode-S code 4952B1 is allocated to Portugal (PT). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 4952B1 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 4952B1, octal 22251261, decimal 4,805,297.
What flights does 4952B1 operate?
Mode-S 4952B1 has broadcast 20 distinct callsigns, including TAP082, TAP075, TAP087, TAP074, TAP22MI.