sensors Mode-S transponder
4BD155
ICAO 24-bit transponder address · allocated to Turkey
Currently assigned to TC-TJU · BOEING 737-800
- Hex
- 4BD155
- Octal
- 22750525
- Decimal
- 4,968,789
- Country
- TR
- Tail
- TC-TJU
- Type
- B738
- Flights observed
- 114
- Distinct callsigns
- 20
- Country
- TR
- Last broadcast
- 52m ago
Current position
Country allocation
The ICAO 24-bit address 4BD155 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 |
|---|---|---|---|
| CXI79ZU | - | 17 | 2026-05-20 |
| CXI7A | - | 11 | 2026-05-20 |
| CXI2JY | Shanxi Airlines | 9 | 2026-05-23 |
| CXI5K | - | 8 | 2026-05-13 |
| CXI74WY | Shanxi Airlines | 7 | 2026-05-29 |
| CXI38SB | Shanxi Airlines | 7 | 2026-05-19 |
| CXI97RE | Shanxi Airlines | 6 | 2026-05-21 |
| CXI6BK | Shanxi Airlines | 6 | 2026-05-26 |
| CXI62QA | Shanxi Airlines | 6 | 2026-05-26 |
| CXI57BX | Shanxi Airlines | 6 | 2026-05-25 |
| CXI43AD | Shanxi Airlines | 6 | 2026-05-21 |
| CXI74GY | Shanxi Airlines | 5 | 2026-05-19 |
| CXI7YH | Shanxi Airlines | 4 | 2026-05-28 |
| CXI6M | Shanxi Airlines | 3 | 2026-05-27 |
| CXI57RW | - | 3 | 2026-04-18 |
| CXI8M | Shanxi Airlines | 2 | 2026-05-28 |
| CXI64EA | Shanxi Airlines | 2 | 2026-04-26 |
| CXI27GP | Shanxi Airlines | 2 | 2026-05-24 |
| CXI97DR | - | 1 | 2026-04-12 |
| CXI65SR | Shanxi Airlines | 1 | 2026-05-16 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | CXI74WY | STR → HRG | May 29, 14:00 UTC | May 30, 05:15 UTC | 15h 15m |
| 2026-05-28 | CXI8M | STR → HRG | May 28, 19:25 UTC | May 29, 12:35 UTC | 17h 10m |
| 2026-05-28 | CXI7YH | HRG → STR | May 28, 08:45 UTC | May 28, 18:15 UTC | 9h 30m |
| 2026-05-27 | CXI57AU | LEJ → HRG | May 27, 19:55 UTC | May 28, 07:10 UTC | 11h 15m |
| 2026-05-27 | CXI6M | HAJ → TFS | May 27, 08:45 UTC | May 27, 18:20 UTC | 9h 35m |
| 2026-05-26 | CXI62QA | HAM → HRG | May 26, 18:55 UTC | May 27, 07:10 UTC | 12h 15m |
| 2026-05-26 | CXI6BK | HRG → HAM | May 26, 07:55 UTC | May 26, 17:44 UTC | 9h 50m |
| 2026-05-25 | CXI57BX | STR → HRG | May 25, 14:25 UTC | May 26, 06:34 UTC | 16h 9m |
| 2026-05-24 | CXI27GP | HRG → STR | May 24, 19:00 UTC | May 25, 13:15 UTC | 18h 15m |
| 2026-05-24 | CXI6BK | HRG → HAM | May 24, 07:50 UTC | May 24, 17:50 UTC | 10h 0m |
| 2026-05-23 | CXI2JY | HRG → VIE | May 23, 19:35 UTC | May 24, 06:35 UTC | 11h 0m |
| 2026-05-23 | CXI6M | HAJ → TFS | May 23, 08:45 UTC | May 23, 18:15 UTC | 9h 31m |
| 2026-05-22 | CXI74WY | STR → HRG | May 22, 14:20 UTC | May 23, 07:10 UTC | 16h 49m |
| 2026-05-21 | CXI43AD | HRG → STR | May 21, 19:30 UTC | May 22, 12:45 UTC | 17h 14m |
| 2026-05-21 | CXI97RE | VIE → HRG | May 21, 08:40 UTC | May 21, 18:10 UTC | 9h 30m |
| 2026-05-20 | CXI79ZU | - | May 20, 11:20 UTC | May 21, 07:10 UTC | 19h 50m |
| 2026-05-20 | CXI79ZU | - | May 20, 09:20 UTC | May 21, 07:10 UTC | 21h 50m |
| 2026-05-20 | CXI79ZU | LNZ → VIE | May 20, 08:45 UTC | May 21, 07:10 UTC | 22h 25m |
| 2026-05-20 | CXI7A | - | May 20, 04:00 UTC | May 20, 07:30 UTC | 3h 31m |
| 2026-05-19 | CXI7A | - | May 19, 09:20 UTC | May 20, 07:30 UTC | 22h 11m |
| 2026-05-19 | CXI38SB | VIE → HRG | May 19, 08:00 UTC | May 20, 07:15 UTC | 23h 16m |
| 2026-05-19 | CXI74GY | HRG → VIE | May 19, 03:00 UTC | May 19, 06:30 UTC | 3h 30m |
| 2026-05-17 | CXI62QA | HAM → HRG | May 17, 19:01 UTC | May 17, 22:55 UTC | 3h 55m |
| 2026-05-17 | CXI6BK | HRG → HAM | May 17, 07:45 UTC | May 17, 17:45 UTC | 10h 0m |
| 2026-05-16 | CXI65SR | LEJ → HRG | May 16, 19:40 UTC | May 17, 06:30 UTC | 10h 50m |
| 2026-05-16 | CXI6M | HAJ → TFS | May 16, 08:46 UTC | May 16, 18:25 UTC | 9h 40m |
| 2026-05-15 | CXI74WY | STR → HRG | May 15, 14:55 UTC | May 16, 07:31 UTC | 16h 36m |
| 2026-05-14 | CXI43AD | HRG → STR | May 14, 19:45 UTC | May 15, 13:15 UTC | 17h 30m |
| 2026-05-14 | CXI7YH | HRG → STR | May 14, 09:10 UTC | May 14, 18:35 UTC | 9h 25m |
| 2026-05-14 | CXI79ZU | - | May 14, 04:35 UTC | May 14, 07:20 UTC | 2h 45m |
| 2026-05-13 | CXI79ZU | - | May 13, 11:20 UTC | May 14, 07:20 UTC | 20h 0m |
| 2026-05-13 | CXI79ZU | - | May 13, 09:20 UTC | May 14, 07:20 UTC | 22h 0m |
| 2026-05-13 | CXI5K | - | May 13, 08:35 UTC | May 14, 07:15 UTC | 22h 40m |
| 2026-05-13 | CXI7A | - | May 13, 03:40 UTC | May 13, 07:25 UTC | 3h 45m |
| 2026-05-12 | CXI7A | - | May 12, 09:20 UTC | May 13, 07:25 UTC | 22h 5m |
| 2026-05-12 | CXI7A | - | May 12, 07:55 UTC | May 13, 07:15 UTC | 23h 20m |
| 2026-05-12 | CXI74GY | HRG → VIE | May 12, 03:05 UTC | May 12, 06:35 UTC | 3h 30m |
| 2026-05-10 | CXI62QA | HAM → HRG | May 10, 19:05 UTC | May 10, 23:05 UTC | 4h 0m |
| 2026-05-10 | CXI6BK | HRG → HAM | May 10, 13:40 UTC | May 10, 17:59 UTC | 4h 20m |
| 2026-05-09 | CXI5K | - | May 9, 08:40 UTC | May 9, 11:30 UTC | 2h 50m |
| 2026-05-08 | CXI62QA | HAM → HRG | May 8, 15:05 UTC | May 9, 07:25 UTC | 16h 20m |
| 2026-05-07 | CXI8M | STR → HRG | May 7, 20:15 UTC | May 8, 13:40 UTC | 17h 25m |
| 2026-05-07 | CXI7YH | HRG → STR | May 7, 08:40 UTC | May 7, 18:50 UTC | 10h 10m |
| 2026-05-07 | CXI79ZU | - | May 7, 04:20 UTC | May 7, 07:20 UTC | 3h 0m |
| 2026-05-06 | CXI79ZU | - | May 6, 11:20 UTC | May 7, 07:20 UTC | 19h 59m |
| 2026-05-06 | CXI79ZU | - | May 6, 09:20 UTC | May 7, 07:20 UTC | 21h 59m |
| 2026-05-06 | CXI5K | - | May 6, 08:45 UTC | May 7, 07:15 UTC | 22h 29m |
| 2026-05-06 | CXI7A | - | May 6, 05:00 UTC | May 6, 07:35 UTC | 2h 35m |
| 2026-05-05 | CXI7A | - | May 5, 09:20 UTC | May 6, 07:35 UTC | 22h 15m |
| 2026-05-05 | CXI38SB | VIE → HRG | May 5, 07:45 UTC | May 6, 07:15 UTC | 23h 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-TJU page for operator, model, and routing details .