sensors Mode-S transponder
4BB149
ICAO 24-bit transponder address · allocated to Turkey
Currently assigned to TC-LJI · BOEING 777-300ER
- Hex
- 4BB149
- Octal
- 22730511
- Decimal
- 4,960,585
- Country
- TR
- Tail
- TC-LJI
- Type
- B77W
- Flights observed
- 196
- Distinct callsigns
- 20
- Country
- TR
- Last broadcast
- 7h ago
Current position
Country allocation
The ICAO 24-bit address 4BB149 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 |
|---|---|---|---|
| THY71 | Turkish Airlines | 16 | 2026-06-20 |
| THY70 | Turkish Airlines | 14 | 2026-06-19 |
| THY199 | - | 8 | 2026-07-14 |
| THY1GJ | Turkish Airlines | 6 | 2026-05-12 |
| THY4 | Turkish Airlines | 5 | 2026-05-31 |
| THY3AX | - | 5 | 2026-07-13 |
| THY3 | Turkish Airlines | 5 | 2026-05-30 |
| THY2XQ | - | 5 | 2026-07-13 |
| THY198 | - | 5 | 2026-07-13 |
| THY8LV | Turkish Airlines | 4 | 2026-05-13 |
| THY8FW | - | 4 | 2026-07-11 |
| THY89 | Turkish Airlines | 4 | 2026-06-15 |
| THY85 | - | 4 | 2026-07-11 |
| THY6KL | - | 4 | 2026-07-11 |
| THY4SD | - | 4 | 2026-07-11 |
| THY2 | Turkish Airlines | 4 | 2026-06-04 |
| THY1 | Turkish Airlines | 4 | 2026-06-03 |
| THY91 | Turkish Airlines | 3 | 2026-05-28 |
| THY9 | Turkish Airlines | 3 | 2026-06-26 |
| THY88 | Turkish Airlines | 3 | 2026-06-13 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | THY199 | - | Jul 14, 12:55 UTC | Jul 14, 15:55 UTC | 3h 0m |
| 2026-07-13 | THY198 | - | Jul 13, 23:55 UTC | Jul 14, 10:40 UTC | 10h 45m |
| 2026-07-13 | THY3AX | - | Jul 13, 19:20 UTC | Jul 13, 20:20 UTC | 1h 0m |
| 2026-07-13 | THY2XQ | - | Jul 13, 16:15 UTC | Jul 13, 17:15 UTC | 1h 0m |
| 2026-07-13 | THY6 | - | Jul 13, 02:01 UTC | Jul 13, 11:55 UTC | 9h 55m |
| 2026-07-12 | THY5 | - | Jul 12, 12:05 UTC | Jul 12, 22:40 UTC | 10h 35m |
| 2026-07-12 | THY66C | - | Jul 12, 08:25 UTC | Jul 12, 09:15 UTC | 50m |
| 2026-07-12 | THY5AB | - | Jul 12, 05:30 UTC | Jul 12, 06:40 UTC | 1h 10m |
| 2026-07-11 | THY4SD | - | Jul 11, 17:50 UTC | Jul 11, 20:50 UTC | 3h 0m |
| 2026-07-11 | THY2LD | - | Jul 11, 12:15 UTC | Jul 11, 15:30 UTC | 3h 15m |
| 2026-07-11 | THY6KL | - | Jul 11, 07:55 UTC | Jul 11, 08:50 UTC | 55m |
| 2026-07-11 | THY8FW | - | Jul 11, 04:55 UTC | Jul 11, 05:55 UTC | 1h 0m |
| 2026-07-11 | THY85 | - | Jul 11, 00:50 UTC | Jul 11, 01:10 UTC | 20m |
| 2026-07-10 | THY85 | - | Jul 10, 14:00 UTC | Jul 11, 00:10 UTC | 10h 10m |
| 2026-07-09 | THY84 | - | Jul 9, 23:55 UTC | Jul 10, 11:10 UTC | 11h 15m |
| 2026-06-29 | THY199 | - | Jun 29, 01:25 UTC | Jun 29, 01:50 UTC | 25m |
| 2026-06-28 | THY199 | - | Jun 28, 13:29 UTC | Jun 29, 00:49 UTC | 11h 20m |
| 2026-06-28 | THY198 | - | Jun 28, 00:04 UTC | Jun 28, 10:39 UTC | 10h 35m |
| 2026-06-27 | THY10 | LAX → IST | Jun 27, 03:40 UTC | Jun 27, 16:10 UTC | 12h 30m |
| 2026-06-26 | THY9 | IST → LAX | Jun 26, 11:55 UTC | Jun 27, 01:09 UTC | 13h 15m |
| 2026-06-26 | THY55 | SIN → IST | Jun 26, 01:39 UTC | Jun 26, 02:00 UTC | 20m |
| 2026-06-25 | THY55 | SIN → IST | Jun 25, 15:34 UTC | Jun 26, 01:05 UTC | 9h 30m |
| 2026-06-24 | THY54 | - | Jun 24, 23:29 UTC | Jun 25, 06:40 UTC | 7h 10m |
| 2026-06-24 | THY9WR | - | Jun 24, 18:05 UTC | Jun 24, 20:54 UTC | 2h 50m |
| 2026-06-24 | THY1PA | IST → CDG | Jun 24, 12:54 UTC | Jun 24, 15:44 UTC | 2h 50m |
| 2026-06-23 | THY73 | - | Jun 23, 15:59 UTC | Jun 23, 20:44 UTC | 4h 45m |
| 2026-06-22 | THY72 | IST → CAN | Jun 22, 22:44 UTC | Jun 23, 05:20 UTC | 6h 35m |
| 2026-06-22 | THY3AX | - | Jun 22, 19:19 UTC | Jun 22, 20:14 UTC | 55m |
| 2026-06-22 | THY2XQ | - | Jun 22, 16:20 UTC | Jun 22, 17:15 UTC | 55m |
| 2026-06-21 | THY41J | MIA → IST | Jun 21, 14:50 UTC | Jun 22, 01:00 UTC | 10h 10m |
| 2026-06-21 | THY4JD | - | Jun 21, 00:40 UTC | Jun 21, 11:55 UTC | 11h 15m |
| 2026-06-20 | THY4SD | - | Jun 20, 18:29 UTC | Jun 20, 21:30 UTC | 3h 0m |
| 2026-06-20 | THY2LD | - | Jun 20, 13:19 UTC | Jun 20, 16:39 UTC | 3h 20m |
| 2026-06-20 | THY71 | HKG → IST | Jun 20, 01:39 UTC | Jun 20, 02:00 UTC | 20m |
| 2026-06-19 | THY71 | HKG → IST | Jun 19, 15:44 UTC | Jun 20, 01:05 UTC | 9h 20m |
| 2026-06-19 | THY71 | HKG → IST | Jun 19, 14:59 UTC | Jun 19, 15:14 UTC | 15m |
| 2026-06-19 | THY70 | IST → HKG | Jun 19, 08:24 UTC | Jun 19, 08:44 UTC | 20m |
| 2026-06-19 | THY70 | IST → HKG | Jun 19, 00:10 UTC | Jun 19, 05:40 UTC | 5h 30m |
| 2026-06-18 | THY70 | IST → HKG | Jun 18, 22:50 UTC | Jun 18, 23:15 UTC | 25m |
| 2026-06-18 | THY10 | LAX → IST | Jun 18, 03:30 UTC | Jun 18, 15:55 UTC | 12h 25m |
| 2026-06-17 | THY9 | IST → LAX | Jun 17, 11:55 UTC | Jun 18, 00:55 UTC | 13h 0m |
| 2026-06-17 | THY199 | - | Jun 17, 00:50 UTC | Jun 17, 01:05 UTC | 15m |
| 2026-06-16 | THY199 | - | Jun 16, 12:55 UTC | Jun 17, 00:00 UTC | 11h 6m |
| 2026-06-15 | THY198 | - | Jun 15, 23:30 UTC | Jun 16, 10:15 UTC | 10h 45m |
| 2026-06-15 | THY89 | PEK → IST | Jun 15, 01:25 UTC | Jun 15, 01:45 UTC | 20m |
| 2026-06-14 | THY89 | PEK → IST | Jun 14, 23:35 UTC | Jun 15, 00:49 UTC | 1h 15m |
| 2026-06-14 | THY89 | PEK → IST | Jun 14, 00:20 UTC | Jun 15, 00:15 UTC | 23h 55m |
| 2026-06-13 | THY88 | IST → PEK | Jun 13, 23:00 UTC | Jun 14, 00:55 UTC | 1h 55m |
| 2026-06-13 | THY32G | - | Jun 13, 02:15 UTC | Jun 13, 12:15 UTC | 9h 59m |
| 2026-06-12 | THY31K | IST → ATL | Jun 12, 12:20 UTC | Jun 12, 23:35 UTC | 11h 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-LJI page for operator, model, and routing details .