sensors Mode-S transponder
4BB4EF
ICAO 24-bit transponder address · allocated to Turkey
Currently assigned to TC-MGO · BOEING 737-800
- Hex
- 4BB4EF
- Octal
- 22732357
- Decimal
- 4,961,519
- Country
- TR
- Tail
- TC-MGO
- Type
- B738
- Flights observed
- 38
- Distinct callsigns
- 20
- Country
- TR
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 4BB4EF 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 |
|---|---|---|---|
| MGH672 | Mavi Gok Airlines | 3 | 2026-06-20 |
| MGH671 | Mavi Gok Airlines | 3 | 2026-06-20 |
| MGH876 | - | 2 | 2026-07-12 |
| MGH875 | - | 2 | 2026-07-12 |
| MGH732 | - | 2 | 2026-04-13 |
| MGH272 | - | 2 | 2026-07-07 |
| MGH271 | - | 2 | 2026-07-07 |
| TAH1105 | - | 1 | 2026-05-25 |
| MGH972 | - | 1 | 2026-06-07 |
| MGH971 | - | 1 | 2026-06-07 |
| MGH878 | Mavi Gok Airlines | 1 | 2026-06-08 |
| MGH877 | Mavi Gok Airlines | 1 | 2026-06-08 |
| MGH792 | - | 1 | 2026-06-28 |
| MGH791 | - | 1 | 2026-06-28 |
| MGH731 | - | 1 | 2026-04-12 |
| MGH728 | Mavi Gok Airlines | 1 | 2026-06-14 |
| MGH727 | Mavi Gok Airlines | 1 | 2026-06-14 |
| MGH642 | - | 1 | 2026-07-11 |
| MGH641 | - | 1 | 2026-07-11 |
| MGH628 | Mavi Gok Airlines | 1 | 2026-06-14 |
Recent flights last 38
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-12 | MGH876 | POZ → AYT | Jul 12, 09:30 UTC | Jul 12, 12:10 UTC | 2h 40m |
| 2026-07-12 | MGH875 | AYT → POZ | Jul 12, 05:20 UTC | Jul 12, 08:10 UTC | 2h 50m |
| 2026-07-11 | MGH642 | - | Jul 11, 12:05 UTC | Jul 11, 14:10 UTC | 2h 5m |
| 2026-07-11 | MGH641 | - | Jul 11, 08:40 UTC | Jul 11, 10:45 UTC | 2h 5m |
| 2026-07-07 | MGH272 | - | Jul 7, 10:35 UTC | Jul 7, 13:05 UTC | 2h 30m |
| 2026-07-07 | MGH271 | - | Jul 7, 05:55 UTC | Jul 7, 08:55 UTC | 3h 0m |
| 2026-07-05 | MGH876 | - | Jul 5, 09:30 UTC | Jul 5, 12:30 UTC | 3h 0m |
| 2026-07-05 | MGH875 | AYT → POZ | Jul 5, 05:30 UTC | Jul 5, 08:25 UTC | 2h 55m |
| 2026-07-03 | MGH514 | - | Jul 3, 09:30 UTC | Jul 3, 11:10 UTC | 1h 40m |
| 2026-07-03 | MGH513 | - | Jul 3, 06:25 UTC | Jul 3, 07:45 UTC | 1h 20m |
| 2026-07-01 | MGH340 | - | Jul 1, 09:10 UTC | Jul 1, 11:25 UTC | 2h 15m |
| 2026-07-01 | MGH339 | AYT → BUD | Jul 1, 05:15 UTC | Jul 1, 07:20 UTC | 2h 5m |
| 2026-06-28 | MGH792 | BER → AYT | Jun 28, 10:44 UTC | Jun 28, 13:45 UTC | 3h 0m |
| 2026-06-28 | MGH791 | - | Jun 28, 06:10 UTC | Jun 28, 09:10 UTC | 3h 0m |
| 2026-06-24 | MGH342 | DEB → AYT | Jun 24, 10:39 UTC | Jun 24, 12:44 UTC | 2h 5m |
| 2026-06-24 | MGH341 | - | Jun 24, 07:10 UTC | Jun 24, 09:09 UTC | 2h 0m |
| 2026-06-20 | MGH672 | MUC → AYT | Jun 20, 10:55 UTC | Jun 20, 13:44 UTC | 2h 50m |
| 2026-06-20 | MGH671 | AYT → MUC | Jun 20, 06:14 UTC | Jun 20, 09:05 UTC | 2h 50m |
| 2026-06-16 | MGH272 | - | Jun 16, 10:49 UTC | Jun 16, 13:19 UTC | 2h 30m |
| 2026-06-16 | MGH271 | - | Jun 16, 06:10 UTC | Jun 16, 09:15 UTC | 3h 5m |
| 2026-06-14 | MGH728 | HAJ → AYT | Jun 14, 22:25 UTC | Jun 15, 01:25 UTC | 3h 0m |
| 2026-06-14 | MGH727 | AYT → HAJ | Jun 14, 17:10 UTC | Jun 14, 20:55 UTC | 3h 45m |
| 2026-06-14 | MGH628 | HAJ → AYT | Jun 14, 08:05 UTC | Jun 14, 11:20 UTC | 3h 15m |
| 2026-06-14 | MGH4002 | - | Jun 14, 02:45 UTC | Jun 14, 06:20 UTC | 3h 35m |
| 2026-06-13 | MGH672 | MUC → AYT | Jun 13, 10:30 UTC | Jun 13, 12:40 UTC | 2h 10m |
| 2026-06-13 | MGH671 | AYT → MUC | Jun 13, 06:10 UTC | Jun 13, 09:05 UTC | 2h 55m |
| 2026-06-08 | MGH878 | WRO → AYT | Jun 8, 11:55 UTC | Jun 8, 14:35 UTC | 2h 40m |
| 2026-06-08 | MGH877 | AYT → WRO | Jun 8, 06:50 UTC | Jun 8, 09:40 UTC | 2h 50m |
| 2026-06-07 | MGH972 | - | Jun 7, 10:00 UTC | Jun 7, 12:40 UTC | 2h 40m |
| 2026-06-07 | MGH971 | AYT → WAW | Jun 7, 05:35 UTC | Jun 7, 08:20 UTC | 2h 45m |
| 2026-06-06 | MGH672 | MUC → AYT | Jun 6, 10:34 UTC | Jun 6, 12:49 UTC | 2h 15m |
| 2026-06-06 | MGH671 | AYT → MUC | Jun 6, 06:05 UTC | Jun 6, 08:50 UTC | 2h 45m |
| 2026-06-02 | MGH260 | - | Jun 2, 22:25 UTC | Jun 3, 01:40 UTC | 3h 15m |
| 2026-06-02 | MGH259 | AYT → FMO | Jun 2, 17:35 UTC | Jun 2, 21:05 UTC | 3h 30m |
| 2026-05-25 | TAH1105 | - | May 25, 11:10 UTC | May 25, 22:30 UTC | 11h 19m |
| 2026-04-13 | MGH732 | - | Apr 13, 00:20 UTC | Apr 13, 00:50 UTC | 30m |
| 2026-04-12 | MGH732 | - | Apr 12, 23:55 UTC | Apr 13, 00:50 UTC | 55m |
| 2026-04-12 | MGH731 | - | Apr 12, 17:35 UTC | Apr 12, 20:15 UTC | 2h 40m |
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-MGO page for operator, model, and routing details .