sensors Mode-S transponder
4BB14F
ICAO 24-bit transponder address · allocated to Turkey
Currently assigned to TC-LJO · BOEING 777-200LR
- Hex
- 4BB14F
- Octal
- 22730517
- Decimal
- 4,960,591
- Country
- TR
- Tail
- TC-LJO
- Type
- B77L
- Flights observed
- 119
- Distinct callsigns
- 20
- Country
- TR
- Last broadcast
- 48m ago
Last known position
Country allocation
The ICAO 24-bit address 4BB14F 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 |
|---|---|---|---|
| THY6024 | Turkish Airlines | 6 | 2026-05-18 |
| THY6023 | Turkish Airlines | 6 | 2026-05-17 |
| THY6589 | Turkish Airlines | 5 | 2026-05-06 |
| THY6437 | Turkish Airlines | 5 | 2026-05-14 |
| THY6273 | - | 5 | 2026-05-01 |
| THY6433 | Turkish Airlines | 4 | 2026-05-08 |
| THY6418 | Turkish Airlines | 4 | 2026-05-29 |
| THY6393 | Turkish Airlines | 4 | 2026-05-12 |
| THY6266 | - | 4 | 2026-04-13 |
| THY6260 | Turkish Airlines | 4 | 2026-04-30 |
| THY6090 | - | 4 | 2026-04-24 |
| THY6060 | - | 4 | 2026-04-13 |
| THY6588 | - | 3 | 2026-05-06 |
| THY6417 | Turkish Airlines | 3 | 2026-04-14 |
| THY6392 | Turkish Airlines | 3 | 2026-04-27 |
| THY6353 | Turkish Airlines | 3 | 2026-05-16 |
| THY6352 | Turkish Airlines | 3 | 2026-05-15 |
| THY6182 | Turkish Airlines | 3 | 2026-05-20 |
| THY6681 | - | 2 | 2026-05-26 |
| THY6611 | Turkish Airlines | 2 | 2026-05-15 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | THY6418 | MAD → IST | May 29, 20:45 UTC | May 29, 23:45 UTC | 3h 0m |
| 2026-05-29 | THY6591 | - | May 29, 17:50 UTC | May 29, 18:05 UTC | 15m |
| 2026-05-29 | THY6591 | - | May 29, 01:30 UTC | May 29, 17:05 UTC | 15h 36m |
| 2026-05-28 | THY6590 | FRU → FRU | May 28, 15:50 UTC | May 29, 15:45 UTC | 23h 55m |
| 2026-05-28 | THY6590 | FRU → FRU | May 28, 15:20 UTC | May 29, 08:35 UTC | 17h 15m |
| 2026-05-28 | THY6751 | - | May 28, 09:00 UTC | May 28, 12:10 UTC | 3h 10m |
| 2026-05-28 | THY6750 | - | May 28, 03:30 UTC | May 28, 06:45 UTC | 3h 15m |
| 2026-05-27 | THY6299 | - | May 27, 23:35 UTC | May 28, 01:45 UTC | 2h 10m |
| 2026-05-27 | THY6299 | - | May 27, 15:20 UTC | May 27, 15:35 UTC | 15m |
| 2026-05-27 | THY6290 | - | May 27, 11:30 UTC | May 27, 12:00 UTC | 30m |
| 2026-05-26 | THY6290 | - | May 26, 22:50 UTC | May 27, 09:15 UTC | 10h 25m |
| 2026-05-26 | THY6681 | - | May 26, 18:19 UTC | May 26, 18:30 UTC | 10m |
| 2026-05-26 | THY6681 | - | May 26, 07:29 UTC | May 26, 17:39 UTC | 10h 10m |
| 2026-05-25 | THY6680 | BOM → BOM | May 25, 18:20 UTC | May 26, 04:39 UTC | 10h 20m |
| 2026-05-22 | THY6118 | IST → MAA | May 22, 02:20 UTC | May 22, 14:10 UTC | 11h 50m |
| 2026-05-21 | THY6307 | IST → MST | May 21, 01:35 UTC | May 21, 14:25 UTC | 12h 50m |
| 2026-05-20 | THY6182 | ATL → IST | May 20, 22:20 UTC | May 20, 22:30 UTC | 10m |
| 2026-05-20 | THY6182 | ATL → IST | May 20, 10:50 UTC | May 20, 21:40 UTC | 10h 50m |
| 2026-05-20 | THY6177 | HKG → HKG | May 20, 02:15 UTC | May 20, 04:10 UTC | 1h 55m |
| 2026-05-19 | THY6584 | IST → PVG | May 19, 00:10 UTC | May 19, 13:30 UTC | 13h 20m |
| 2026-05-18 | THY6584 | IST → PVG | May 18, 23:20 UTC | May 18, 23:30 UTC | 10m |
| 2026-05-18 | THY6024 | MIA → MST | May 18, 17:25 UTC | May 18, 19:50 UTC | 2h 24m |
| 2026-05-18 | THY6024 | MIA → MST | May 18, 07:00 UTC | May 18, 15:25 UTC | 8h 25m |
| 2026-05-17 | THY6023 | OSL → OSL | May 17, 15:55 UTC | May 18, 04:15 UTC | 12h 20m |
| 2026-05-17 | THY6023 | OSL → OSL | May 17, 01:35 UTC | May 17, 12:15 UTC | 10h 40m |
| 2026-05-16 | THY6353 | IST → LGW | May 16, 11:25 UTC | May 16, 21:45 UTC | 10h 20m |
| 2026-05-15 | THY6352 | LGW → IST | May 15, 22:35 UTC | May 16, 08:20 UTC | 9h 46m |
| 2026-05-15 | THY6612 | ORD → IST | May 15, 08:40 UTC | May 15, 18:25 UTC | 9h 44m |
| 2026-05-15 | THY6611 | MST → IST | May 15, 03:15 UTC | May 15, 05:00 UTC | 1h 45m |
| 2026-05-14 | THY6611 | MST → IST | May 14, 13:35 UTC | May 14, 23:40 UTC | 10h 5m |
| 2026-05-14 | THY6437 | IST → MIA | May 14, 07:10 UTC | May 14, 09:10 UTC | 2h 0m |
| 2026-05-13 | THY6437 | IST → MIA | May 13, 22:00 UTC | May 14, 05:10 UTC | 7h 10m |
| 2026-05-13 | THY6573 | - | May 13, 10:10 UTC | May 13, 17:45 UTC | 7h 35m |
| 2026-05-12 | THY6573 | - | May 12, 12:20 UTC | May 13, 11:45 UTC | 23h 25m |
| 2026-05-12 | THY6393 | FRU → IST | May 12, 04:10 UTC | May 12, 13:20 UTC | 9h 10m |
| 2026-05-11 | THY6393 | FRU → IST | May 11, 20:05 UTC | May 11, 20:20 UTC | 15m |
| 2026-05-11 | THY6390 | BUD → IST | May 11, 15:20 UTC | May 11, 15:50 UTC | 30m |
| 2026-05-11 | THY6390 | BUD → IST | May 11, 07:05 UTC | May 11, 08:15 UTC | 1h 10m |
| 2026-05-10 | THY6144 | IST → RUH | May 10, 10:45 UTC | May 11, 02:45 UTC | 16h 0m |
| 2026-05-10 | THY6144 | IST → RUH | May 10, 06:59 UTC | May 10, 08:00 UTC | 1h 0m |
| 2026-05-09 | THY6434 | CDG → IST | May 9, 18:00 UTC | May 9, 20:20 UTC | 2h 20m |
| 2026-05-08 | THY6433 | IST → CDG | May 8, 23:00 UTC | May 9, 14:25 UTC | 15h 25m |
| 2026-05-08 | THY6433 | IST → CDG | May 8, 16:00 UTC | May 9, 14:25 UTC | 22h 25m |
| 2026-05-08 | THY6593 | - | May 8, 07:50 UTC | May 9, 07:40 UTC | 23h 50m |
| 2026-05-08 | THY6592 | IST → VNO | May 8, 06:25 UTC | May 8, 23:20 UTC | 16h 55m |
| 2026-05-07 | THY6437 | IST → MIA | May 7, 22:10 UTC | May 7, 23:55 UTC | 1h 45m |
| 2026-05-07 | THY6437 | IST → MIA | May 7, 17:55 UTC | May 7, 19:10 UTC | 1h 15m |
| 2026-05-07 | THY6437 | IST → MIA | May 7, 10:30 UTC | May 7, 13:25 UTC | 2h 55m |
| 2026-05-06 | THY6589 | TBS → HKG | May 6, 15:50 UTC | May 7, 06:55 UTC | 15h 4m |
| 2026-05-06 | THY6588 | - | May 6, 06:40 UTC | May 6, 22:55 UTC | 16h 14m |
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-LJO page for operator, model, and routing details .