sensors Mode-S transponder
4BB159
ICAO 24-bit transponder address · allocated to Turkey
Currently assigned to TC-LJY · BOEING 777-200LR
- Hex
- 4BB159
- Octal
- 22730531
- Decimal
- 4,960,601
- Country
- TR
- Tail
- TC-LJY
- Type
- B77L
- Flights observed
- 128
- Distinct callsigns
- 20
- Country
- TR
- Last broadcast
- 4h ago
Current position
Country allocation
The ICAO 24-bit address 4BB159 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 |
|---|---|---|---|
| THY6626 | Turkish Airlines | 6 | 2026-05-27 |
| THY6202 | Turkish Airlines | 6 | 2026-05-16 |
| THY6090 | - | 6 | 2026-04-17 |
| THY6350 | Turkish Airlines | 5 | 2026-04-28 |
| THY6571 | - | 4 | 2026-05-19 |
| THY6439 | - | 4 | 2026-04-13 |
| THY6351 | Turkish Airlines | 4 | 2026-04-29 |
| THY6309 | Turkish Airlines | 4 | 2026-04-23 |
| THY6203 | Turkish Airlines | 4 | 2026-05-16 |
| THY6058 | Turkish Airlines | 4 | 2026-04-30 |
| THY6057 | Turkish Airlines | 4 | 2026-04-29 |
| THY6023 | Turkish Airlines | 4 | 2026-04-26 |
| THY6627 | Turkish Airlines | 3 | 2026-05-27 |
| THY6591 | - | 3 | 2026-05-08 |
| THY6573 | - | 3 | 2026-05-20 |
| THY6354 | Turkish Airlines | 3 | 2026-04-24 |
| THY6307 | Turkish Airlines | 3 | 2026-04-22 |
| THY6597 | Turkish Airlines | 2 | 2026-05-17 |
| THY6596 | - | 2 | 2026-05-17 |
| THY6589 | Turkish Airlines | 2 | 2026-05-29 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-30 | THY6111 | IST → JNB | May 30, 03:25 UTC | May 30, 03:45 UTC | 20m |
| 2026-05-29 | THY6111 | IST → JNB | May 29, 20:55 UTC | May 30, 02:45 UTC | 5h 50m |
| 2026-05-29 | THY6110 | - | May 29, 11:25 UTC | May 29, 17:30 UTC | 6h 5m |
| 2026-05-29 | THY6589 | TBS → HKG | May 29, 03:50 UTC | May 29, 04:10 UTC | 20m |
| 2026-05-28 | THY6589 | TBS → HKG | May 28, 11:35 UTC | May 29, 03:05 UTC | 15h 30m |
| 2026-05-28 | THY6588 | - | May 28, 02:20 UTC | May 28, 22:35 UTC | 20h 15m |
| 2026-05-28 | THY6588 | - | May 28, 02:05 UTC | May 28, 22:35 UTC | 20h 30m |
| 2026-05-27 | THY6627 | MAD → BLL | May 27, 12:15 UTC | May 27, 23:15 UTC | 11h 0m |
| 2026-05-27 | THY6626 | LGG → IST | May 27, 06:09 UTC | May 27, 09:25 UTC | 3h 16m |
| 2026-05-26 | THY6626 | LGG → IST | May 26, 16:50 UTC | May 27, 03:20 UTC | 10h 30m |
| 2026-05-25 | THY6233 | HAN → IST | May 25, 14:15 UTC | May 26, 03:35 UTC | 13h 19m |
| 2026-05-25 | THY6196 | - | May 25, 09:45 UTC | May 25, 10:00 UTC | 15m |
| 2026-05-25 | THY6196 | - | May 25, 04:30 UTC | May 25, 08:45 UTC | 4h 15m |
| 2026-05-24 | THY6410 | MST → IST | May 24, 21:10 UTC | May 24, 23:46 UTC | 2h 36m |
| 2026-05-24 | THY6409 | IST → MIA | May 24, 14:25 UTC | May 24, 17:00 UTC | 2h 35m |
| 2026-05-23 | THY6034 | IAH → IST | May 23, 18:30 UTC | May 24, 05:35 UTC | 11h 5m |
| 2026-05-23 | THY6034 | IAH → IST | May 23, 13:30 UTC | May 23, 15:05 UTC | 1h 35m |
| 2026-05-22 | THY6033 | IST → HEL | May 22, 23:00 UTC | May 23, 10:25 UTC | 11h 24m |
| 2026-05-20 | THY6033 | IST → HEL | May 20, 20:40 UTC | May 20, 23:15 UTC | 2h 35m |
| 2026-05-20 | THY6573 | - | May 20, 17:00 UTC | May 20, 17:15 UTC | 15m |
| 2026-05-20 | THY6573 | - | May 20, 09:45 UTC | May 20, 16:20 UTC | 6h 35m |
| 2026-05-20 | THY6573 | - | May 20, 06:45 UTC | May 20, 06:55 UTC | 10m |
| 2026-05-19 | THY6572 | IST → FRU | May 19, 16:35 UTC | May 19, 18:25 UTC | 1h 50m |
| 2026-05-19 | THY6571 | - | May 19, 13:15 UTC | May 19, 13:25 UTC | 10m |
| 2026-05-19 | THY6571 | - | May 19, 03:15 UTC | May 19, 12:30 UTC | 9h 15m |
| 2026-05-18 | THY6571 | - | May 18, 12:25 UTC | May 19, 12:15 UTC | 23h 49m |
| 2026-05-18 | THY6571 | - | May 18, 11:25 UTC | May 19, 08:05 UTC | 20h 39m |
| 2026-05-17 | THY6597 | FRU → IST | May 17, 15:31 UTC | May 18, 07:15 UTC | 15h 45m |
| 2026-05-17 | THY6596 | - | May 17, 06:50 UTC | May 18, 06:10 UTC | 23h 20m |
| 2026-05-17 | THY6596 | - | May 17, 06:00 UTC | May 17, 06:10 UTC | 10m |
| 2026-05-16 | THY6203 | MST → IST | May 16, 06:50 UTC | May 17, 01:40 UTC | 18h 50m |
| 2026-05-16 | THY6203 | MST → IST | May 16, 02:20 UTC | May 17, 01:40 UTC | 23h 20m |
| 2026-05-16 | THY6202 | MST → IST | May 16, 01:20 UTC | May 17, 00:15 UTC | 22h 56m |
| 2026-05-15 | THY6428 | DWC → MFM | May 15, 19:40 UTC | May 15, 21:25 UTC | 1h 45m |
| 2026-05-15 | THY6427 | IST → MXP | May 15, 14:50 UTC | May 15, 17:05 UTC | 2h 15m |
| 2026-05-15 | THY6212 | - | May 15, 00:55 UTC | May 15, 10:35 UTC | 9h 40m |
| 2026-05-14 | THY6212 | - | May 14, 08:35 UTC | May 14, 21:35 UTC | 13h 0m |
| 2026-05-14 | THY6416 | MAD → IST | May 14, 01:55 UTC | May 14, 04:45 UTC | 2h 50m |
| 2026-05-13 | THY6415 | IST → MAD | May 13, 18:30 UTC | May 13, 22:35 UTC | 4h 5m |
| 2026-05-13 | THY6299 | - | May 13, 11:00 UTC | May 13, 12:10 UTC | 1h 10m |
| 2026-05-13 | THY6299 | - | May 13, 02:50 UTC | May 13, 03:05 UTC | 15m |
| 2026-05-12 | THY6290 | - | May 12, 11:40 UTC | May 12, 23:50 UTC | 12h 10m |
| 2026-05-11 | THY6627 | MAD → BLL | May 11, 20:55 UTC | May 12, 07:55 UTC | 11h 0m |
| 2026-05-11 | THY6626 | LGG → IST | May 11, 15:25 UTC | May 11, 17:30 UTC | 2h 6m |
| 2026-05-11 | THY6626 | LGG → IST | May 11, 01:00 UTC | May 11, 11:45 UTC | 10h 45m |
| 2026-05-10 | THY6203 | MST → IST | May 10, 03:30 UTC | May 10, 20:45 UTC | 17h 15m |
| 2026-05-09 | THY6203 | MST → IST | May 9, 22:20 UTC | May 10, 20:45 UTC | 22h 25m |
| 2026-05-09 | THY6202 | MST → IST | May 9, 21:40 UTC | May 10, 16:25 UTC | 18h 45m |
| 2026-05-09 | THY6202 | MST → IST | May 9, 16:20 UTC | May 10, 16:10 UTC | 23h 50m |
| 2026-05-09 | THY6202 | MST → IST | May 9, 16:00 UTC | May 10, 14:14 UTC | 22h 15m |
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-LJY page for operator, model, and routing details .