sensors Mode-S transponder
4BD062
ICAO 24-bit transponder address · allocated to Turkey
Currently assigned to TC-TCB · HAWKER BEECHCRAFT Hawker 750/850
- Hex
- 4BD062
- Octal
- 22750142
- Decimal
- 4,968,546
- Country
- TR
- Tail
- TC-TCB
- Type
- H25B
- Flights observed
- 77
- Distinct callsigns
- 1
- Country
- TR
- Last broadcast
- 58m ago
Last known position
Country allocation
The ICAO 24-bit address 4BD062 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 1 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| TCTCB | - | 77 | 2026-07-18 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-18 | TCTCB | - | Jul 18, 21:25 UTC | Jul 18, 22:05 UTC | 40m |
| 2026-07-18 | TCTCB | - | Jul 18, 19:40 UTC | Jul 18, 20:50 UTC | 1h 10m |
| 2026-07-17 | TCTCB | - | Jul 17, 13:05 UTC | Jul 17, 22:10 UTC | 9h 5m |
| 2026-07-15 | TCTCB | - | Jul 15, 16:20 UTC | Jul 15, 17:15 UTC | 55m |
| 2026-07-15 | TCTCB | - | Jul 15, 14:50 UTC | Jul 15, 15:35 UTC | 45m |
| 2026-07-15 | TCTCB | - | Jul 15, 12:05 UTC | Jul 15, 12:50 UTC | 45m |
| 2026-07-14 | TCTCB | - | Jul 14, 20:50 UTC | Jul 14, 23:00 UTC | 2h 9m |
| 2026-07-14 | TCTCB | - | Jul 14, 18:50 UTC | Jul 14, 19:35 UTC | 45m |
| 2026-07-12 | TCTCB | - | Jul 12, 14:25 UTC | Jul 12, 16:05 UTC | 1h 40m |
| 2026-07-12 | TCTCB | - | Jul 12, 12:10 UTC | Jul 12, 12:55 UTC | 45m |
| 2026-07-12 | TCTCB | - | Jul 12, 09:55 UTC | Jul 12, 11:15 UTC | 1h 20m |
| 2026-07-12 | TCTCB | - | Jul 12, 07:40 UTC | Jul 12, 09:20 UTC | 1h 40m |
| 2026-07-11 | TCTCB | - | Jul 11, 15:00 UTC | Jul 11, 15:45 UTC | 45m |
| 2026-07-11 | TCTCB | - | Jul 11, 12:20 UTC | Jul 11, 13:10 UTC | 50m |
| 2026-07-11 | TCTCB | - | Jul 11, 08:45 UTC | Jul 11, 09:45 UTC | 1h 0m |
| 2026-07-10 | TCTCB | - | Jul 10, 12:10 UTC | Jul 10, 14:40 UTC | 2h 30m |
| 2026-07-09 | TCTCB | - | Jul 9, 08:10 UTC | Jul 9, 10:55 UTC | 2h 45m |
| 2026-07-07 | TCTCB | - | Jul 7, 13:55 UTC | Jul 7, 16:15 UTC | 2h 20m |
| 2026-07-07 | TCTCB | - | Jul 7, 10:15 UTC | Jul 7, 12:55 UTC | 2h 40m |
| 2026-07-06 | TCTCB | - | Jul 6, 14:10 UTC | Jul 6, 14:45 UTC | 35m |
| 2026-07-06 | TCTCB | - | Jul 6, 08:20 UTC | Jul 6, 08:45 UTC | 25m |
| 2026-07-03 | TCTCB | - | Jul 3, 09:30 UTC | Jul 3, 13:00 UTC | 3h 30m |
| 2026-07-03 | TCTCB | - | Jul 3, 04:30 UTC | Jul 3, 08:15 UTC | 3h 45m |
| 2026-07-01 | TCTCB | - | Jul 1, 16:45 UTC | Jul 1, 17:35 UTC | 50m |
| 2026-07-01 | TCTCB | - | Jul 1, 14:10 UTC | Jul 1, 14:25 UTC | 15m |
| 2026-07-01 | TCTCB | - | Jul 1, 12:45 UTC | Jul 1, 13:30 UTC | 45m |
| 2026-06-30 | TCTCB | - | Jun 30, 10:00 UTC | Jun 30, 10:50 UTC | 50m |
| 2026-06-30 | TCTCB | - | Jun 30, 08:10 UTC | Jun 30, 08:50 UTC | 40m |
| 2026-06-30 | TCTCB | - | Jun 30, 06:05 UTC | Jun 30, 07:00 UTC | 55m |
| 2026-06-29 | TCTCB | - | Jun 29, 14:25 UTC | Jun 29, 15:19 UTC | 55m |
| 2026-06-29 | TCTCB | - | Jun 29, 11:45 UTC | Jun 29, 13:24 UTC | 1h 40m |
| 2026-06-29 | TCTCB | - | Jun 29, 07:50 UTC | Jun 29, 08:54 UTC | 1h 5m |
| 2026-06-27 | TCTCB | - | Jun 27, 10:14 UTC | Jun 27, 10:50 UTC | 35m |
| 2026-06-27 | TCTCB | - | Jun 27, 08:39 UTC | Jun 27, 09:04 UTC | 25m |
| 2026-06-26 | TCTCB | - | Jun 26, 11:00 UTC | Jun 26, 13:30 UTC | 2h 30m |
| 2026-06-26 | TCTCB | - | Jun 26, 06:39 UTC | Jun 26, 08:50 UTC | 2h 10m |
| 2026-06-25 | TCTCB | - | Jun 25, 02:14 UTC | Jun 25, 04:14 UTC | 2h 0m |
| 2026-06-20 | TCTCB | - | Jun 20, 13:39 UTC | Jun 20, 21:40 UTC | 8h 0m |
| 2026-06-20 | TCTCB | - | Jun 20, 11:49 UTC | Jun 20, 11:59 UTC | 10m |
| 2026-06-16 | TCTCB | - | Jun 16, 19:10 UTC | Jun 16, 19:30 UTC | 20m |
| 2026-06-06 | TCTCB | - | Jun 6, 09:45 UTC | Jun 6, 10:09 UTC | 25m |
| 2026-06-06 | TCTCB | - | Jun 6, 06:00 UTC | Jun 6, 06:20 UTC | 20m |
| 2026-05-18 | TCTCB | - | May 18, 14:50 UTC | May 18, 16:30 UTC | 1h 40m |
| 2026-05-15 | TCTCB | - | May 15, 08:45 UTC | May 15, 22:00 UTC | 13h 14m |
| 2026-05-11 | TCTCB | - | May 11, 18:50 UTC | May 11, 19:35 UTC | 45m |
| 2026-05-11 | TCTCB | - | May 11, 18:10 UTC | May 11, 18:20 UTC | 10m |
| 2026-05-11 | TCTCB | - | May 11, 16:40 UTC | May 11, 17:00 UTC | 21m |
| 2026-05-11 | TCTCB | - | May 11, 12:45 UTC | May 11, 13:35 UTC | 50m |
| 2026-05-09 | TCTCB | - | May 9, 15:25 UTC | May 9, 16:10 UTC | 45m |
| 2026-05-09 | TCTCB | - | May 9, 14:30 UTC | May 9, 14:50 UTC | 20m |
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-TCB page for operator, model, and routing details .