sensors Mode-S transponder

4B9DA2

ICAO 24-bit transponder address · allocated to Turkey

Currently assigned to TC-GMB · AIRBUS A-320

Hex
4B9DA2
Octal
22716642
Decimal
4,955,554
Country
TR
Tail
TC-GMB
Type
A320
No current signal · last broadcast 9d ago
Flights observed
56
Distinct callsigns
20
Country
TR
Last broadcast
9d ago

Last known position

Most recent position reported by Mode-S 4B9DA2.

Country allocation

The ICAO 24-bit address 4B9DA2 falls within the block assigned to Turkey (TR) by ICAO Annex 10, Volume III. Every aircraft registered in Turkey 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
NMA160 Nesma Airlines 4 2026-07-23
NMA153 Nesma Airlines 3 2026-07-19
NMA123 - 3 2026-07-14
NMA331 Nesma Airlines 2 2026-07-21
NMA330 Nesma Airlines 2 2026-07-21
NMA200 - 2 2026-07-16
NMA173 Nesma Airlines 2 2026-07-23
NMA172 - 2 2026-07-16
NMA162 Nesma Airlines 2 2026-07-24
NMA152 - 2 2026-07-18
NMA140 - 2 2026-07-23
MGH792 Mavi Gok Airlines 2 2026-05-31
MGH791 Mavi Gok Airlines 2 2026-05-31
NMA7121 Nesma Airlines 1 2026-07-19
NMA7120 Nesma Airlines 1 2026-07-19
NMA301 - 1 2026-07-15
NMA300 - 1 2026-07-15
NMA177 - 1 2026-07-11
NMA165 - 1 2026-07-22
NMA164 Nesma Airlines 1 2026-07-22

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-24 NMA163 RUH → CAI Jul 24, 13:15 UTCJul 24, 13:25 UTC10m
2026-07-24 NMA162 CAI → RUH Jul 24, 08:00 UTCJul 24, 08:45 UTC45m
2026-07-23 NMA173 JED → CAI Jul 23, 17:05 UTCJul 23, 21:40 UTC4h 35m
2026-07-23 NMA140 - Jul 23, 09:15 UTCJul 23, 13:45 UTC4h 30m
2026-07-23 NMA161 RUH → CAI Jul 23, 06:40 UTCJul 23, 07:20 UTC40m
2026-07-23 NMA160 CAI → RUH Jul 23, 01:30 UTCJul 23, 02:20 UTC50m
2026-07-22 NMA165 - Jul 22, 21:15 UTCJul 22, 21:45 UTC30m
2026-07-22 NMA164 CAI → RUH Jul 22, 16:05 UTCJul 22, 16:55 UTC50m
2026-07-22 NMA160 CAI → RUH Jul 22, 00:40 UTCJul 22, 01:35 UTC55m
2026-07-21 NMA331 SAW → CAI Jul 21, 12:55 UTCJul 21, 14:20 UTC1h 25m
2026-07-21 NMA330 CAI → TIF Jul 21, 09:15 UTCJul 21, 10:55 UTC1h 40m
2026-07-20 NMA059 - Jul 20, 16:00 UTCJul 20, 16:10 UTC10m
2026-07-20 NMA058 CAI → HRG Jul 20, 13:25 UTCJul 20, 13:35 UTC10m
2026-07-19 NMA142 - Jul 19, 17:20 UTCJul 19, 21:35 UTC4h 15m
2026-07-19 NMA7121 NAP → SSH Jul 19, 11:45 UTCJul 19, 13:50 UTC2h 5m
2026-07-19 NMA7120 SSH → NAP Jul 19, 07:55 UTCJul 19, 09:35 UTC1h 40m
2026-07-19 NMA153 DMM → CAI Jul 19, 04:00 UTCJul 19, 04:25 UTC25m
2026-07-18 NMA152 - Jul 18, 22:30 UTCJul 18, 23:10 UTC40m
2026-07-18 NMA160 - Jul 18, 01:34 UTCJul 18, 07:05 UTC5h 31m
2026-07-17 NMA331 SAW → CAI Jul 17, 12:35 UTCJul 17, 14:00 UTC1h 25m
2026-07-17 NMA330 CAI → TIF Jul 17, 09:20 UTCJul 17, 10:50 UTC1h 30m
2026-07-16 NMA173 JED → CAI Jul 16, 21:45 UTCJul 16, 22:15 UTC30m
2026-07-16 NMA172 - Jul 16, 17:10 UTCJul 16, 17:20 UTC10m
2026-07-16 NMA200 - Jul 16, 05:00 UTCJul 16, 11:15 UTC6h 15m
2026-07-15 NMA301 - Jul 15, 22:25 UTCJul 16, 01:40 UTC3h 15m
2026-07-15 NMA300 - Jul 15, 16:10 UTCJul 15, 19:55 UTC3h 45m
2026-07-15 NMA172 - Jul 15, 04:25 UTCJul 15, 14:15 UTC9h 50m
2026-07-14 NMA123 - Jul 14, 15:10 UTCJul 14, 18:40 UTC3h 30m
2026-07-14 NMA200 - Jul 14, 05:15 UTCJul 14, 11:45 UTC6h 30m
2026-07-12 NMA123 - Jul 12, 14:45 UTCJul 12, 15:05 UTC20m
2026-07-11 NMA177 - Jul 11, 14:00 UTCJul 11, 23:55 UTC9h 55m
2026-07-11 NMA153 - Jul 11, 03:20 UTCJul 11, 03:55 UTC35m
2026-07-11 NMA153 - Jul 11, 01:35 UTCJul 11, 01:50 UTC15m
2026-07-10 NMA152 - Jul 10, 21:25 UTCJul 10, 22:15 UTC50m
2026-07-10 NMA162 - Jul 10, 09:55 UTCJul 10, 15:50 UTC5h 55m
2026-07-10 NMA155 - Jul 10, 07:15 UTCJul 10, 07:35 UTC20m
2026-07-10 NMA154 - Jul 10, 01:45 UTCJul 10, 02:35 UTC50m
2026-07-09 NMA123 - Jul 9, 18:20 UTCJul 9, 21:50 UTC3h 30m
2026-07-09 NMA141 - Jul 9, 14:45 UTCJul 9, 15:15 UTC30m
2026-07-09 NMA140 - Jul 9, 10:55 UTCJul 9, 11:35 UTC40m
2026-07-09 NMA160 - Jul 9, 03:05 UTCJul 9, 08:40 UTC5h 35m
2026-07-08 BBT9001 - Jul 8, 12:05 UTCJul 8, 13:05 UTC1h 0m
2026-07-03 FHY822 - Jul 3, 08:25 UTCJul 3, 10:20 UTC1h 55m
2026-07-03 FHY821 - Jul 3, 04:55 UTCJul 3, 07:00 UTC2h 5m
2026-07-02 HYM315 - Jul 2, 21:15 UTCJul 2, 22:40 UTC1h 25m
2026-07-02 HYM318 - Jul 2, 00:55 UTCJul 2, 02:15 UTC1h 20m
2026-05-31 MGH792 BER → AYT May 31, 10:35 UTCMay 31, 13:15 UTC2h 40m
2026-05-31 MGH791 AYT → BER May 31, 08:25 UTCMay 31, 08:55 UTC30m
2026-05-24 MGH792 BER → AYT May 24, 10:05 UTCMay 24, 13:05 UTC3h 0m
2026-05-24 MGH791 AYT → BER May 24, 05:45 UTCMay 24, 08:45 UTC3h 0m

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

Mode-S 4B9DA2 frequently asked

What is Mode-S code 4B9DA2?
4B9DA2 is an ICAO 24-bit transponder address. Allocated to Turkey. Assigned to TC-GMB.
Where is Mode-S 4B9DA2 registered?
Mode-S code 4B9DA2 is allocated to Turkey (TR). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 4B9DA2 broadcasting right now?
No active broadcast right now. Last signal was 9d ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 4B9DA2, octal 22716642, decimal 4,955,554.
What flights does 4B9DA2 operate?
Mode-S 4B9DA2 has broadcast 20 distinct callsigns, including NMA160, NMA153, NMA123, NMA331, NMA330.