sensors Mode-S transponder
4BB0E4
ICAO 24-bit transponder address · allocated to Turkey
Currently assigned to TC-LGD · AIRBUS A-350-900
- Hex
- 4BB0E4
- Octal
- 22730344
- Decimal
- 4,960,484
- Country
- TR
- Tail
- TC-LGD
- Type
- A359
- Flights observed
- 229
- Distinct callsigns
- 20
- Country
- TR
- Last broadcast
- 4h ago
Last known position
Country allocation
The ICAO 24-bit address 4BB0E4 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 |
|---|---|---|---|
| THY800 | Turkish Airlines | 10 | 2026-06-07 |
| THY175 | Turkish Airlines | 10 | 2026-07-08 |
| THY174 | Turkish Airlines | 10 | 2026-07-08 |
| THY165 | Turkish Airlines | 9 | 2026-07-03 |
| THY59 | Turkish Airlines | 8 | 2026-05-26 |
| THY057 | Turkish Airlines | 8 | 2026-06-26 |
| THY95Y | Turkish Airlines | 7 | 2026-04-23 |
| THY58 | Turkish Airlines | 7 | 2026-05-25 |
| THY209 | - | 7 | 2026-07-02 |
| THY056 | - | 7 | 2026-06-26 |
| THY8EL | Turkish Airlines | 6 | 2026-04-24 |
| THY208 | Turkish Airlines | 6 | 2026-07-01 |
| THY12V | - | 6 | 2026-06-29 |
| THY067 | Turkish Airlines | 6 | 2026-05-13 |
| THY801 | Turkish Airlines | 5 | 2026-06-02 |
| THY49A | - | 5 | 2026-07-10 |
| THY45T | Turkish Airlines | 5 | 2026-07-05 |
| THY39V | - | 5 | 2026-07-11 |
| THY164 | - | 5 | 2026-07-02 |
| THY10J | Turkish Airlines | 5 | 2026-07-04 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | THY903 | - | Jul 13, 12:15 UTC | Jul 13, 23:00 UTC | 10h 45m |
| 2026-07-13 | THY2JS | - | Jul 13, 00:40 UTC | Jul 13, 09:20 UTC | 8h 40m |
| 2026-07-12 | THY40Y | - | Jul 12, 12:30 UTC | Jul 12, 21:35 UTC | 9h 5m |
| 2026-07-12 | THY2YR | - | Jul 12, 07:10 UTC | Jul 12, 08:35 UTC | 1h 25m |
| 2026-07-12 | THY39GV | - | Jul 12, 04:05 UTC | Jul 12, 05:20 UTC | 1h 15m |
| 2026-07-11 | THY39V | - | Jul 11, 15:40 UTC | Jul 12, 01:50 UTC | 10h 10m |
| 2026-07-10 | THY49A | - | Jul 10, 23:20 UTC | Jul 11, 08:55 UTC | 9h 35m |
| 2026-07-08 | THY175 | - | Jul 8, 22:25 UTC | Jul 9, 08:45 UTC | 10h 20m |
| 2026-07-08 | THY175 | SYD → KUL | Jul 8, 11:30 UTC | Jul 8, 20:20 UTC | 8h 50m |
| 2026-07-08 | THY174 | KUL → SYD | Jul 8, 01:20 UTC | Jul 8, 08:45 UTC | 7h 25m |
| 2026-07-07 | THY174 | KUL → SYD | Jul 7, 13:45 UTC | Jul 7, 23:05 UTC | 9h 20m |
| 2026-07-06 | THY4MS | - | Jul 6, 20:15 UTC | Jul 7, 07:55 UTC | 11h 40m |
| 2026-07-06 | THY73G | - | Jul 6, 05:05 UTC | Jul 6, 18:05 UTC | 13h 0m |
| 2026-07-05 | THY45T | CPT → IST | Jul 5, 14:45 UTC | Jul 6, 01:05 UTC | 10h 20m |
| 2026-07-04 | THY10J | IST → CPT | Jul 4, 23:20 UTC | Jul 5, 09:30 UTC | 10h 10m |
| 2026-07-04 | THY9FG | - | Jul 4, 11:30 UTC | Jul 4, 14:00 UTC | 2h 30m |
| 2026-07-04 | THY2WM | - | Jul 4, 05:25 UTC | Jul 4, 08:10 UTC | 2h 45m |
| 2026-07-03 | THY165 | HAN → IST | Jul 3, 16:50 UTC | Jul 4, 02:10 UTC | 9h 20m |
| 2026-07-02 | THY164 | - | Jul 2, 23:20 UTC | Jul 3, 07:10 UTC | 7h 50m |
| 2026-07-02 | THY9ZP | - | Jul 2, 19:10 UTC | Jul 2, 19:40 UTC | 30m |
| 2026-07-02 | THY7UW | IST → BSL | Jul 2, 16:40 UTC | Jul 2, 17:15 UTC | 35m |
| 2026-07-02 | THY209 | - | Jul 2, 02:45 UTC | Jul 2, 13:25 UTC | 10h 40m |
| 2026-07-01 | THY208 | IST → SIN | Jul 1, 14:30 UTC | Jul 2, 00:25 UTC | 9h 55m |
| 2026-07-01 | THY1RT | - | Jul 1, 02:30 UTC | Jul 1, 11:05 UTC | 8h 35m |
| 2026-06-30 | THY81D | IST → BOS | Jun 30, 22:20 UTC | Jun 30, 23:10 UTC | 50m |
| 2026-06-30 | THY81D | IST → BOS | Jun 30, 14:10 UTC | Jun 30, 22:15 UTC | 8h 5m |
| 2026-06-30 | THY2JT | - | Jun 30, 09:30 UTC | Jun 30, 11:35 UTC | 2h 5m |
| 2026-06-30 | THY6AG | - | Jun 30, 04:55 UTC | Jun 30, 06:50 UTC | 1h 55m |
| 2026-06-29 | THY12V | - | Jun 29, 23:25 UTC | Jun 30, 01:09 UTC | 1h 45m |
| 2026-06-29 | THY12V | - | Jun 29, 01:05 UTC | Jun 30, 01:00 UTC | 23h 55m |
| 2026-06-29 | THY71M | - | Jun 29, 00:05 UTC | Jun 29, 01:50 UTC | 1h 45m |
| 2026-06-28 | THY209 | - | Jun 28, 02:49 UTC | Jun 28, 13:25 UTC | 10h 35m |
| 2026-06-27 | THY208 | IST → SIN | Jun 27, 14:39 UTC | Jun 28, 00:30 UTC | 9h 50m |
| 2026-06-27 | THY3ES | - | Jun 27, 09:09 UTC | Jun 27, 11:30 UTC | 2h 20m |
| 2026-06-27 | THY9FP | - | Jun 27, 04:24 UTC | Jun 27, 06:30 UTC | 2h 5m |
| 2026-06-26 | THY057 | CGK → IST | Jun 26, 14:09 UTC | Jun 27, 01:35 UTC | 11h 25m |
| 2026-06-26 | THY056 | - | Jun 26, 09:59 UTC | Jun 26, 10:20 UTC | 20m |
| 2026-06-25 | THY056 | - | Jun 25, 23:19 UTC | Jun 26, 09:24 UTC | 10h 5m |
| 2026-06-25 | THY48L | - | Jun 25, 03:34 UTC | Jun 25, 13:00 UTC | 9h 25m |
| 2026-06-25 | THY48L | - | Jun 25, 02:30 UTC | Jun 25, 02:39 UTC | 10m |
| 2026-06-24 | THY45M | IST → KUL | Jun 24, 14:15 UTC | Jun 24, 23:34 UTC | 9h 20m |
| 2026-06-24 | THY3ES | - | Jun 24, 09:15 UTC | Jun 24, 11:29 UTC | 2h 15m |
| 2026-06-24 | THY9FP | - | Jun 24, 04:24 UTC | Jun 24, 06:35 UTC | 2h 10m |
| 2026-06-23 | THY904 | PTY → IST | Jun 23, 00:19 UTC | Jun 23, 17:30 UTC | 17h 10m |
| 2026-06-22 | THY904 | PTY → IST | Jun 22, 17:04 UTC | Jun 23, 16:59 UTC | 23h 55m |
| 2026-06-22 | THY903 | - | Jun 22, 15:05 UTC | Jun 23, 14:59 UTC | 23h 55m |
| 2026-06-22 | THY903 | - | Jun 22, 14:19 UTC | Jun 23, 13:00 UTC | 22h 40m |
| 2026-06-22 | THY175 | SYD → KUL | Jun 22, 00:29 UTC | Jun 22, 10:44 UTC | 10h 15m |
| 2026-06-21 | THY175 | SYD → KUL | Jun 21, 14:15 UTC | Jun 21, 22:24 UTC | 8h 10m |
| 2026-06-21 | THY174 | KUL → SYD | Jun 21, 02:04 UTC | Jun 21, 09:24 UTC | 7h 20m |
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-LGD page for operator, model, and routing details .