sensors Mode-S transponder
4BB154
ICAO 24-bit transponder address · allocated to Turkey
Currently assigned to TC-LJT · BOEING 777-200LR
- Hex
- 4BB154
- Octal
- 22730524
- Decimal
- 4,960,596
- Country
- TR
- Tail
- TC-LJT
- Type
- B77L
- Flights observed
- 284
- Distinct callsigns
- 20
- Country
- TR
- Last broadcast
- Jul 26, 22:50 UTC
Last known position
Country allocation
The ICAO 24-bit address 4BB154 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 |
|---|---|---|---|
| THY6355 | Turkish Airlines | 11 | 2026-06-14 |
| THY6626 | Turkish Airlines | 10 | 2026-07-20 |
| THY6437 | - | 8 | 2026-07-02 |
| THY6228 | Turkish Airlines | 8 | 2026-04-18 |
| THY6579 | - | 7 | 2026-07-24 |
| THY6354 | - | 7 | 2026-06-13 |
| THY6350 | Turkish Airlines | 6 | 2026-07-21 |
| THY6263 | - | 6 | 2026-06-23 |
| THY6058 | Turkish Airlines | 6 | 2026-07-23 |
| THY6627 | Turkish Airlines | 5 | 2026-07-20 |
| THY6591 | - | 5 | 2026-07-02 |
| THY6351 | - | 5 | 2026-07-21 |
| THY6299 | - | 5 | 2026-06-03 |
| THY6255 | Turkish Airlines | 5 | 2026-04-27 |
| THY6116 | - | 5 | 2026-06-19 |
| THY6590 | - | 4 | 2026-07-02 |
| THY6577 | Turkish Airlines | 4 | 2026-06-05 |
| THY6297 | Turkish Airlines | 4 | 2026-04-15 |
| THY6251 | - | 4 | 2026-07-16 |
| THY6245 | Turkish Airlines | 4 | 2026-04-26 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | THY6596 | IST → FRU | Jul 26, 05:45 UTC | Jul 26, 22:50 UTC | 17h 6m |
| 2026-07-25 | THY6434 | CDG → IST | Jul 25, 18:50 UTC | Jul 25, 21:50 UTC | 3h 0m |
| 2026-07-25 | THY6433 | IST → CDG | Jul 25, 10:50 UTC | Jul 25, 13:40 UTC | 2h 50m |
| 2026-07-24 | THY6579 | - | Jul 24, 23:00 UTC | Jul 25, 07:40 UTC | 8h 40m |
| 2026-07-24 | THY6579 | - | Jul 24, 07:05 UTC | Jul 25, 07:00 UTC | 23h 55m |
| 2026-07-24 | THY6579 | - | Jul 24, 06:00 UTC | Jul 25, 05:00 UTC | 23h 0m |
| 2026-07-23 | THY6058 | LCK → IST | Jul 23, 14:05 UTC | Jul 23, 20:10 UTC | 6h 5m |
| 2026-07-23 | THY6058 | LCK → IST | Jul 23, 05:55 UTC | Jul 23, 12:00 UTC | 6h 5m |
| 2026-07-22 | THY6057 | IST → CDG | Jul 22, 11:10 UTC | Jul 23, 02:15 UTC | 15h 5m |
| 2026-07-22 | THY6057 | IST → CDG | Jul 22, 05:15 UTC | Jul 23, 02:15 UTC | 21h 0m |
| 2026-07-21 | THY6351 | - | Jul 21, 21:05 UTC | Jul 21, 21:20 UTC | 15m |
| 2026-07-21 | THY6350 | MCT → HAN | Jul 21, 17:30 UTC | Jul 21, 17:55 UTC | 25m |
| 2026-07-21 | THY6350 | MCT → HAN | Jul 21, 09:45 UTC | Jul 21, 15:45 UTC | 6h 0m |
| 2026-07-21 | THY6350 | MCT → HAN | Jul 21, 03:30 UTC | Jul 21, 05:15 UTC | 1h 45m |
| 2026-07-20 | THY6627 | MAD → BLL | Jul 20, 12:55 UTC | Jul 21, 00:20 UTC | 11h 25m |
| 2026-07-20 | THY6626 | LGG → IST | Jul 20, 08:00 UTC | Jul 20, 09:55 UTC | 1h 55m |
| 2026-07-19 | THY6626 | LGG → IST | Jul 19, 18:25 UTC | Jul 20, 04:55 UTC | 10h 30m |
| 2026-07-19 | THY6406 | FRA → IST | Jul 19, 11:50 UTC | Jul 19, 14:10 UTC | 2h 20m |
| 2026-07-19 | THY6405 | IST → FRA | Jul 19, 06:00 UTC | Jul 19, 08:25 UTC | 2h 25m |
| 2026-07-18 | THY6040 | ATL → IST | Jul 18, 19:00 UTC | Jul 18, 21:40 UTC | 2h 40m |
| 2026-07-18 | THY6040 | ATL → IST | Jul 18, 06:25 UTC | Jul 18, 15:05 UTC | 8h 40m |
| 2026-07-17 | THY6039 | ATL → ORD | Jul 17, 16:15 UTC | Jul 18, 03:55 UTC | 11h 41m |
| 2026-07-17 | THY6039 | ATL → ORD | Jul 17, 01:20 UTC | Jul 17, 12:10 UTC | 10h 50m |
| 2026-07-16 | THY6251 | - | Jul 16, 21:15 UTC | Jul 16, 21:35 UTC | 20m |
| 2026-07-16 | THY6251 | - | Jul 16, 10:45 UTC | Jul 16, 20:39 UTC | 9h 55m |
| 2026-07-15 | THY6246 | - | Jul 15, 21:30 UTC | Jul 16, 07:35 UTC | 10h 5m |
| 2026-07-15 | THY6237 | - | Jul 15, 09:55 UTC | Jul 15, 18:20 UTC | 8h 25m |
| 2026-07-15 | THY6237 | - | Jul 15, 07:50 UTC | Jul 15, 08:00 UTC | 10m |
| 2026-07-15 | THY6127 | - | Jul 15, 03:40 UTC | Jul 15, 04:15 UTC | 35m |
| 2026-07-14 | THY6127 | - | Jul 14, 20:25 UTC | Jul 15, 01:50 UTC | 5h 24m |
| 2026-07-14 | THY6127 | - | Jul 14, 12:55 UTC | Jul 14, 18:10 UTC | 5h 15m |
| 2026-07-13 | THY6585 | - | Jul 13, 23:25 UTC | Jul 14, 08:55 UTC | 9h 30m |
| 2026-07-13 | THY6585 | - | Jul 13, 12:55 UTC | Jul 14, 08:55 UTC | 20h 0m |
| 2026-07-13 | THY6585 | - | Jul 13, 09:15 UTC | Jul 14, 08:55 UTC | 23h 40m |
| 2026-07-13 | THY6584 | - | Jul 13, 08:25 UTC | Jul 14, 07:00 UTC | 22h 35m |
| 2026-07-12 | THY6060 | - | Jul 12, 20:01 UTC | Jul 13, 06:01 UTC | 10h 0m |
| 2026-07-12 | THY6059 | JFK → ORD | Jul 12, 14:20 UTC | Jul 12, 16:15 UTC | 1h 55m |
| 2026-07-12 | THY6059 | - | Jul 12, 00:35 UTC | Jul 12, 10:20 UTC | 9h 45m |
| 2026-07-11 | THY6040 | - | Jul 11, 18:25 UTC | Jul 11, 20:50 UTC | 2h 25m |
| 2026-07-11 | THY6040 | - | Jul 11, 07:40 UTC | Jul 11, 16:10 UTC | 8h 30m |
| 2026-07-10 | THY6039 | ORD → MIA | Jul 10, 15:30 UTC | Jul 11, 05:01 UTC | 13h 31m |
| 2026-07-10 | THY6039 | - | Jul 10, 01:05 UTC | Jul 10, 11:55 UTC | 10h 50m |
| 2026-07-09 | THY6251 | - | Jul 9, 21:50 UTC | Jul 9, 22:15 UTC | 25m |
| 2026-07-09 | THY6251 | - | Jul 9, 11:05 UTC | Jul 9, 21:15 UTC | 10h 10m |
| 2026-07-08 | THY6246 | - | Jul 8, 21:45 UTC | Jul 9, 07:45 UTC | 10h 0m |
| 2026-07-07 | THY6367 | - | Jul 7, 01:30 UTC | Jul 7, 01:40 UTC | 10m |
| 2026-07-06 | THY6367 | - | Jul 6, 14:05 UTC | Jul 7, 00:35 UTC | 10h 30m |
| 2026-07-06 | THY6364 | - | Jul 6, 01:10 UTC | Jul 6, 11:45 UTC | 10h 35m |
| 2026-07-05 | THY6406 | - | Jul 5, 20:05 UTC | Jul 5, 22:15 UTC | 2h 10m |
| 2026-07-05 | THY6405 | - | Jul 5, 15:05 UTC | Jul 5, 17:35 UTC | 2h 30m |
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-LJT page for operator, model, and routing details .