sensors Mode-S transponder
4BB46F
ICAO 24-bit transponder address · allocated to Turkey
Currently assigned to TC-MCO · AIRBUS A-330-300
- Hex
- 4BB46F
- Octal
- 22732157
- Decimal
- 4,961,391
- Country
- TR
- Tail
- TC-MCO
- Type
- A333
- Flights observed
- 111
- Distinct callsigns
- 20
- Country
- TR
- Last broadcast
- 1h ago
Last known position
Country allocation
The ICAO 24-bit address 4BB46F 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 |
|---|---|---|---|
| MNB412 | MNG Airlines | 11 | 2026-05-04 |
| MNB610 | - | 6 | 2026-05-14 |
| MNB413 | MNG Airlines | 6 | 2026-05-05 |
| MNB180 | MNG Airlines | 5 | 2026-05-09 |
| MNB179 | MNG Airlines | 5 | 2026-05-05 |
| MNB601 | MNG Airlines | 4 | 2026-05-23 |
| MNB2300 | - | 4 | 2026-05-17 |
| MNB600 | MNG Airlines | 3 | 2026-05-22 |
| MNB446 | - | 3 | 2026-05-02 |
| MNB430 | MNG Airlines | 3 | 2026-04-17 |
| MNB6564 | - | 2 | 2026-05-30 |
| MNB6300 | - | 2 | 2026-05-20 |
| MNB6101 | - | 2 | 2026-05-19 |
| MNB510 | MNG Airlines | 2 | 2026-05-17 |
| MNB447 | - | 2 | 2026-05-02 |
| MNB432 | - | 2 | 2026-04-17 |
| MNB380 | MNG Airlines | 2 | 2026-05-15 |
| MNB300 | MNG Airlines | 2 | 2026-04-16 |
| MNB232 | - | 2 | 2026-05-07 |
| MNB231 | MNG Airlines | 2 | 2026-05-07 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-30 | MNB6564 | - | May 30, 05:30 UTC | May 30, 05:45 UTC | 15m |
| 2026-05-26 | MNB296 | - | May 26, 23:54 UTC | May 27, 02:19 UTC | 2h 25m |
| 2026-05-25 | MNB295 | ALA → IST | May 25, 23:14 UTC | May 26, 01:05 UTC | 1h 50m |
| 2026-05-25 | MNB294 | TBS → HKG | May 25, 03:50 UTC | May 25, 20:19 UTC | 16h 29m |
| 2026-05-24 | MNB292 | BFS → BFS | May 24, 21:20 UTC | May 24, 23:35 UTC | 2h 15m |
| 2026-05-23 | MNB291 | ESB → ESB | May 23, 19:25 UTC | May 23, 21:30 UTC | 2h 5m |
| 2026-05-23 | MNB290 | - | May 23, 11:55 UTC | May 23, 12:40 UTC | 45m |
| 2026-05-23 | MNB601 | JFK → IST | May 23, 03:15 UTC | May 23, 05:40 UTC | 2h 25m |
| 2026-05-22 | MNB600 | CGN → JFK | May 22, 19:20 UTC | May 22, 21:50 UTC | 2h 30m |
| 2026-05-22 | MNB601 | JFK → IST | May 22, 03:35 UTC | May 22, 06:10 UTC | 2h 35m |
| 2026-05-21 | MNB600 | CGN → JFK | May 21, 19:15 UTC | May 21, 21:55 UTC | 2h 40m |
| 2026-05-20 | MNB6300 | - | May 20, 19:50 UTC | May 21, 14:50 UTC | 19h 0m |
| 2026-05-20 | MNB6300 | - | May 20, 19:40 UTC | May 21, 14:50 UTC | 19h 10m |
| 2026-05-20 | MNB602 | - | May 20, 08:00 UTC | May 20, 11:15 UTC | 3h 15m |
| 2026-05-20 | MNB601 | JFK → IST | May 20, 04:35 UTC | May 20, 05:50 UTC | 1h 16m |
| 2026-05-19 | MNB600 | CGN → JFK | May 19, 23:25 UTC | May 20, 02:00 UTC | 2h 35m |
| 2026-05-19 | MNB6101 | - | May 19, 14:10 UTC | May 19, 16:10 UTC | 2h 0m |
| 2026-05-18 | MNB6101 | - | May 18, 19:50 UTC | May 19, 16:10 UTC | 20h 20m |
| 2026-05-18 | MNB6100 | - | May 18, 19:25 UTC | May 19, 16:10 UTC | 20h 45m |
| 2026-05-18 | MNB2301 | - | May 18, 11:40 UTC | May 18, 11:50 UTC | 10m |
| 2026-05-17 | MNB2301 | - | May 17, 15:50 UTC | May 18, 11:00 UTC | 19h 10m |
| 2026-05-17 | MNB2300 | - | May 17, 15:15 UTC | May 18, 11:00 UTC | 19h 45m |
| 2026-05-17 | MNB2300 | - | May 17, 14:20 UTC | May 17, 14:35 UTC | 15m |
| 2026-05-17 | MNB510 | ALA → IST | May 17, 10:35 UTC | May 17, 10:45 UTC | 10m |
| 2026-05-16 | MNB510 | ALA → IST | May 16, 22:15 UTC | May 17, 09:45 UTC | 11h 30m |
| 2026-05-16 | MNB6564 | - | May 16, 03:25 UTC | May 16, 18:30 UTC | 15h 6m |
| 2026-05-16 | MNB382 | - | May 16, 01:20 UTC | May 16, 01:35 UTC | 15m |
| 2026-05-15 | MNB380 | HKG → IST | May 15, 10:00 UTC | May 15, 21:10 UTC | 11h 9m |
| 2026-05-15 | MNB380 | HKG → IST | May 15, 08:40 UTC | May 15, 08:50 UTC | 10m |
| 2026-05-14 | MNB313 | JFK → IST | May 14, 19:00 UTC | May 15, 03:45 UTC | 8h 45m |
| 2026-05-14 | MNB312 | LGG → JFK | May 14, 06:55 UTC | May 14, 15:01 UTC | 8h 5m |
| 2026-05-14 | MNB610 | - | May 14, 02:50 UTC | May 14, 05:20 UTC | 2h 30m |
| 2026-05-13 | MNB601 | JFK → IST | May 13, 04:55 UTC | May 13, 07:05 UTC | 2h 10m |
| 2026-05-13 | MNB9392 | CGN → IST | May 13, 01:10 UTC | May 13, 02:10 UTC | 1h 0m |
| 2026-05-12 | MNB9391 | EMA → IST | May 12, 19:25 UTC | May 12, 23:05 UTC | 3h 40m |
| 2026-05-11 | MNB503 | - | May 11, 02:15 UTC | May 11, 17:50 UTC | 15h 36m |
| 2026-05-10 | MNB943 | - | May 10, 18:29 UTC | May 10, 19:50 UTC | 1h 20m |
| 2026-05-10 | MNB942 | - | May 10, 14:54 UTC | May 10, 16:04 UTC | 1h 10m |
| 2026-05-10 | MNB940 | ISL → CMN | May 10, 04:19 UTC | May 10, 12:15 UTC | 7h 55m |
| 2026-05-09 | MNB180 | AMM → AMM | May 9, 10:25 UTC | May 9, 11:45 UTC | 1h 20m |
| 2026-05-08 | MNB180 | AMM → AMM | May 8, 23:40 UTC | May 9, 00:00 UTC | 20m |
| 2026-05-08 | MNB234 | - | May 8, 05:00 UTC | May 8, 19:45 UTC | 14h 45m |
| 2026-05-08 | MNB233 | HKG → KGF | May 8, 02:59 UTC | May 8, 03:14 UTC | 15m |
| 2026-05-07 | MNB232 | - | May 7, 12:50 UTC | May 7, 16:35 UTC | 3h 45m |
| 2026-05-07 | MNB232 | SHJ → SHJ | May 7, 09:40 UTC | May 7, 10:05 UTC | 25m |
| 2026-05-07 | MNB231 | HKG → KGF | May 7, 01:25 UTC | May 7, 03:35 UTC | 2h 10m |
| 2026-05-06 | MNB231 | HKG → KGF | May 6, 23:20 UTC | May 6, 23:35 UTC | 15m |
| 2026-05-06 | MNB230 | - | May 6, 16:35 UTC | May 6, 17:00 UTC | 25m |
| 2026-05-06 | MNB229 | IST → ISL | May 6, 01:55 UTC | May 6, 14:20 UTC | 12h 24m |
| 2026-05-05 | MNB229 | IST → ISL | May 5, 23:50 UTC | May 6, 00:05 UTC | 15m |
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-MCO page for operator, model, and routing details .