sensors Mode-S transponder
4BB0E3
ICAO 24-bit transponder address · allocated to Turkey
Currently assigned to TC-LGC · AIRBUS A-350-900
- Hex
- 4BB0E3
- Octal
- 22730343
- Decimal
- 4,960,483
- Country
- TR
- Tail
- TC-LGC
- Type
- A359
- Flights observed
- 255
- Distinct callsigns
- 20
- Country
- TR
- Last broadcast
- Jul 26, 20:15 UTC
Current position
Country allocation
The ICAO 24-bit address 4BB0E3 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 |
|---|---|---|---|
| THY75G | Turkish Airlines | 11 | 2026-06-09 |
| THY216 | - | 11 | 2026-07-14 |
| THY900 | Turkish Airlines | 8 | 2026-04-15 |
| THY215 | - | 8 | 2026-07-14 |
| THY175 | Turkish Airlines | 8 | 2026-07-03 |
| THY174 | Turkish Airlines | 8 | 2026-07-03 |
| THY79K | Turkish Airlines | 7 | 2026-07-25 |
| THY39V | - | 7 | 2026-07-09 |
| THY209 | - | 7 | 2026-06-30 |
| THY208 | Turkish Airlines | 7 | 2026-06-29 |
| THY1MG | Turkish Airlines | 7 | 2026-06-08 |
| THY9WC | Turkish Airlines | 6 | 2026-07-26 |
| THY92W | - | 6 | 2026-07-01 |
| THY16 | - | 6 | 2026-07-11 |
| THY15 | - | 6 | 2026-07-10 |
| THY10J | - | 6 | 2026-07-16 |
| THY067 | Turkish Airlines | 6 | 2026-07-23 |
| THY9FP | Turkish Airlines | 5 | 2026-07-24 |
| THY801 | Turkish Airlines | 5 | 2026-05-28 |
| THY49A | - | 5 | 2026-07-08 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | THY2JV | - | Jul 26, 19:05 UTC | Jul 26, 20:15 UTC | 1h 10m |
| 2026-07-26 | THY9QA | BLQ → IST | Jul 26, 16:35 UTC | Jul 26, 17:30 UTC | 55m |
| 2026-07-26 | THY9WC | SFO → IST | Jul 26, 02:15 UTC | Jul 26, 13:35 UTC | 11h 21m |
| 2026-07-25 | THY79K | IST → SFO | Jul 25, 10:40 UTC | Jul 25, 23:25 UTC | 12h 45m |
| 2026-07-24 | THY3ES | IST → ADB | Jul 24, 09:15 UTC | Jul 24, 11:35 UTC | 2h 20m |
| 2026-07-24 | THY9FP | IST → PRG | Jul 24, 04:45 UTC | Jul 24, 07:05 UTC | 2h 20m |
| 2026-07-23 | THY067 | CGK → IST | Jul 23, 06:50 UTC | Jul 24, 01:40 UTC | 18h 50m |
| 2026-07-23 | THY067 | CGK → IST | Jul 23, 04:50 UTC | Jul 24, 01:40 UTC | 20h 50m |
| 2026-07-23 | THY067 | CGK → IST | Jul 23, 03:25 UTC | Jul 24, 01:40 UTC | 22h 15m |
| 2026-07-22 | THY066 | IST → DPS | Jul 22, 22:55 UTC | Jul 23, 20:30 UTC | 21h 35m |
| 2026-07-22 | THY9WC | SFO → IST | Jul 22, 03:00 UTC | Jul 22, 15:00 UTC | 12h 0m |
| 2026-07-21 | THY79K | - | Jul 21, 11:05 UTC | Jul 22, 00:20 UTC | 13h 15m |
| 2026-07-20 | THY169 | SIN → IST | Jul 20, 21:55 UTC | Jul 21, 08:20 UTC | 10h 25m |
| 2026-07-20 | THY169 | SIN → IST | Jul 20, 12:05 UTC | Jul 20, 13:15 UTC | 1h 10m |
| 2026-07-20 | THY168 | SIN → MEL | Jul 20, 03:25 UTC | Jul 20, 10:00 UTC | 6h 35m |
| 2026-07-19 | THY168 | SIN → MEL | Jul 19, 15:15 UTC | Jul 20, 01:25 UTC | 10h 10m |
| 2026-07-19 | THY48L | KUL → IST | Jul 19, 05:15 UTC | Jul 19, 12:20 UTC | 7h 5m |
| 2026-07-19 | THY48L | KUL → IST | Jul 19, 02:10 UTC | Jul 19, 02:30 UTC | 20m |
| 2026-07-18 | THY45M | - | Jul 18, 23:30 UTC | Jul 18, 23:50 UTC | 20m |
| 2026-07-18 | THY45M | - | Jul 18, 14:20 UTC | Jul 18, 22:25 UTC | 8h 5m |
| 2026-07-18 | THY3ES | - | Jul 18, 09:10 UTC | Jul 18, 11:20 UTC | 2h 10m |
| 2026-07-18 | THY9FP | - | Jul 18, 04:20 UTC | Jul 18, 06:40 UTC | 2h 20m |
| 2026-07-17 | THY45T | - | Jul 17, 14:39 UTC | Jul 18, 00:45 UTC | 10h 5m |
| 2026-07-16 | THY10J | - | Jul 16, 23:20 UTC | Jul 17, 09:45 UTC | 10h 25m |
| 2026-07-16 | THY8JK | - | Jul 16, 02:40 UTC | Jul 16, 13:34 UTC | 10h 55m |
| 2026-07-15 | THY8DE | - | Jul 15, 12:30 UTC | Jul 16, 00:00 UTC | 11h 30m |
| 2026-07-14 | THY216 | - | Jul 14, 20:00 UTC | Jul 15, 08:10 UTC | 12h 9m |
| 2026-07-14 | THY216 | - | Jul 14, 14:35 UTC | Jul 14, 17:40 UTC | 3h 5m |
| 2026-07-14 | THY215 | - | Jul 14, 08:25 UTC | Jul 14, 11:20 UTC | 2h 55m |
| 2026-07-13 | THY215 | - | Jul 13, 17:40 UTC | Jul 14, 06:10 UTC | 12h 30m |
| 2026-07-13 | THY6JS | - | Jul 13, 10:30 UTC | Jul 13, 13:40 UTC | 3h 10m |
| 2026-07-13 | THY8GY | - | Jul 13, 04:20 UTC | Jul 13, 08:15 UTC | 3h 55m |
| 2026-07-12 | THY12V | - | Jul 12, 23:10 UTC | Jul 13, 01:01 UTC | 1h 50m |
| 2026-07-12 | THY12V | - | Jul 12, 00:50 UTC | Jul 13, 00:45 UTC | 23h 55m |
| 2026-07-11 | THY71M | - | Jul 11, 23:35 UTC | Jul 12, 01:15 UTC | 1h 40m |
| 2026-07-11 | THY16 | - | Jul 11, 08:01 UTC | Jul 11, 19:30 UTC | 11h 30m |
| 2026-07-11 | THY16 | - | Jul 11, 03:20 UTC | Jul 11, 05:15 UTC | 1h 55m |
| 2026-07-10 | THY15 | - | Jul 10, 22:55 UTC | Jul 11, 01:35 UTC | 2h 40m |
| 2026-07-10 | THY15 | - | Jul 10, 07:50 UTC | Jul 10, 20:40 UTC | 12h 50m |
| 2026-07-09 | THY39V | - | Jul 9, 15:50 UTC | Jul 10, 01:55 UTC | 10h 5m |
| 2026-07-08 | THY49A | - | Jul 8, 23:05 UTC | Jul 9, 08:50 UTC | 9h 45m |
| 2026-07-08 | THY1JZ | - | Jul 8, 19:35 UTC | Jul 8, 21:00 UTC | 1h 25m |
| 2026-07-08 | THY3FH | - | Jul 8, 16:35 UTC | Jul 8, 17:45 UTC | 1h 10m |
| 2026-07-08 | THY8JK | - | Jul 8, 02:35 UTC | Jul 8, 13:10 UTC | 10h 35m |
| 2026-07-07 | THY8DE | IST → SEA | Jul 7, 12:20 UTC | Jul 8, 00:10 UTC | 11h 50m |
| 2026-07-07 | THY2YR | - | Jul 7, 07:20 UTC | Jul 7, 08:50 UTC | 1h 30m |
| 2026-07-07 | THY39GV | - | Jul 7, 04:15 UTC | Jul 7, 05:25 UTC | 1h 10m |
| 2026-07-06 | THY12V | - | Jul 6, 23:15 UTC | Jul 7, 00:55 UTC | 1h 40m |
| 2026-07-06 | THY12V | - | Jul 6, 00:50 UTC | Jul 7, 00:45 UTC | 23h 55m |
| 2026-07-05 | THY71M | - | Jul 5, 23:40 UTC | Jul 6, 01:25 UTC | 1h 45m |
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-LGC page for operator, model, and routing details .