sensors Mode-S transponder
4BB164
ICAO 24-bit transponder address · allocated to Turkey
Currently assigned to TC-LKD · BOEING 777-300ER
- Hex
- 4BB164
- Octal
- 22730544
- Decimal
- 4,960,612
- Country
- TR
- Tail
- TC-LKD
- Type
- B77W
- Flights observed
- 81
- Distinct callsigns
- 20
- Country
- TR
- Last broadcast
- Jun 11, 16:20 UTC
Last known position
Country allocation
The ICAO 24-bit address 4BB164 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 |
|---|---|---|---|
| THY8AK | - | 3 | 2026-06-06 |
| THY6DT | Turkish Airlines | 3 | 2026-05-30 |
| THY5HS | Turkish Airlines | 3 | 2026-06-11 |
| THY5032 | - | 3 | 2026-04-13 |
| THY5016 | Turkish Airlines | 3 | 2026-04-18 |
| THY1QU | Turkish Airlines | 3 | 2026-05-30 |
| THY9DX | Turkish Airlines | 2 | 2026-05-24 |
| THY5377 | - | 2 | 2026-05-17 |
| THY5253 | Turkish Airlines | 2 | 2026-06-01 |
| THY5087 | Turkish Airlines | 2 | 2026-04-17 |
| THY5047 | Turkish Airlines | 2 | 2026-04-17 |
| THY5046 | Turkish Airlines | 2 | 2026-04-17 |
| THY5009 | Turkish Airlines | 2 | 2026-04-16 |
| THY5008 | Turkish Airlines | 2 | 2026-04-16 |
| THY5005 | - | 2 | 2026-04-14 |
| THY5000 | Turkish Airlines | 2 | 2026-04-16 |
| THY8XS | Turkish Airlines | 1 | 2026-05-06 |
| THY8HX | Turkish Airlines | 1 | 2026-05-06 |
| THY80E | Turkish Airlines | 1 | 2026-05-27 |
| THY7NQ | Turkish Airlines | 1 | 2026-06-09 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-11 | THY5HS | BRU → ISL | Jun 11, 15:25 UTC | Jun 11, 16:20 UTC | 55m |
| 2026-06-09 | THY7NQ | ESB → IST | Jun 9, 19:45 UTC | Jun 10, 14:55 UTC | 19h 10m |
| 2026-06-09 | THY5294 | - | Jun 9, 12:20 UTC | Jun 9, 19:50 UTC | 7h 30m |
| 2026-06-08 | THY5266 | - | Jun 8, 04:40 UTC | Jun 8, 12:35 UTC | 7h 55m |
| 2026-06-06 | THY8AK | - | Jun 6, 18:04 UTC | Jun 6, 18:55 UTC | 50m |
| 2026-06-05 | THY5349 | JED → IST | Jun 5, 08:05 UTC | Jun 5, 16:15 UTC | 8h 10m |
| 2026-06-04 | THY5324 | JED → IST | Jun 4, 16:25 UTC | Jun 5, 03:20 UTC | 10h 55m |
| 2026-06-04 | THY5271 | JED → ESB | Jun 4, 06:00 UTC | Jun 4, 13:50 UTC | 7h 50m |
| 2026-06-03 | THY5311 | MED → IST | Jun 3, 14:55 UTC | Jun 3, 22:35 UTC | 7h 40m |
| 2026-06-03 | THY5309 | JED → IST | Jun 3, 03:55 UTC | Jun 3, 12:10 UTC | 8h 15m |
| 2026-06-01 | THY5253 | JED → IST | Jun 1, 11:15 UTC | Jun 1, 20:00 UTC | 8h 45m |
| 2026-05-31 | THY5251 | JED → IST | May 31, 21:15 UTC | Jun 1, 05:40 UTC | 8h 25m |
| 2026-05-31 | THY4955 | ADA → IST | May 31, 15:25 UTC | May 31, 16:10 UTC | 45m |
| 2026-05-31 | THY4954 | IST → AYT | May 31, 12:45 UTC | May 31, 13:20 UTC | 35m |
| 2026-05-31 | THY4951 | GZT → IST | May 31, 08:45 UTC | May 31, 09:25 UTC | 40m |
| 2026-05-30 | THY1QU | IST → BHX | May 30, 11:45 UTC | May 30, 12:45 UTC | 1h 0m |
| 2026-05-30 | THY6DT | IST → AYT | May 30, 08:50 UTC | May 30, 09:30 UTC | 40m |
| 2026-05-28 | THY2NP | AYT → VKO | May 28, 07:55 UTC | May 28, 08:40 UTC | 45m |
| 2026-05-28 | THY3YH | IST → BOD | May 28, 05:20 UTC | May 28, 06:05 UTC | 45m |
| 2026-05-27 | THY4YH | ADB → IST | May 27, 19:00 UTC | May 27, 19:45 UTC | 45m |
| 2026-05-27 | THY80E | IST → ADB | May 27, 16:40 UTC | May 27, 17:05 UTC | 25m |
| 2026-05-27 | THY6VH | AYT → IST | May 27, 12:40 UTC | May 27, 13:35 UTC | 55m |
| 2026-05-24 | THY3JW | AYT → IST | May 24, 14:40 UTC | May 24, 15:35 UTC | 55m |
| 2026-05-24 | THY9DX | IST → EAP | May 24, 12:10 UTC | May 24, 12:45 UTC | 35m |
| 2026-05-24 | THY9DX | IST → EAP | May 24, 11:50 UTC | May 24, 12:05 UTC | 15m |
| 2026-05-21 | THY5291 | - | May 21, 06:10 UTC | May 21, 13:50 UTC | 7h 40m |
| 2026-05-20 | THY5279 | - | May 20, 11:25 UTC | May 20, 13:00 UTC | 1h 35m |
| 2026-05-18 | THY5277 | - | May 18, 19:15 UTC | May 19, 02:30 UTC | 7h 15m |
| 2026-05-18 | THY5261 | - | May 18, 07:35 UTC | May 18, 15:05 UTC | 7h 30m |
| 2026-05-17 | THY5377 | - | May 17, 16:25 UTC | May 18, 00:35 UTC | 8h 10m |
| 2026-05-16 | THY5399 | - | May 16, 17:01 UTC | May 17, 00:20 UTC | 7h 20m |
| 2026-05-15 | THY8AK | - | May 15, 18:10 UTC | May 15, 18:20 UTC | 10m |
| 2026-05-15 | THY5HS | BRU → ISL | May 15, 15:45 UTC | May 15, 16:20 UTC | 35m |
| 2026-05-15 | THY2VS | IST → ESB | May 15, 10:30 UTC | May 15, 10:50 UTC | 20m |
| 2026-05-15 | THY3RB | IST → AYT | May 15, 07:50 UTC | May 15, 08:35 UTC | 45m |
| 2026-05-14 | THY5362 | GNY → MED | May 14, 01:55 UTC | May 14, 09:20 UTC | 7h 25m |
| 2026-05-13 | THY5383 | - | May 13, 06:05 UTC | May 13, 13:15 UTC | 7h 10m |
| 2026-05-11 | THY5377 | - | May 11, 16:10 UTC | May 12, 09:40 UTC | 17h 31m |
| 2026-05-09 | THY5289 | - | May 9, 20:49 UTC | May 10, 04:04 UTC | 7h 15m |
| 2026-05-06 | THY8XS | IST → CDG | May 6, 08:40 UTC | May 6, 08:55 UTC | 15m |
| 2026-05-06 | THY8HX | ESB → IST | May 6, 05:50 UTC | May 6, 06:35 UTC | 45m |
| 2026-05-04 | THY8AK | - | May 4, 18:00 UTC | May 4, 18:40 UTC | 41m |
| 2026-05-04 | THY5HS | BRU → ISL | May 4, 15:15 UTC | May 4, 16:00 UTC | 45m |
| 2026-05-03 | THY1QU | IST → BHX | May 3, 11:35 UTC | May 3, 12:20 UTC | 45m |
| 2026-05-03 | THY6DT | IST → AYT | May 3, 08:45 UTC | May 3, 09:25 UTC | 40m |
| 2026-04-30 | THY5253 | - | Apr 30, 18:20 UTC | May 1, 01:15 UTC | 6h 55m |
| 2026-04-30 | THY5397 | - | Apr 30, 07:45 UTC | Apr 30, 14:55 UTC | 7h 10m |
| 2026-04-26 | THY5355 | - | Apr 26, 17:25 UTC | Apr 27, 00:05 UTC | 6h 40m |
| 2026-04-26 | THY5454 | - | Apr 26, 14:30 UTC | Apr 26, 14:55 UTC | 25m |
| 2026-04-25 | THY2ZT | - | Apr 25, 14:10 UTC | Apr 25, 14:20 UTC | 10m |
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-LKD page for operator, model, and routing details .