sensors Mode-S transponder
4BB0EF
ICAO 24-bit transponder address · allocated to Turkey
Currently assigned to TC-LGO · AIRBUS A-350-900
- Hex
- 4BB0EF
- Octal
- 22730357
- Decimal
- 4,960,495
- Country
- TR
- Tail
- TC-LGO
- Type
- A359
- Flights observed
- 256
- Distinct callsigns
- 20
- Country
- TR
- Last broadcast
- 4h ago
Last known position
Country allocation
The ICAO 24-bit address 4BB0EF 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 |
|---|---|---|---|
| THY39V | Turkish Airlines | 15 | 2026-06-22 |
| THY209 | - | 15 | 2026-07-13 |
| THY49A | - | 12 | 2026-06-21 |
| THY801 | Turkish Airlines | 8 | 2026-06-09 |
| THY69 | - | 8 | 2026-07-08 |
| THY45M | Turkish Airlines | 8 | 2026-06-26 |
| THY208 | - | 8 | 2026-07-12 |
| THY68 | - | 7 | 2026-07-07 |
| THY056 | - | 7 | 2026-06-12 |
| THY81D | Turkish Airlines | 6 | 2026-06-25 |
| THY175 | Turkish Airlines | 6 | 2026-05-27 |
| THY174 | Turkish Airlines | 6 | 2026-05-26 |
| THY904 | Turkish Airlines | 5 | 2026-05-18 |
| THY8NK | - | 5 | 2026-06-17 |
| THY7JV | - | 5 | 2026-06-17 |
| THY79K | Turkish Airlines | 5 | 2026-07-03 |
| THY48L | - | 5 | 2026-06-27 |
| THY3UN | Turkish Airlines | 5 | 2026-07-07 |
| THY3PQ | - | 5 | 2026-07-07 |
| THY216 | Turkish Airlines | 5 | 2026-07-06 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | THY75G | - | Jul 14, 16:30 UTC | Jul 14, 17:00 UTC | 30m |
| 2026-07-14 | THY75G | - | Jul 14, 10:05 UTC | Jul 14, 13:40 UTC | 3h 35m |
| 2026-07-13 | THY1MG | - | Jul 13, 23:10 UTC | Jul 14, 07:55 UTC | 8h 45m |
| 2026-07-13 | THY209 | - | Jul 13, 13:50 UTC | Jul 13, 14:20 UTC | 30m |
| 2026-07-13 | THY209 | - | Jul 13, 03:40 UTC | Jul 13, 13:15 UTC | 9h 35m |
| 2026-07-12 | THY208 | - | Jul 12, 15:10 UTC | Jul 12, 23:05 UTC | 7h 55m |
| 2026-07-12 | THY2CP | - | Jul 12, 08:45 UTC | Jul 12, 10:30 UTC | 1h 45m |
| 2026-07-12 | THY3QX | - | Jul 12, 04:50 UTC | Jul 12, 06:50 UTC | 2h 0m |
| 2026-07-11 | THY311 | - | Jul 11, 07:50 UTC | Jul 12, 02:20 UTC | 18h 30m |
| 2026-07-11 | THY311 | - | Jul 11, 05:50 UTC | Jul 12, 02:20 UTC | 20h 30m |
| 2026-07-11 | THY310 | - | Jul 11, 03:50 UTC | Jul 12, 02:20 UTC | 22h 30m |
| 2026-07-10 | THY310 | - | Jul 10, 23:50 UTC | Jul 11, 22:35 UTC | 22h 45m |
| 2026-07-10 | THY310 | - | Jul 10, 23:35 UTC | Jul 11, 20:25 UTC | 20h 50m |
| 2026-07-10 | THY1JZ | - | Jul 10, 19:10 UTC | Jul 10, 20:35 UTC | 1h 25m |
| 2026-07-10 | THY3FH | - | Jul 10, 16:05 UTC | Jul 10, 17:25 UTC | 1h 20m |
| 2026-07-10 | THY209 | - | Jul 10, 02:45 UTC | Jul 10, 13:20 UTC | 10h 35m |
| 2026-07-09 | THY208 | - | Jul 9, 14:40 UTC | Jul 9, 20:10 UTC | 5h 30m |
| 2026-07-09 | THY9FG | - | Jul 9, 09:00 UTC | Jul 9, 11:30 UTC | 2h 30m |
| 2026-07-09 | THY2WM | - | Jul 9, 04:20 UTC | Jul 9, 07:05 UTC | 2h 45m |
| 2026-07-08 | THY69 | - | Jul 8, 16:15 UTC | Jul 8, 20:05 UTC | 3h 50m |
| 2026-07-07 | THY68 | - | Jul 7, 23:20 UTC | Jul 8, 08:05 UTC | 8h 45m |
| 2026-07-07 | THY3PQ | - | Jul 7, 16:20 UTC | Jul 7, 19:20 UTC | 3h 0m |
| 2026-07-07 | THY3UN | IST → LHR | Jul 7, 10:50 UTC | Jul 7, 14:15 UTC | 3h 25m |
| 2026-07-06 | THY216 | GRU → IST | Jul 6, 20:15 UTC | Jul 7, 08:10 UTC | 11h 55m |
| 2026-07-06 | THY216 | GRU → IST | Jul 6, 15:35 UTC | Jul 6, 17:55 UTC | 2h 20m |
| 2026-07-06 | THY215 | GRU → SCL | Jul 6, 08:25 UTC | Jul 6, 12:10 UTC | 3h 45m |
| 2026-07-05 | THY215 | GRU → SCL | Jul 5, 17:35 UTC | Jul 6, 06:25 UTC | 12h 50m |
| 2026-07-05 | THY4YT | EWR → IST | Jul 5, 06:20 UTC | Jul 5, 15:00 UTC | 8h 40m |
| 2026-07-04 | THY29M | IST → EWR | Jul 4, 17:00 UTC | Jul 5, 04:00 UTC | 11h 0m |
| 2026-07-04 | THY9WC | - | Jul 4, 02:20 UTC | Jul 4, 14:30 UTC | 12h 10m |
| 2026-07-03 | THY79K | IST → SFO | Jul 3, 11:00 UTC | Jul 3, 23:35 UTC | 12h 35m |
| 2026-07-03 | THY69 | BKK → IST | Jul 3, 01:10 UTC | Jul 3, 01:30 UTC | 20m |
| 2026-07-02 | THY69 | BKK → IST | Jul 2, 16:25 UTC | Jul 3, 00:35 UTC | 8h 10m |
| 2026-07-01 | THY68 | - | Jul 1, 23:40 UTC | Jul 2, 08:20 UTC | 8h 40m |
| 2026-07-01 | THY1JZ | - | Jul 1, 19:30 UTC | Jul 1, 21:00 UTC | 1h 30m |
| 2026-07-01 | THY3FH | - | Jul 1, 16:40 UTC | Jul 1, 18:05 UTC | 1h 25m |
| 2026-07-01 | THY8JK | - | Jul 1, 02:35 UTC | Jul 1, 14:00 UTC | 11h 25m |
| 2026-06-30 | THY8DE | IST → SEA | Jun 30, 12:45 UTC | Jul 1, 00:00 UTC | 11h 15m |
| 2026-06-29 | THY81A | - | Jun 29, 20:00 UTC | Jun 30, 07:30 UTC | 11h 31m |
| 2026-06-29 | THY3DC | - | Jun 29, 05:45 UTC | Jun 29, 16:55 UTC | 11h 10m |
| 2026-06-27 | THY48L | - | Jun 27, 02:20 UTC | Jun 27, 07:34 UTC | 5h 15m |
| 2026-06-26 | THY45M | IST → KUL | Jun 26, 21:24 UTC | Jun 27, 00:14 UTC | 2h 50m |
| 2026-06-26 | THY45M | IST → KUL | Jun 26, 14:44 UTC | Jun 26, 21:20 UTC | 6h 35m |
| 2026-06-26 | THY1RT | - | Jun 26, 03:24 UTC | Jun 26, 12:00 UTC | 8h 35m |
| 2026-06-25 | THY81D | IST → BOS | Jun 25, 15:24 UTC | Jun 26, 01:05 UTC | 9h 40m |
| 2026-06-25 | THY3ES | - | Jun 25, 09:14 UTC | Jun 25, 11:39 UTC | 2h 25m |
| 2026-06-25 | THY9FP | - | Jun 25, 04:29 UTC | Jun 25, 06:35 UTC | 2h 5m |
| 2026-06-24 | THY92W | - | Jun 24, 16:14 UTC | Jun 24, 16:34 UTC | 20m |
| 2026-06-24 | THY92W | - | Jun 24, 10:10 UTC | Jun 24, 14:04 UTC | 3h 55m |
| 2026-06-23 | THY21Y | - | Jun 23, 22:55 UTC | Jun 24, 07:50 UTC | 8h 55m |
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-LGO page for operator, model, and routing details .