sensors Mode-S transponder
4BB4E7
ICAO 24-bit transponder address · allocated to Turkey
Currently assigned to TC-MGG · BOEING 777-300ER
- Hex
- 4BB4E7
- Octal
- 22732347
- Decimal
- 4,961,511
- Country
- TR
- Tail
- TC-MGG
- Type
- B77W
- Flights observed
- 55
- Distinct callsigns
- 20
- Country
- TR
- Last broadcast
- 2h ago
Last known position
Country allocation
The ICAO 24-bit address 4BB4E7 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 |
|---|---|---|---|
| RAM2902 | - | 4 | 2026-05-05 |
| RAM2113 | - | 4 | 2026-06-07 |
| RAM2105 | Royal Air Maroc | 4 | 2026-06-03 |
| RAM2810 | - | 3 | 2026-05-06 |
| RAM8959 | - | 2 | 2026-05-03 |
| RAM2819 | - | 2 | 2026-06-07 |
| RAM2110 | Royal Air Maroc | 2 | 2026-05-08 |
| MGH702 | - | 2 | 2026-04-26 |
| MGH701 | - | 2 | 2026-04-26 |
| RAM8960 | - | 1 | 2026-06-17 |
| RAM2932 | - | 1 | 2026-05-20 |
| RAM2930 | - | 1 | 2026-05-19 |
| RAM2928 | - | 1 | 2026-05-18 |
| RAM2922 | - | 1 | 2026-05-15 |
| RAM2920 | - | 1 | 2026-05-14 |
| RAM2918 | - | 1 | 2026-05-13 |
| RAM2916 | - | 1 | 2026-05-12 |
| RAM2914 | - | 1 | 2026-05-11 |
| RAM2912 | - | 1 | 2026-05-10 |
| RAM2910 | - | 1 | 2026-05-09 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-17 | RAM8960 | - | Jun 17, 08:35 UTC | Jun 17, 12:55 UTC | 4h 20m |
| 2026-06-15 | RAM2129 | - | Jun 15, 10:40 UTC | Jun 16, 01:10 UTC | 14h 30m |
| 2026-06-14 | RAM2127 | - | Jun 14, 11:45 UTC | Jun 15, 02:15 UTC | 14h 29m |
| 2026-06-13 | RAM2125 | - | Jun 13, 08:05 UTC | Jun 13, 22:55 UTC | 14h 50m |
| 2026-06-12 | RAM2123 | - | Jun 12, 02:35 UTC | Jun 12, 17:40 UTC | 15h 5m |
| 2026-06-11 | RAM2121 | - | Jun 11, 06:45 UTC | Jun 11, 21:30 UTC | 14h 45m |
| 2026-06-10 | RAM2119 | - | Jun 10, 10:20 UTC | Jun 11, 01:10 UTC | 14h 50m |
| 2026-06-09 | RAM2117 | - | Jun 9, 12:55 UTC | Jun 10, 03:25 UTC | 14h 30m |
| 2026-06-08 | RAM2019 | JED → AGA | Jun 8, 13:15 UTC | Jun 9, 03:30 UTC | 14h 15m |
| 2026-06-07 | RAM2819 | - | Jun 7, 21:50 UTC | Jun 8, 17:55 UTC | 20h 5m |
| 2026-06-07 | RAM2819 | - | Jun 7, 19:50 UTC | Jun 8, 17:55 UTC | 22h 5m |
| 2026-06-07 | RAM2113 | - | Jun 7, 17:50 UTC | Jun 8, 17:25 UTC | 23h 35m |
| 2026-06-07 | RAM2113 | - | Jun 7, 16:55 UTC | Jun 8, 15:45 UTC | 22h 50m |
| 2026-06-07 | RAM2113 | - | Jun 7, 01:50 UTC | Jun 7, 21:55 UTC | 20h 5m |
| 2026-06-07 | RAM2113 | - | Jun 7, 01:20 UTC | Jun 7, 21:55 UTC | 20h 35m |
| 2026-06-06 | RAM2111 | - | Jun 6, 09:39 UTC | Jun 6, 23:44 UTC | 14h 5m |
| 2026-06-05 | RAM2013 | JED → TNG | Jun 5, 11:00 UTC | Jun 6, 02:00 UTC | 15h 0m |
| 2026-06-04 | RAM2907 | - | Jun 4, 02:20 UTC | Jun 4, 20:25 UTC | 18h 5m |
| 2026-06-03 | RAM2105 | TUN → TNG | Jun 3, 13:35 UTC | Jun 4, 06:00 UTC | 16h 25m |
| 2026-06-03 | RAM2105 | TUN → TNG | Jun 3, 05:50 UTC | Jun 4, 05:35 UTC | 23h 45m |
| 2026-06-03 | RAM2105 | TUN → TNG | Jun 3, 03:50 UTC | Jun 4, 03:45 UTC | 23h 55m |
| 2026-06-03 | RAM2105 | TUN → TNG | Jun 3, 02:35 UTC | Jun 3, 17:35 UTC | 15h 0m |
| 2026-06-02 | RAM2103 | - | Jun 2, 02:30 UTC | Jun 2, 18:05 UTC | 15h 35m |
| 2026-06-01 | RAM2101 | JED → RAK | Jun 1, 00:30 UTC | Jun 1, 12:25 UTC | 11h 55m |
| 2026-05-21 | RAM2134 | - | May 21, 06:00 UTC | May 21, 16:55 UTC | 10h 55m |
| 2026-05-20 | RAM2932 | - | May 20, 04:15 UTC | May 20, 20:20 UTC | 16h 6m |
| 2026-05-19 | RAM2930 | - | May 19, 04:30 UTC | May 19, 19:35 UTC | 15h 5m |
| 2026-05-18 | RAM2928 | - | May 18, 01:00 UTC | May 18, 18:00 UTC | 17h 0m |
| 2026-05-17 | RAM2832 | - | May 17, 01:20 UTC | May 17, 15:55 UTC | 14h 35m |
| 2026-05-15 | RAM2922 | - | May 15, 01:15 UTC | May 15, 16:25 UTC | 15h 9m |
| 2026-05-14 | RAM2920 | - | May 14, 03:25 UTC | May 14, 18:30 UTC | 15h 5m |
| 2026-05-13 | RAM2918 | - | May 13, 01:15 UTC | May 13, 15:20 UTC | 14h 5m |
| 2026-05-12 | RAM2916 | - | May 12, 02:45 UTC | May 12, 15:50 UTC | 13h 5m |
| 2026-05-11 | RAM2914 | - | May 11, 01:30 UTC | May 11, 16:20 UTC | 14h 50m |
| 2026-05-10 | RAM2912 | - | May 10, 06:45 UTC | May 10, 20:30 UTC | 13h 45m |
| 2026-05-09 | RAM2910 | - | May 9, 06:30 UTC | May 9, 20:25 UTC | 13h 55m |
| 2026-05-08 | RAM2110 | AGA → MED | May 8, 09:49 UTC | May 9, 09:45 UTC | 23h 55m |
| 2026-05-08 | RAM2110 | AGA → MED | May 8, 07:50 UTC | May 9, 07:45 UTC | 23h 55m |
| 2026-05-08 | RAM2108 | FEZ → MED | May 8, 05:49 UTC | May 8, 09:49 UTC | 4h 0m |
| 2026-05-07 | RAM2906 | - | May 7, 10:55 UTC | May 8, 01:24 UTC | 14h 29m |
| 2026-05-06 | RAM2810 | - | May 6, 06:15 UTC | May 6, 20:30 UTC | 14h 14m |
| 2026-05-05 | RAM2810 | - | May 5, 21:50 UTC | May 6, 20:30 UTC | 22h 39m |
| 2026-05-05 | RAM2810 | - | May 5, 19:50 UTC | May 6, 19:45 UTC | 23h 54m |
| 2026-05-05 | RAM2902 | - | May 5, 17:50 UTC | May 6, 17:45 UTC | 23h 54m |
| 2026-05-05 | RAM2902 | - | May 5, 17:35 UTC | May 6, 15:40 UTC | 22h 5m |
| 2026-05-05 | RAM2902 | - | May 5, 09:50 UTC | May 6, 09:40 UTC | 23h 50m |
| 2026-05-05 | RAM2902 | - | May 5, 09:10 UTC | May 6, 07:45 UTC | 22h 35m |
| 2026-05-04 | RAM2900 | - | May 4, 07:00 UTC | May 4, 21:25 UTC | 14h 26m |
| 2026-05-03 | RAM2100 | TNG → MED | May 3, 13:50 UTC | May 4, 10:15 UTC | 20h 25m |
| 2026-05-03 | RAM8959 | - | May 3, 11:50 UTC | May 4, 10:15 UTC | 22h 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 TC-MGG page for operator, model, and routing details .