sensors Mode-S transponder
4BBD06
ICAO 24-bit transponder address · allocated to Turkey
Currently assigned to TC-OHF · BOEING 737 MAX 8
- Hex
- 4BBD06
- Octal
- 22736406
- Decimal
- 4,963,590
- Country
- TR
- Tail
- TC-OHF
- Type
- B38M
- Flights observed
- 142
- Distinct callsigns
- 20
- Country
- TR
- Last broadcast
- 1h ago
Current position
Country allocation
The ICAO 24-bit address 4BBD06 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 |
|---|---|---|---|
| TKJ4NB | - | 5 | 2026-05-16 |
| TKJ3MQ | - | 5 | 2026-05-16 |
| TKJ2GJ | Tarkim Havacilik | 4 | 2026-05-05 |
| TKJ8VB | Tarkim Havacilik | 3 | 2026-05-13 |
| TKJ5VN | Tarkim Havacilik | 3 | 2026-05-29 |
| TKJ5ED | Tarkim Havacilik | 3 | 2026-05-13 |
| TKJ3QR | Tarkim Havacilik | 3 | 2026-04-18 |
| TKJ39Y | Tarkim Havacilik | 3 | 2026-05-05 |
| TKJ1KN | Tarkim Havacilik | 3 | 2026-05-26 |
| TKJ9ZV | Tarkim Havacilik | 2 | 2026-05-17 |
| TKJ9DT | - | 2 | 2026-05-26 |
| TKJ8KJ | - | 2 | 2026-05-21 |
| TKJ7SW | Tarkim Havacilik | 2 | 2026-05-22 |
| TKJ6MP | Tarkim Havacilik | 2 | 2026-04-25 |
| TKJ6BL | Tarkim Havacilik | 2 | 2026-04-25 |
| TKJ610 | Tarkim Havacilik | 2 | 2026-05-19 |
| TKJ5LJ | Tarkim Havacilik | 2 | 2026-05-29 |
| TKJ5GL | Tarkim Havacilik | 2 | 2026-05-16 |
| TKJ582 | Tarkim Havacilik | 2 | 2026-05-23 |
| TKJ573 | Tarkim Havacilik | 2 | 2026-05-25 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-30 | TKJ47Y | ESB → BCN | May 30, 07:10 UTC | May 30, 07:30 UTC | 20m |
| 2026-05-29 | TKJ3KN | - | May 29, 18:50 UTC | May 29, 20:10 UTC | 1h 20m |
| 2026-05-29 | TKJ5LJ | AYT → ESB | May 29, 12:35 UTC | May 29, 16:15 UTC | 3h 40m |
| 2026-05-29 | TKJ5VN | ESB → AYT | May 29, 10:40 UTC | May 29, 11:00 UTC | 20m |
| 2026-05-28 | TKJ34Y | STR → ESB | May 28, 15:40 UTC | May 29, 07:35 UTC | 15h 55m |
| 2026-05-28 | TKJ6XW | ESB → STR | May 28, 06:55 UTC | May 28, 14:35 UTC | 7h 40m |
| 2026-05-28 | TKJ4DR | ESB → ERZ | May 28, 05:05 UTC | May 28, 05:20 UTC | 15m |
| 2026-05-27 | TKJ1ZP | DUS → ESB | May 27, 16:15 UTC | May 27, 18:55 UTC | 2h 40m |
| 2026-05-26 | TKJ1KN | ESB → DUS | May 26, 21:55 UTC | May 27, 14:40 UTC | 16h 45m |
| 2026-05-26 | TKJ1KN | ESB → DUS | May 26, 13:40 UTC | May 27, 13:30 UTC | 23h 51m |
| 2026-05-26 | TKJ9DT | - | May 26, 10:39 UTC | May 27, 07:30 UTC | 20h 51m |
| 2026-05-26 | TKJ9DT | - | May 26, 05:59 UTC | May 26, 22:29 UTC | 16h 30m |
| 2026-05-25 | TKJ573 | ESB → FRU | May 25, 21:24 UTC | May 26, 14:55 UTC | 17h 30m |
| 2026-05-25 | TKJ573 | ESB → FRU | May 25, 18:10 UTC | May 26, 14:55 UTC | 20h 44m |
| 2026-05-25 | TKJ3KN | - | May 25, 13:00 UTC | May 25, 16:35 UTC | 3h 35m |
| 2026-05-24 | TKJ572 | ALA → ESB | May 24, 17:35 UTC | May 25, 11:35 UTC | 18h 0m |
| 2026-05-24 | TKJ5LJ | AYT → ESB | May 24, 12:15 UTC | May 24, 16:00 UTC | 3h 45m |
| 2026-05-24 | TKJ5VN | ESB → AYT | May 24, 10:30 UTC | May 24, 10:45 UTC | 15m |
| 2026-05-24 | TKJ3BW | - | May 24, 07:55 UTC | May 24, 08:15 UTC | 20m |
| 2026-05-23 | TKJ6LN | - | May 23, 14:05 UTC | May 24, 06:45 UTC | 16h 40m |
| 2026-05-23 | TKJ582 | NQZ → ESB | May 23, 06:00 UTC | May 23, 17:40 UTC | 11h 40m |
| 2026-05-22 | TKJ582 | NQZ → ESB | May 22, 22:00 UTC | May 23, 17:40 UTC | 19h 39m |
| 2026-05-22 | TKJ7SW | SAW → EZS | May 22, 17:35 UTC | May 23, 14:05 UTC | 20h 29m |
| 2026-05-22 | TKJ7SW | SAW → EZS | May 22, 15:50 UTC | May 23, 14:05 UTC | 22h 15m |
| 2026-05-21 | TKJ8KJ | - | May 21, 21:25 UTC | May 22, 14:20 UTC | 16h 55m |
| 2026-05-21 | TKJ8KJ | - | May 21, 16:30 UTC | May 22, 14:20 UTC | 21h 50m |
| 2026-05-20 | TKJ568 | JRO → IST | May 20, 21:35 UTC | May 21, 15:00 UTC | 17h 25m |
| 2026-05-20 | TKJ568 | JRO → IST | May 20, 17:35 UTC | May 21, 15:00 UTC | 21h 25m |
| 2026-05-20 | TKJ1ZP | DUS → ESB | May 20, 16:15 UTC | May 21, 15:00 UTC | 22h 45m |
| 2026-05-19 | TKJ1KN | ESB → DUS | May 19, 21:20 UTC | May 20, 14:50 UTC | 17h 31m |
| 2026-05-19 | TKJ610 | JED → ESB | May 19, 01:35 UTC | May 19, 23:05 UTC | 21h 30m |
| 2026-05-18 | TKJ610 | JED → ESB | May 18, 19:55 UTC | May 19, 03:05 UTC | 7h 10m |
| 2026-05-18 | TKJ2JY | STR → SAW | May 18, 11:05 UTC | May 18, 13:10 UTC | 2h 5m |
| 2026-05-18 | TKJ35Z | AJI → ESB | May 18, 06:50 UTC | May 18, 09:15 UTC | 2h 25m |
| 2026-05-18 | TKJ5EF | SAW → BER | May 18, 03:05 UTC | May 18, 03:35 UTC | 30m |
| 2026-05-17 | TKJ5GR | SAW → PRN | May 17, 20:55 UTC | May 17, 21:10 UTC | 15m |
| 2026-05-17 | TKJ8JC | YEI → DIY | May 17, 15:40 UTC | May 17, 16:05 UTC | 25m |
| 2026-05-17 | TKJ21K | - | May 17, 10:35 UTC | May 17, 13:01 UTC | 2h 25m |
| 2026-05-17 | TKJ9ZV | ESB → CDG | May 17, 05:50 UTC | May 17, 08:45 UTC | 2h 55m |
| 2026-05-16 | TKJ3MQ | - | May 16, 21:45 UTC | May 17, 00:50 UTC | 3h 5m |
| 2026-05-16 | TKJ4NB | - | May 16, 16:45 UTC | May 16, 20:10 UTC | 3h 25m |
| 2026-05-16 | TKJ12T | SAW → BJV | May 16, 11:41 UTC | May 16, 13:55 UTC | 2h 15m |
| 2026-05-16 | TKJ5GL | SAW → GVA | May 16, 07:31 UTC | May 16, 10:16 UTC | 2h 45m |
| 2026-05-15 | TKJ1BP | - | May 15, 15:00 UTC | May 15, 17:05 UTC | 2h 5m |
| 2026-05-15 | TKJ4LQ | SAW → STR | May 15, 11:00 UTC | May 15, 13:35 UTC | 2h 35m |
| 2026-05-14 | TKJ1FZ | ECN → ESB | May 14, 12:15 UTC | May 14, 14:50 UTC | 2h 35m |
| 2026-05-13 | TKJ8VB | VIE → SAW | May 13, 11:40 UTC | May 13, 13:10 UTC | 1h 30m |
| 2026-05-13 | TKJ5ED | SAW → VIE | May 13, 07:35 UTC | May 13, 09:30 UTC | 1h 55m |
| 2026-05-12 | TKJ5898 | - | May 12, 03:10 UTC | May 12, 20:50 UTC | 17h 40m |
| 2026-05-11 | TKJ5897 | - | May 11, 20:00 UTC | May 12, 19:30 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-OHF page for operator, model, and routing details .