sensors Mode-S transponder

49526B

ICAO 24-bit transponder address · allocated to Portugal

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

Hex
49526B
Octal
22251153
Decimal
4,805,227
Country
PT
Tail
CS-TSK
Type
A20N
Broadcasting now · callsign RZO172 · 675 ft
Flights observed
481
Distinct callsigns
20
Country
PT
Last broadcast
1d ago

Current position

49526B is currently broadcasting. Map zoomed to live position.

Country allocation

The ICAO 24-bit address 49526B 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
RZO127 SATA International 34 2026-07-20
RZO128 SATA International 29 2026-07-21
RZO123 - 28 2026-07-15
RZO121 - 28 2026-07-15
RZO174 - 27 2026-07-21
RZO173 SATA International 27 2026-07-21
RZO120 - 27 2026-07-15
RZO160 SATA International 26 2026-07-20
RZO163 - 23 2026-07-20
RZO124 - 23 2026-07-20
RZO171 - 12 2026-07-21
RZO565 - 11 2026-07-18
RZO328 - 11 2026-07-07
RZO564 - 10 2026-07-18
RZO172 - 10 2026-07-21
RZO183 SATA International 9 2026-07-26
RZO560 SATA International 8 2026-05-13
RZO4021 SATA International 8 2026-05-14
RZO246 - 7 2026-07-06
RZO182 SATA International 7 2026-07-26

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-26 RZO183 OPO → TER Jul 26, 14:50 UTCJul 26, 20:20 UTC5h 30m
2026-07-26 RZO182 TER → OPO Jul 26, 07:55 UTCJul 26, 13:35 UTC5h 40m
2026-07-25 RZO134 TER → LIS Jul 25, 15:00 UTCJul 25, 20:35 UTC5h 35m
2026-07-25 RZO182 - Jul 25, 08:15 UTCJul 25, 13:50 UTC5h 35m
2026-07-24 RZO134 TER → LIS Jul 24, 15:35 UTCJul 24, 21:05 UTC5h 30m
2026-07-24 RZO131 LIS → TER Jul 24, 08:20 UTCJul 24, 13:55 UTC5h 35m
2026-07-23 RZO183 OPO → LIS Jul 23, 15:50 UTCJul 23, 21:25 UTC5h 35m
2026-07-23 RZO131 LIS → TER Jul 23, 08:05 UTCJul 23, 14:25 UTC6h 20m
2026-07-22 RZO134 TER → LIS Jul 22, 14:50 UTCJul 22, 20:45 UTC5h 55m
2026-07-22 RZO182 - Jul 22, 12:50 UTCJul 22, 13:30 UTC40m
2026-07-21 RZO128 PDL → LIS Jul 21, 23:25 UTCJul 22, 00:00 UTC35m
2026-07-21 RZO128 PDL → LIS Jul 21, 22:10 UTCJul 21, 22:20 UTC10m
2026-07-21 RZO173 OPO → PDL Jul 21, 18:40 UTCJul 21, 19:25 UTC45m
2026-07-21 RZO174 - Jul 21, 16:45 UTCJul 21, 17:20 UTC35m
2026-07-21 RZO174 - Jul 21, 15:30 UTCJul 21, 15:40 UTC10m
2026-07-21 RZO171 - Jul 21, 11:55 UTCJul 21, 12:40 UTC45m
2026-07-21 RZO172 - Jul 21, 09:45 UTCJul 21, 10:25 UTC40m
2026-07-20 RZO127 LIS → PDL Jul 20, 18:55 UTCJul 20, 19:40 UTC45m
2026-07-20 RZO124 - Jul 20, 16:20 UTCJul 20, 17:05 UTC45m
2026-07-20 RZO163 - Jul 20, 12:35 UTCJul 20, 14:00 UTC1h 25m
2026-07-20 RZO160 PDL → FNC Jul 20, 10:10 UTCJul 20, 11:30 UTC1h 20m
2026-07-20 RZO177 OPO → TER Jul 20, 07:00 UTCJul 20, 07:40 UTC40m
2026-07-19 RZO176 PDL → OPO Jul 19, 23:25 UTCJul 20, 00:05 UTC40m
2026-07-19 RZO173 OPO → PDL Jul 19, 18:50 UTCJul 19, 19:30 UTC40m
2026-07-19 RZO174 - Jul 19, 16:40 UTCJul 19, 17:25 UTC45m
2026-07-19 RZO163 - Jul 19, 13:45 UTCJul 19, 13:55 UTC10m
2026-07-19 RZO163 - Jul 19, 12:30 UTCJul 19, 12:40 UTC10m
2026-07-19 RZO160 - Jul 19, 11:05 UTCJul 19, 11:10 UTC5m
2026-07-19 RZO160 - Jul 19, 09:50 UTCJul 19, 10:00 UTC10m
2026-07-19 RZO177 OPO → TER Jul 19, 05:25 UTCJul 19, 06:20 UTC55m
2026-07-18 RZO176 PDL → OPO Jul 18, 23:25 UTCJul 19, 00:05 UTC40m
2026-07-18 RZO173 OPO → PDL Jul 18, 18:50 UTCJul 18, 19:30 UTC40m
2026-07-18 RZO174 - Jul 18, 16:45 UTCJul 18, 17:25 UTC40m
2026-07-18 RZO163 - Jul 18, 12:25 UTCJul 18, 12:35 UTC10m
2026-07-18 RZO160 - Jul 18, 11:10 UTCJul 18, 11:20 UTC10m
2026-07-18 RZO565 - Jul 18, 04:25 UTCJul 18, 06:30 UTC2h 5m
2026-07-18 RZO564 - Jul 18, 00:29 UTCJul 18, 03:05 UTC2h 36m
2026-07-17 RZO564 - Jul 17, 23:10 UTCJul 17, 23:20 UTC10m
2026-07-17 RZO173 - Jul 17, 20:55 UTCJul 17, 21:05 UTC10m
2026-07-17 RZO173 - Jul 17, 19:00 UTCJul 17, 19:40 UTC40m
2026-07-17 RZO174 - Jul 17, 16:49 UTCJul 17, 17:25 UTC35m
2026-07-17 RZO174 - Jul 17, 15:29 UTCJul 17, 15:40 UTC10m
2026-07-17 RZO171 - Jul 17, 14:10 UTCJul 17, 14:20 UTC10m
2026-07-17 RZO171 - Jul 17, 12:15 UTCJul 17, 12:55 UTC40m
2026-07-17 RZO172 - Jul 17, 09:50 UTCJul 17, 10:30 UTC40m
2026-07-17 RZO172 - Jul 17, 08:35 UTCJul 17, 08:45 UTC10m
2026-07-16 RZO173 - Jul 16, 18:44 UTCJul 16, 19:30 UTC45m
2026-07-16 RZO174 - Jul 16, 16:44 UTCJul 16, 17:25 UTC40m
2026-07-16 RZO163 - Jul 16, 13:54 UTCJul 16, 14:05 UTC10m
2026-07-16 RZO163 - Jul 16, 12:44 UTCJul 16, 12:55 UTC10m

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

Mode-S 49526B frequently asked

What is Mode-S code 49526B?
49526B is an ICAO 24-bit transponder address. Allocated to Portugal. Assigned to CS-TSK.
Where is Mode-S 49526B registered?
Mode-S code 49526B is allocated to Portugal (PT). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 49526B broadcasting right now?
Yes. Mode-S 49526B is currently airborne.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 49526B, octal 22251153, decimal 4,805,227.
What flights does 49526B operate?
Mode-S 49526B has broadcast 20 distinct callsigns, including RZO127, RZO128, RZO123, RZO121, RZO174.