sensors Mode-S transponder
4BB150
ICAO 24-bit transponder address · allocated to Turkey
Currently assigned to TC-LJP · BOEING 777-200LR
- Hex
- 4BB150
- Octal
- 22730520
- Decimal
- 4,960,592
- Country
- TR
- Tail
- TC-LJP
- Type
- B77L
- Flights observed
- 273
- Distinct callsigns
- 20
- Country
- TR
- Last broadcast
- Jul 26, 21:10 UTC
Last known position
Country allocation
The ICAO 24-bit address 4BB150 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 |
|---|---|---|---|
| THY6583 | - | 11 | 2026-06-08 |
| THY6040 | Turkish Airlines | 9 | 2026-06-24 |
| THY6039 | - | 8 | 2026-06-23 |
| THY6320 | - | 6 | 2026-06-26 |
| THY6212 | - | 6 | 2026-07-17 |
| THY6434 | Turkish Airlines | 5 | 2026-07-18 |
| THY6267 | - | 5 | 2026-07-07 |
| THY6235 | Turkish Airlines | 5 | 2026-06-06 |
| THY6228 | Turkish Airlines | 5 | 2026-05-30 |
| THY6216 | - | 5 | 2026-06-22 |
| THY6116 | Turkish Airlines | 5 | 2026-06-05 |
| THY6680 | Turkish Airlines | 4 | 2026-05-31 |
| THY6593 | - | 4 | 2026-06-20 |
| THY6587 | Turkish Airlines | 4 | 2026-06-03 |
| THY6581 | Turkish Airlines | 4 | 2026-07-26 |
| THY6571 | - | 4 | 2026-06-16 |
| THY6406 | - | 4 | 2026-07-03 |
| THY6263 | Turkish Airlines | 4 | 2026-04-14 |
| THY6261 | - | 4 | 2026-06-11 |
| THY6255 | - | 4 | 2026-07-14 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | THY6315 | FRU → SZX | Jul 26, 15:00 UTC | Jul 26, 21:05 UTC | 6h 5m |
| 2026-07-26 | THY6581 | CAN → IST | Jul 26, 07:25 UTC | Jul 26, 07:50 UTC | 25m |
| 2026-07-25 | THY6581 | CAN → IST | Jul 25, 22:30 UTC | Jul 26, 06:55 UTC | 8h 26m |
| 2026-07-25 | THY6581 | CAN → IST | Jul 25, 08:10 UTC | Jul 26, 06:55 UTC | 22h 46m |
| 2026-07-25 | THY6581 | CAN → IST | Jul 25, 07:15 UTC | Jul 26, 06:00 UTC | 22h 45m |
| 2026-07-24 | THY6111 | IST → JNB | Jul 24, 21:55 UTC | Jul 25, 04:15 UTC | 6h 20m |
| 2026-07-24 | THY6110 | - | Jul 24, 11:20 UTC | Jul 24, 17:35 UTC | 6h 15m |
| 2026-07-24 | THY6113 | HKG → IST | Jul 24, 01:20 UTC | Jul 24, 07:35 UTC | 6h 15m |
| 2026-07-23 | THY6112 | IST → BOM | Jul 23, 14:40 UTC | Jul 23, 20:45 UTC | 6h 5m |
| 2026-07-21 | THY6356 | MXP → IST | Jul 21, 15:00 UTC | Jul 21, 15:30 UTC | 30m |
| 2026-07-21 | THY6356 | MXP → IST | Jul 21, 13:15 UTC | Jul 21, 14:25 UTC | 1h 10m |
| 2026-07-21 | THY6356 | - | Jul 21, 05:05 UTC | Jul 21, 05:15 UTC | 10m |
| 2026-07-21 | THY6345 | - | Jul 21, 01:00 UTC | Jul 21, 01:30 UTC | 30m |
| 2026-07-20 | THY6345 | - | Jul 20, 17:20 UTC | Jul 20, 23:15 UTC | 5h 55m |
| 2026-07-20 | THY6345 | - | Jul 20, 10:30 UTC | Jul 20, 14:55 UTC | 4h 25m |
| 2026-07-20 | THY6139 | HKG → BOM | Jul 20, 04:45 UTC | Jul 20, 06:30 UTC | 1h 45m |
| 2026-07-19 | THY6139 | HKG → BOM | Jul 19, 23:40 UTC | Jul 20, 01:00 UTC | 1h 20m |
| 2026-07-19 | THY6119 | HKG → IST | Jul 19, 03:10 UTC | Jul 19, 20:55 UTC | 17h 45m |
| 2026-07-18 | THY6434 | CDG → IST | Jul 18, 21:15 UTC | Jul 18, 23:50 UTC | 2h 35m |
| 2026-07-18 | THY6434 | CDG → IST | Jul 18, 16:40 UTC | Jul 18, 17:30 UTC | 50m |
| 2026-07-18 | THY6434 | CDG → IST | Jul 18, 12:00 UTC | Jul 18, 14:55 UTC | 2h 55m |
| 2026-07-18 | THY6154 | IST → AMM | Jul 18, 08:25 UTC | Jul 18, 08:55 UTC | 30m |
| 2026-07-17 | THY6154 | IST → AMM | Jul 17, 14:39 UTC | Jul 17, 19:05 UTC | 4h 25m |
| 2026-07-17 | THY6212 | - | Jul 17, 00:45 UTC | Jul 17, 11:00 UTC | 10h 15m |
| 2026-07-16 | THY6212 | - | Jul 16, 21:50 UTC | Jul 16, 22:05 UTC | 15m |
| 2026-07-16 | THY6212 | - | Jul 16, 08:25 UTC | Jul 16, 17:05 UTC | 8h 40m |
| 2026-07-16 | THY6186 | - | Jul 16, 02:40 UTC | Jul 16, 04:45 UTC | 2h 5m |
| 2026-07-15 | THY6186 | - | Jul 15, 10:45 UTC | Jul 16, 00:10 UTC | 13h 25m |
| 2026-07-14 | THY6573 | - | Jul 14, 21:35 UTC | Jul 15, 05:55 UTC | 8h 19m |
| 2026-07-14 | THY6573 | - | Jul 14, 20:45 UTC | Jul 14, 21:00 UTC | 15m |
| 2026-07-14 | THY6572 | - | Jul 14, 06:10 UTC | Jul 14, 08:00 UTC | 1h 50m |
| 2026-07-14 | THY6255 | - | Jul 14, 02:40 UTC | Jul 14, 03:00 UTC | 20m |
| 2026-07-13 | THY6255 | - | Jul 13, 12:15 UTC | Jul 14, 02:05 UTC | 13h 50m |
| 2026-07-13 | THY6255 | - | Jul 13, 06:15 UTC | Jul 14, 02:05 UTC | 19h 50m |
| 2026-07-13 | THY6255 | - | Jul 13, 03:40 UTC | Jul 14, 02:00 UTC | 22h 20m |
| 2026-07-13 | THY6340 | - | Jul 13, 02:01 UTC | Jul 13, 02:25 UTC | 25m |
| 2026-07-12 | THY6245 | - | Jul 12, 21:50 UTC | Jul 12, 22:05 UTC | 15m |
| 2026-07-12 | THY6245 | - | Jul 12, 16:15 UTC | Jul 12, 21:10 UTC | 4h 55m |
| 2026-07-12 | THY6245 | - | Jul 12, 11:15 UTC | Jul 12, 14:25 UTC | 3h 10m |
| 2026-07-11 | THY6244 | - | Jul 11, 23:20 UTC | Jul 12, 07:25 UTC | 8h 5m |
| 2026-07-11 | THY6244 | - | Jul 11, 19:50 UTC | Jul 11, 20:55 UTC | 1h 5m |
| 2026-07-10 | THY6661 | - | Jul 10, 20:05 UTC | Jul 11, 14:30 UTC | 18h 25m |
| 2026-07-10 | THY6661 | - | Jul 10, 19:45 UTC | Jul 11, 14:30 UTC | 18h 45m |
| 2026-07-10 | THY6355 | - | Jul 10, 05:55 UTC | Jul 10, 15:30 UTC | 9h 35m |
| 2026-07-10 | THY6355 | - | Jul 10, 04:45 UTC | Jul 10, 05:00 UTC | 15m |
| 2026-07-10 | THY6354 | - | Jul 10, 01:30 UTC | Jul 10, 01:50 UTC | 20m |
| 2026-07-09 | THY6354 | - | Jul 9, 17:05 UTC | Jul 10, 00:40 UTC | 7h 35m |
| 2026-07-09 | THY6575 | - | Jul 9, 05:30 UTC | Jul 9, 13:40 UTC | 8h 10m |
| 2026-07-09 | THY6575 | - | Jul 9, 03:35 UTC | Jul 9, 03:45 UTC | 10m |
| 2026-07-08 | THY6574 | - | Jul 8, 06:30 UTC | Jul 8, 08:15 UTC | 1h 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-LJP page for operator, model, and routing details .