sensors Mode-S transponder
4BB106
ICAO 24-bit transponder address · allocated to Turkey
Currently assigned to TC-LHF · AIRBUS A-350-900
- Hex
- 4BB106
- Octal
- 22730406
- Decimal
- 4,960,518
- Country
- TR
- Tail
- TC-LHF
- Type
- A359
- Flights observed
- 246
- Distinct callsigns
- 20
- Country
- TR
- Last broadcast
- 3h ago
Current position
Country allocation
The ICAO 24-bit address 4BB106 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 |
|---|---|---|---|
| THY49A | Turkish Airlines | 16 | 2026-06-06 |
| THY39V | Turkish Airlines | 12 | 2026-06-08 |
| THY216 | - | 10 | 2026-07-08 |
| THY175 | Turkish Airlines | 10 | 2026-07-06 |
| THY056 | - | 10 | 2026-07-14 |
| THY174 | Turkish Airlines | 9 | 2026-07-05 |
| THY215 | Turkish Airlines | 8 | 2026-07-08 |
| THY057 | - | 8 | 2026-07-14 |
| THY165 | Turkish Airlines | 7 | 2026-06-24 |
| THY9WC | - | 6 | 2026-07-13 |
| THY79K | - | 6 | 2026-07-12 |
| THY73G | Turkish Airlines | 6 | 2026-04-16 |
| THY68 | - | 6 | 2026-06-26 |
| THY21Y | Turkish Airlines | 6 | 2026-05-04 |
| THY164 | - | 6 | 2026-07-11 |
| THY16 | Turkish Airlines | 6 | 2026-06-03 |
| THY15 | Turkish Airlines | 6 | 2026-06-02 |
| THY067 | Turkish Airlines | 6 | 2026-05-08 |
| THY92W | Turkish Airlines | 5 | 2026-05-04 |
| THY900 | Turkish Airlines | 5 | 2026-06-17 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | THY057 | - | Jul 14, 14:10 UTC | Jul 14, 15:15 UTC | 1h 5m |
| 2026-07-14 | THY056 | - | Jul 14, 09:55 UTC | Jul 14, 10:15 UTC | 20m |
| 2026-07-13 | THY056 | - | Jul 13, 23:10 UTC | Jul 14, 09:20 UTC | 10h 10m |
| 2026-07-13 | THY9WC | - | Jul 13, 02:55 UTC | Jul 13, 14:35 UTC | 11h 40m |
| 2026-07-12 | THY79K | - | Jul 12, 10:45 UTC | Jul 13, 00:05 UTC | 13h 20m |
| 2026-07-11 | THY164 | - | Jul 11, 04:01 UTC | Jul 11, 20:10 UTC | 16h 10m |
| 2026-07-10 | THY164 | - | Jul 10, 23:40 UTC | Jul 11, 20:10 UTC | 20h 30m |
| 2026-07-10 | THY2JV | - | Jul 10, 18:50 UTC | Jul 10, 19:40 UTC | 50m |
| 2026-07-10 | THY9QA | - | Jul 10, 16:25 UTC | Jul 10, 17:10 UTC | 45m |
| 2026-07-10 | THY5YR | - | Jul 10, 03:05 UTC | Jul 10, 13:55 UTC | 10h 50m |
| 2026-07-09 | THY83J | - | Jul 9, 12:10 UTC | Jul 10, 00:25 UTC | 12h 15m |
| 2026-07-08 | THY216 | - | Jul 8, 19:55 UTC | Jul 9, 07:55 UTC | 12h 0m |
| 2026-07-08 | THY216 | - | Jul 8, 15:10 UTC | Jul 8, 17:35 UTC | 2h 25m |
| 2026-07-08 | THY216 | - | Jul 8, 14:25 UTC | Jul 8, 14:35 UTC | 10m |
| 2026-07-08 | THY215 | GRU → SCL | Jul 8, 08:30 UTC | Jul 8, 11:15 UTC | 2h 45m |
| 2026-07-07 | THY215 | GRU → SCL | Jul 7, 17:45 UTC | Jul 8, 06:20 UTC | 12h 35m |
| 2026-07-07 | THY9WC | - | Jul 7, 02:30 UTC | Jul 7, 14:20 UTC | 11h 50m |
| 2026-07-06 | THY79K | IST → SFO | Jul 6, 10:55 UTC | Jul 7, 00:10 UTC | 13h 15m |
| 2026-07-06 | THY175 | SYD → KUL | Jul 6, 03:40 UTC | Jul 6, 07:55 UTC | 4h 15m |
| 2026-07-05 | THY175 | SYD → KUL | Jul 5, 21:50 UTC | Jul 6, 01:55 UTC | 4h 5m |
| 2026-07-05 | THY175 | SYD → KUL | Jul 5, 11:30 UTC | Jul 5, 19:20 UTC | 7h 50m |
| 2026-07-05 | THY174 | KUL → SYD | Jul 5, 01:30 UTC | Jul 5, 09:00 UTC | 7h 30m |
| 2026-07-04 | THY174 | KUL → SYD | Jul 4, 13:45 UTC | Jul 4, 23:15 UTC | 9h 30m |
| 2026-07-04 | THY3ES | - | Jul 4, 09:20 UTC | Jul 4, 11:25 UTC | 2h 5m |
| 2026-07-04 | THY9FP | - | Jul 4, 04:30 UTC | Jul 4, 06:50 UTC | 2h 20m |
| 2026-07-04 | THY057 | CGK → IST | Jul 4, 01:20 UTC | Jul 4, 01:45 UTC | 25m |
| 2026-07-03 | THY057 | CGK → IST | Jul 3, 14:10 UTC | Jul 4, 00:35 UTC | 10h 25m |
| 2026-07-03 | THY056 | - | Jul 3, 09:35 UTC | Jul 3, 09:50 UTC | 15m |
| 2026-07-03 | THY056 | - | Jul 3, 00:15 UTC | Jul 3, 09:05 UTC | 8h 50m |
| 2026-07-02 | THY056 | - | Jul 2, 23:00 UTC | Jul 2, 23:30 UTC | 30m |
| 2026-07-02 | THY8JK | - | Jul 2, 02:40 UTC | Jul 2, 13:40 UTC | 11h 0m |
| 2026-07-01 | THY8DE | IST → SEA | Jul 1, 12:35 UTC | Jul 1, 23:55 UTC | 11h 20m |
| 2026-06-30 | THY175 | SYD → KUL | Jun 30, 22:05 UTC | Jul 1, 08:30 UTC | 10h 25m |
| 2026-06-30 | THY175 | SYD → KUL | Jun 30, 11:35 UTC | Jun 30, 19:50 UTC | 8h 15m |
| 2026-06-30 | THY174 | KUL → SYD | Jun 30, 01:00 UTC | Jun 30, 08:35 UTC | 7h 36m |
| 2026-06-29 | THY174 | KUL → SYD | Jun 29, 13:14 UTC | Jun 29, 22:35 UTC | 9h 20m |
| 2026-06-28 | THY397 | - | Jun 28, 23:50 UTC | Jun 29, 10:10 UTC | 10h 20m |
| 2026-06-28 | THY396 | - | Jun 28, 11:50 UTC | Jun 28, 21:40 UTC | 9h 50m |
| 2026-06-27 | THY81A | - | Jun 27, 20:09 UTC | Jun 28, 07:40 UTC | 11h 30m |
| 2026-06-27 | THY3DC | - | Jun 27, 05:44 UTC | Jun 27, 17:39 UTC | 11h 55m |
| 2026-06-27 | THY69 | BKK → IST | Jun 27, 01:04 UTC | Jun 27, 01:24 UTC | 20m |
| 2026-06-26 | THY69 | BKK → IST | Jun 26, 16:09 UTC | Jun 27, 00:29 UTC | 8h 20m |
| 2026-06-26 | THY68 | - | Jun 26, 00:39 UTC | Jun 26, 07:55 UTC | 7h 15m |
| 2026-06-25 | THY68 | - | Jun 25, 23:24 UTC | Jun 25, 23:49 UTC | 25m |
| 2026-06-25 | THY8AK | - | Jun 25, 18:04 UTC | Jun 25, 18:59 UTC | 55m |
| 2026-06-25 | THY5HS | - | Jun 25, 15:24 UTC | Jun 25, 16:20 UTC | 55m |
| 2026-06-25 | THY209 | - | Jun 25, 02:45 UTC | Jun 25, 13:29 UTC | 10h 45m |
| 2026-06-24 | THY208 | IST → SIN | Jun 24, 14:34 UTC | Jun 25, 00:35 UTC | 10h 0m |
| 2026-06-24 | THY2JT | - | Jun 24, 09:34 UTC | Jun 24, 11:34 UTC | 2h 0m |
| 2026-06-24 | THY6AG | - | Jun 24, 05:05 UTC | Jun 24, 07:10 UTC | 2h 5m |
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-LHF page for operator, model, and routing details .