sensors Mode-S transponder
4BB108
ICAO 24-bit transponder address · allocated to Turkey
Currently assigned to TC-LHH · AIRBUS A-350-900
- Hex
- 4BB108
- Octal
- 22730410
- Decimal
- 4,960,520
- Country
- TR
- Tail
- TC-LHH
- Type
- A359
- Flights observed
- 257
- Distinct callsigns
- 20
- Country
- TR
- Last broadcast
- 2h ago
Last known position
Country allocation
The ICAO 24-bit address 4BB108 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 |
|---|---|---|---|
| THY067 | Turkish Airlines | 58 | 2026-07-07 |
| THY16 | - | 38 | 2026-07-12 |
| THY15 | - | 37 | 2026-07-11 |
| THY066 | - | 30 | 2026-07-13 |
| THY800 | - | 8 | 2026-07-08 |
| THY81K | - | 7 | 2026-06-26 |
| THY801 | Turkish Airlines | 7 | 2026-07-03 |
| THY38H | - | 7 | 2026-06-25 |
| THY8JK | Turkish Airlines | 5 | 2026-04-13 |
| THY165 | Turkish Airlines | 5 | 2026-06-28 |
| THY164 | - | 5 | 2026-06-28 |
| THY71M | - | 4 | 2026-07-10 |
| THY48L | Turkish Airlines | 4 | 2026-04-28 |
| THY45M | Turkish Airlines | 4 | 2026-04-27 |
| THY209 | Turkish Airlines | 4 | 2026-06-01 |
| THY208 | Turkish Airlines | 3 | 2026-05-31 |
| THY6VM | Turkish Airlines | 2 | 2026-04-18 |
| THY3ES | Turkish Airlines | 2 | 2026-05-31 |
| THY12V | - | 2 | 2026-07-10 |
| THY9WR | - | 1 | 2026-06-16 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | THY066 | - | Jul 13, 02:55 UTC | Jul 14, 01:20 UTC | 22h 25m |
| 2026-07-13 | THY066 | - | Jul 13, 00:15 UTC | Jul 14, 00:00 UTC | 23h 45m |
| 2026-07-12 | THY066 | - | Jul 12, 22:55 UTC | Jul 12, 23:20 UTC | 25m |
| 2026-07-12 | THY16 | - | Jul 12, 07:35 UTC | Jul 12, 19:40 UTC | 12h 5m |
| 2026-07-12 | THY16 | - | Jul 12, 03:25 UTC | Jul 12, 05:30 UTC | 2h 5m |
| 2026-07-11 | THY15 | - | Jul 11, 23:00 UTC | Jul 12, 01:35 UTC | 2h 35m |
| 2026-07-11 | THY15 | - | Jul 11, 07:50 UTC | Jul 11, 20:45 UTC | 12h 55m |
| 2026-07-10 | THY12V | - | Jul 10, 23:20 UTC | Jul 11, 01:05 UTC | 1h 45m |
| 2026-07-10 | THY71M | - | Jul 10, 00:05 UTC | Jul 11, 00:00 UTC | 23h 55m |
| 2026-07-09 | THY71M | - | Jul 9, 23:55 UTC | Jul 10, 01:40 UTC | 1h 45m |
| 2026-07-09 | THY3AX | - | Jul 9, 19:25 UTC | Jul 9, 20:20 UTC | 55m |
| 2026-07-09 | THY2XQ | - | Jul 9, 16:25 UTC | Jul 9, 17:25 UTC | 1h 0m |
| 2026-07-08 | THY800 | - | Jul 8, 22:15 UTC | Jul 9, 13:45 UTC | 15h 30m |
| 2026-07-08 | THY800 | - | Jul 8, 07:05 UTC | Jul 8, 17:45 UTC | 10h 40m |
| 2026-07-07 | THY067 | CGK → IST | Jul 7, 06:05 UTC | Jul 8, 01:30 UTC | 19h 25m |
| 2026-07-07 | THY067 | CGK → IST | Jul 7, 04:20 UTC | Jul 8, 01:30 UTC | 21h 10m |
| 2026-07-07 | THY066 | - | Jul 7, 02:40 UTC | Jul 8, 01:30 UTC | 22h 50m |
| 2026-07-07 | THY066 | - | Jul 7, 00:05 UTC | Jul 8, 00:00 UTC | 23h 55m |
| 2026-07-06 | THY066 | - | Jul 6, 22:35 UTC | Jul 7, 21:40 UTC | 23h 5m |
| 2026-07-06 | THY2JV | - | Jul 6, 18:50 UTC | Jul 6, 19:50 UTC | 1h 0m |
| 2026-07-06 | THY9QA | BLQ → IST | Jul 6, 16:30 UTC | Jul 6, 17:20 UTC | 50m |
| 2026-07-05 | THY800 | - | Jul 5, 18:05 UTC | Jul 6, 13:55 UTC | 19h 50m |
| 2026-07-05 | THY800 | - | Jul 5, 17:55 UTC | Jul 6, 13:55 UTC | 20h 0m |
| 2026-07-05 | THY800 | - | Jul 5, 08:05 UTC | Jul 6, 03:40 UTC | 19h 35m |
| 2026-07-05 | THY800 | - | Jul 5, 07:50 UTC | Jul 6, 03:40 UTC | 19h 50m |
| 2026-07-04 | THY067 | CGK → IST | Jul 4, 06:05 UTC | Jul 5, 01:20 UTC | 19h 15m |
| 2026-07-04 | THY067 | CGK → IST | Jul 4, 04:20 UTC | Jul 5, 01:20 UTC | 21h 0m |
| 2026-07-04 | THY067 | CGK → IST | Jul 4, 02:45 UTC | Jul 5, 01:20 UTC | 22h 35m |
| 2026-07-04 | THY067 | CGK → IST | Jul 4, 00:05 UTC | Jul 5, 00:00 UTC | 23h 55m |
| 2026-07-03 | THY066 | - | Jul 3, 22:45 UTC | Jul 4, 19:55 UTC | 21h 10m |
| 2026-07-03 | THY1JZ | - | Jul 3, 19:15 UTC | Jul 3, 20:45 UTC | 1h 30m |
| 2026-07-03 | THY3FH | - | Jul 3, 16:25 UTC | Jul 3, 17:35 UTC | 1h 10m |
| 2026-07-03 | THY801 | OSM → IST | Jul 3, 02:40 UTC | Jul 3, 13:40 UTC | 11h 0m |
| 2026-07-02 | THY801 | OSM → IST | Jul 2, 10:05 UTC | Jul 3, 10:00 UTC | 23h 55m |
| 2026-07-02 | THY801 | OSM → IST | Jul 2, 08:05 UTC | Jul 3, 03:55 UTC | 19h 50m |
| 2026-07-02 | THY801 | OSM → IST | Jul 2, 07:05 UTC | Jul 3, 03:55 UTC | 20h 50m |
| 2026-07-01 | THY067 | CGK → IST | Jul 1, 06:05 UTC | Jul 2, 01:30 UTC | 19h 25m |
| 2026-07-01 | THY067 | CGK → IST | Jul 1, 04:05 UTC | Jul 2, 01:30 UTC | 21h 25m |
| 2026-07-01 | THY067 | CGK → IST | Jul 1, 02:50 UTC | Jul 2, 01:30 UTC | 22h 40m |
| 2026-07-01 | THY066 | - | Jul 1, 00:05 UTC | Jul 2, 00:00 UTC | 23h 55m |
| 2026-06-30 | THY066 | - | Jun 30, 22:50 UTC | Jul 1, 20:20 UTC | 21h 30m |
| 2026-06-30 | THY801 | OSM → IST | Jun 30, 02:35 UTC | Jun 30, 13:50 UTC | 11h 15m |
| 2026-06-29 | THY801 | OSM → IST | Jun 29, 08:04 UTC | Jun 30, 03:45 UTC | 19h 41m |
| 2026-06-29 | THY801 | OSM → IST | Jun 29, 06:59 UTC | Jun 30, 03:45 UTC | 20h 46m |
| 2026-06-28 | THY165 | HAN → IST | Jun 28, 16:39 UTC | Jun 29, 02:09 UTC | 9h 30m |
| 2026-06-28 | THY164 | - | Jun 28, 08:14 UTC | Jun 28, 08:29 UTC | 15m |
| 2026-06-27 | THY164 | - | Jun 27, 23:45 UTC | Jun 28, 07:40 UTC | 7h 55m |
| 2026-06-27 | THY16 | GRU → IST | Jun 27, 07:30 UTC | Jun 27, 19:29 UTC | 12h 0m |
| 2026-06-27 | THY16 | GRU → IST | Jun 27, 02:55 UTC | Jun 27, 05:04 UTC | 2h 10m |
| 2026-06-26 | THY15 | IST → GRU | Jun 26, 22:44 UTC | Jun 27, 01:09 UTC | 2h 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-LHH page for operator, model, and routing details .