sensors Mode-S transponder
4BB0EB
ICAO 24-bit transponder address · allocated to Turkey
Currently assigned to TC-LGK · AIRBUS A-350-900
- Hex
- 4BB0EB
- Octal
- 22730353
- Decimal
- 4,960,491
- Country
- TR
- Tail
- TC-LGK
- Type
- A359
- Flights observed
- 262
- Distinct callsigns
- 20
- Country
- TR
- Last broadcast
- 1h ago
Last known position
Country allocation
The ICAO 24-bit address 4BB0EB 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 |
|---|---|---|---|
| THY163 | - | 52 | 2026-07-09 |
| THY162 | - | 26 | 2026-07-08 |
| THY4YT | Turkish Airlines | 19 | 2026-07-04 |
| THY29M | Turkish Airlines | 16 | 2026-07-03 |
| THY165 | Turkish Airlines | 14 | 2026-06-25 |
| THY48L | - | 13 | 2026-07-03 |
| THY45M | Turkish Airlines | 12 | 2026-07-02 |
| THY164 | - | 8 | 2026-06-25 |
| THY81D | Turkish Airlines | 7 | 2026-07-01 |
| THY1RT | - | 7 | 2026-07-02 |
| THY95Y | - | 5 | 2026-07-11 |
| THY8EL | - | 5 | 2026-07-12 |
| THY9FP | Turkish Airlines | 4 | 2026-05-28 |
| THY9WR | - | 3 | 2026-06-15 |
| THY7XE | Turkish Airlines | 3 | 2026-06-03 |
| THY5QF | Turkish Airlines | 3 | 2026-06-03 |
| THY3ES | Turkish Airlines | 3 | 2026-05-28 |
| THY1PA | Turkish Airlines | 3 | 2026-06-15 |
| THY12V | - | 3 | 2026-07-13 |
| THY9ZP | - | 2 | 2026-07-04 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | THY3JL | - | Jul 14, 05:40 UTC | Jul 14, 08:45 UTC | 3h 5m |
| 2026-07-13 | THY12V | - | Jul 13, 23:15 UTC | Jul 14, 01:15 UTC | 2h 0m |
| 2026-07-13 | THY12V | - | Jul 13, 00:50 UTC | Jul 14, 00:45 UTC | 23h 55m |
| 2026-07-12 | THY71M | - | Jul 12, 23:40 UTC | Jul 13, 01:30 UTC | 1h 50m |
| 2026-07-12 | THY8EL | - | Jul 12, 02:55 UTC | Jul 12, 14:01 UTC | 11h 5m |
| 2026-07-11 | THY95Y | - | Jul 11, 12:15 UTC | Jul 12, 00:01 UTC | 11h 45m |
| 2026-07-10 | THY4MS | - | Jul 10, 20:40 UTC | Jul 11, 08:25 UTC | 11h 45m |
| 2026-07-10 | THY73G | - | Jul 10, 05:00 UTC | Jul 10, 18:05 UTC | 13h 5m |
| 2026-07-09 | THY163 | - | Jul 9, 06:50 UTC | Jul 10, 01:15 UTC | 18h 25m |
| 2026-07-09 | THY163 | - | Jul 9, 05:20 UTC | Jul 10, 01:15 UTC | 19h 55m |
| 2026-07-09 | THY163 | - | Jul 9, 03:50 UTC | Jul 10, 01:15 UTC | 21h 25m |
| 2026-07-09 | THY163 | - | Jul 9, 00:50 UTC | Jul 10, 00:45 UTC | 23h 55m |
| 2026-07-08 | THY162 | - | Jul 8, 23:15 UTC | Jul 9, 20:10 UTC | 20h 55m |
| 2026-07-08 | THY8EL | - | Jul 8, 03:05 UTC | Jul 8, 13:40 UTC | 10h 35m |
| 2026-07-07 | THY95Y | IST → DUS | Jul 7, 12:15 UTC | Jul 8, 00:30 UTC | 12h 15m |
| 2026-07-06 | THY81A | - | Jul 6, 20:00 UTC | Jul 7, 06:45 UTC | 10h 45m |
| 2026-07-06 | THY3DC | - | Jul 6, 05:30 UTC | Jul 6, 17:30 UTC | 12h 0m |
| 2026-07-05 | THY163 | SGN → IST | Jul 5, 06:50 UTC | Jul 6, 01:30 UTC | 18h 40m |
| 2026-07-05 | THY163 | SGN → IST | Jul 5, 05:05 UTC | Jul 6, 01:30 UTC | 20h 25m |
| 2026-07-05 | THY163 | SGN → IST | Jul 5, 03:25 UTC | Jul 6, 01:30 UTC | 22h 5m |
| 2026-07-05 | THY163 | SGN → IST | Jul 5, 00:50 UTC | Jul 6, 00:45 UTC | 23h 55m |
| 2026-07-04 | THY162 | - | Jul 4, 23:15 UTC | Jul 5, 20:10 UTC | 20h 55m |
| 2026-07-04 | THY9ZP | - | Jul 4, 19:20 UTC | Jul 4, 20:00 UTC | 40m |
| 2026-07-04 | THY7UW | IST → BSL | Jul 4, 16:50 UTC | Jul 4, 17:25 UTC | 35m |
| 2026-07-04 | THY4YT | EWR → IST | Jul 4, 06:20 UTC | Jul 4, 13:50 UTC | 7h 30m |
| 2026-07-04 | THY4YT | EWR → IST | Jul 4, 05:05 UTC | Jul 4, 06:15 UTC | 1h 10m |
| 2026-07-03 | THY29M | IST → EWR | Jul 3, 16:20 UTC | Jul 4, 02:35 UTC | 10h 15m |
| 2026-07-03 | THY48L | - | Jul 3, 02:40 UTC | Jul 3, 13:00 UTC | 10h 20m |
| 2026-07-02 | THY45M | IST → KUL | Jul 2, 14:30 UTC | Jul 3, 00:05 UTC | 9h 35m |
| 2026-07-02 | THY1RT | - | Jul 2, 02:55 UTC | Jul 2, 11:30 UTC | 8h 35m |
| 2026-07-01 | THY81D | IST → BOS | Jul 1, 15:05 UTC | Jul 2, 00:30 UTC | 9h 25m |
| 2026-07-01 | THY48L | - | Jul 1, 02:25 UTC | Jul 1, 12:35 UTC | 10h 10m |
| 2026-06-30 | THY45M | IST → KUL | Jun 30, 14:20 UTC | Jun 30, 23:55 UTC | 9h 35m |
| 2026-06-30 | THY1KD | - | Jun 30, 09:15 UTC | Jun 30, 11:05 UTC | 1h 50m |
| 2026-06-30 | THY7KF | - | Jun 30, 05:20 UTC | Jun 30, 06:55 UTC | 1h 35m |
| 2026-06-29 | THY163 | SGN → IST | Jun 29, 06:50 UTC | Jun 30, 01:09 UTC | 18h 20m |
| 2026-06-29 | THY163 | SGN → IST | Jun 29, 04:50 UTC | Jun 30, 01:09 UTC | 20h 20m |
| 2026-06-29 | THY163 | SGN → IST | Jun 29, 03:14 UTC | Jun 30, 01:09 UTC | 21h 55m |
| 2026-06-29 | THY163 | SGN → IST | Jun 29, 00:49 UTC | Jun 30, 00:45 UTC | 23h 55m |
| 2026-06-28 | THY162 | - | Jun 28, 23:14 UTC | Jun 29, 20:00 UTC | 20h 45m |
| 2026-06-28 | THY2NA | - | Jun 28, 18:14 UTC | Jun 28, 20:14 UTC | 2h 0m |
| 2026-06-28 | THY3GK | IST → FCO | Jun 28, 14:19 UTC | Jun 28, 16:14 UTC | 1h 55m |
| 2026-06-28 | THY1RT | - | Jun 28, 02:10 UTC | Jun 28, 10:35 UTC | 8h 25m |
| 2026-06-27 | THY81D | IST → BOS | Jun 27, 14:09 UTC | Jun 27, 23:19 UTC | 9h 10m |
| 2026-06-27 | THY1RT | - | Jun 27, 02:29 UTC | Jun 27, 11:00 UTC | 8h 30m |
| 2026-06-26 | THY81D | IST → BOS | Jun 26, 14:05 UTC | Jun 26, 23:25 UTC | 9h 20m |
| 2026-06-25 | THY165 | HAN → IST | Jun 25, 17:30 UTC | Jun 26, 02:09 UTC | 8h 40m |
| 2026-06-25 | THY165 | HAN → IST | Jun 25, 16:45 UTC | Jun 25, 16:59 UTC | 15m |
| 2026-06-25 | THY164 | - | Jun 25, 08:40 UTC | Jun 25, 08:55 UTC | 15m |
| 2026-06-25 | THY164 | - | Jun 25, 00:14 UTC | Jun 25, 07:59 UTC | 7h 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-LGK page for operator, model, and routing details .