sensors Mode-S transponder

49530B

ICAO 24-bit transponder address · allocated to Portugal

Currently assigned to CS-TXK · AIRBUS A-321neo

Hex
49530B
Octal
22251413
Decimal
4,805,387
Country
PT
Tail
CS-TXK
Type
A21N
Broadcasting now · callsign TAP257N · 31,975 ft
Flights observed
268
Distinct callsigns
20
Country
PT
Last broadcast
18m ago

Current position

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

Country allocation

The ICAO 24-bit address 49530B 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
TAP232Y - 11 2026-07-01
TAP231P - 11 2026-07-01
TAP215 - 11 2026-07-02
TAP262M - 10 2026-07-13
TAP216L - 10 2026-07-03
TAP212 - 10 2026-07-09
TAP261 - 9 2026-07-12
TAP211 - 9 2026-07-08
TAP201 - 9 2026-07-13
TAP202A - 8 2026-07-13
TAP015 - 7 2026-07-11
TAP218 - 6 2026-07-03
TAP217C - 6 2026-07-03
TAP257N - 5 2026-07-14
TAP234Y - 5 2026-06-23
TAP233 - 5 2026-06-22
TAP1704 - 5 2026-07-08
TAP1703 - 5 2026-07-08
TAP89WT - 4 2026-06-16
TAP3961 - 4 2026-07-07

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-14 TAP257N - Jul 14, 10:10 UTCJul 14, 10:45 UTC35m
2026-07-13 TAP202A EWR → LIS Jul 13, 22:00 UTCJul 14, 04:35 UTC6h 35m
2026-07-13 TAP201 LIS → EWR Jul 13, 12:20 UTCJul 13, 19:30 UTC7h 10m
2026-07-13 TAP262M YYZ → LIS Jul 13, 03:10 UTCJul 13, 10:15 UTC7h 5m
2026-07-12 TAP261 LIS → YYZ Jul 12, 17:10 UTCJul 13, 00:35 UTC7h 25m
2026-07-12 TAP016 - Jul 12, 07:45 UTCJul 12, 14:55 UTC7h 10m
2026-07-11 TAP015 - Jul 11, 22:10 UTCJul 12, 05:30 UTC7h 20m
2026-07-11 TAP1862 - Jul 11, 18:05 UTCJul 11, 18:55 UTC50m
2026-07-11 TAP1861 - Jul 11, 15:20 UTCJul 11, 15:30 UTC10m
2026-07-11 TAP1861 - Jul 11, 13:25 UTCJul 11, 14:10 UTC45m
2026-07-11 TAP262M - Jul 11, 04:50 UTCJul 11, 09:50 UTC5h 0m
2026-07-11 TAP262M - Jul 11, 03:10 UTCJul 11, 04:45 UTC1h 35m
2026-07-10 TAP261 LIS → YYZ Jul 10, 17:00 UTCJul 11, 00:40 UTC7h 40m
2026-07-10 TAP262M YYZ → LIS Jul 10, 04:10 UTCJul 10, 10:55 UTC6h 45m
2026-07-09 TAP261 LIS → YYZ Jul 9, 17:55 UTCJul 10, 01:30 UTC7h 35m
2026-07-09 TAP1929 OPO → LIS Jul 9, 15:20 UTCJul 9, 16:00 UTC40m
2026-07-09 TAP212 EWR → OPO Jul 9, 03:15 UTCJul 9, 09:50 UTC6h 35m
2026-07-08 TAP211 OPO → EWR Jul 8, 17:50 UTCJul 9, 00:40 UTC6h 50m
2026-07-08 TAP1704 FNC → OPO Jul 8, 14:30 UTCJul 8, 16:00 UTC1h 30m
2026-07-08 TAP1703 OPO → FNC Jul 8, 11:55 UTCJul 8, 13:40 UTC1h 45m
2026-07-08 TAP212 EWR → OPO Jul 8, 03:40 UTCJul 8, 10:10 UTC6h 30m
2026-07-07 TAP211 OPO → EWR Jul 7, 17:30 UTCJul 8, 00:35 UTC7h 5m
2026-07-07 TAP9255 OPO → LIS Jul 7, 14:05 UTCJul 7, 14:40 UTC35m
2026-07-07 TAP3961 OPO → LIS Jul 7, 11:35 UTCJul 7, 12:20 UTC45m
2026-07-07 TAP212 EWR → OPO Jul 7, 03:30 UTCJul 7, 09:45 UTC6h 15m
2026-07-06 TAP211 OPO → EWR Jul 6, 17:35 UTCJul 7, 00:55 UTC7h 20m
2026-07-06 TAP228 - Jul 6, 05:20 UTCJul 6, 11:05 UTC5h 45m
2026-07-06 TAP227 BOS → BOS Jul 6, 00:20 UTCJul 6, 00:25 UTC5m
2026-07-05 TAP227 OPO → BOS Jul 5, 17:15 UTCJul 6, 00:10 UTC6h 55m
2026-07-05 TAP212 - Jul 5, 05:00 UTCJul 5, 11:05 UTC6h 5m
2026-07-04 TAP211 OPO → EWR Jul 4, 18:50 UTCJul 5, 02:05 UTC7h 15m
2026-07-04 TAP1930 LIS → OPO Jul 4, 16:30 UTCJul 4, 17:05 UTC35m
2026-07-04 TAP88TM FNC → LIS Jul 4, 12:10 UTCJul 4, 13:45 UTC1h 35m
2026-07-04 TAP1687 - Jul 4, 10:45 UTCJul 4, 10:55 UTC10m
2026-07-04 TAP1687 - Jul 4, 09:25 UTCJul 4, 10:15 UTC50m
2026-07-03 TAP218 BOS → LIS Jul 3, 22:40 UTCJul 4, 04:50 UTC6h 10m
2026-07-03 TAP217C LIS → BOS Jul 3, 11:25 UTCJul 3, 18:05 UTC6h 40m
2026-07-03 TAP216L BOS → LIS Jul 3, 03:25 UTCJul 3, 09:35 UTC6h 10m
2026-07-02 TAP215 LIS → BOS Jul 2, 17:35 UTCJul 3, 00:35 UTC7h 0m
2026-07-02 TAP1359 - Jul 2, 13:40 UTCJul 2, 16:00 UTC2h 20m
2026-07-02 TAP52TP LIS → LHR Jul 2, 09:40 UTCJul 2, 12:05 UTC2h 25m
2026-07-01 TAP232Y IAD → LIS Jul 1, 22:20 UTCJul 2, 05:20 UTC7h 0m
2026-07-01 TAP231P LIS → IAD Jul 1, 11:00 UTCJul 1, 18:30 UTC7h 30m
2026-07-01 TAP216L BOS → LIS Jul 1, 03:00 UTCJul 1, 09:05 UTC6h 5m
2026-06-30 TAP215 - Jun 30, 17:30 UTCJun 30, 23:55 UTC6h 25m
2026-06-30 TAP15NC MAD → LIS Jun 30, 14:55 UTCJun 30, 15:55 UTC1h 0m
2026-06-30 TAP14NC - Jun 30, 12:45 UTCJun 30, 13:40 UTC55m
2026-06-30 TAP052 - Jun 30, 09:20 UTCJun 30, 10:10 UTC50m
2026-06-29 TAP051 - Jun 29, 10:50 UTCJun 30, 10:10 UTC23h 20m
2026-06-29 TAP051 - Jun 29, 10:24 UTCJun 29, 11:50 UTC1h 25m

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

Mode-S 49530B frequently asked

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