sensors Mode-S transponder
4BBD07
ICAO 24-bit transponder address · allocated to Turkey
Currently assigned to TC-OHG · BOEING 737-800
- Hex
- 4BBD07
- Octal
- 22736407
- Decimal
- 4,963,591
- Country
- TR
- Tail
- TC-OHG
- Type
- B738
- Flights observed
- 149
- Distinct callsigns
- 20
- Country
- TR
- Last broadcast
- 6h ago
Last known position
Country allocation
The ICAO 24-bit address 4BBD07 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 |
|---|---|---|---|
| TKJ583 | Tarkim Havacilik | 25 | 2026-05-27 |
| TKJ584 | - | 14 | 2026-05-22 |
| TKJ9SC | - | 3 | 2026-04-14 |
| TKJ8UY | - | 3 | 2026-04-13 |
| TKJ7LT | - | 3 | 2026-05-27 |
| TKJ6UN | - | 3 | 2026-05-29 |
| TKJ3DV | - | 3 | 2026-05-28 |
| TKJ22D | - | 3 | 2026-05-29 |
| TKJ1KE | Tarkim Havacilik | 3 | 2026-04-13 |
| TKJ9ZV | Tarkim Havacilik | 2 | 2026-04-17 |
| TKJ9CK | Tarkim Havacilik | 2 | 2026-04-14 |
| TKJ8RE | Tarkim Havacilik | 2 | 2026-04-24 |
| TKJ80C | - | 2 | 2026-05-12 |
| TKJ6ZV | - | 2 | 2026-05-25 |
| TKJ6MD | Tarkim Havacilik | 2 | 2026-04-24 |
| TKJ6DS | - | 2 | 2026-04-18 |
| TKJ51T | Tarkim Havacilik | 2 | 2026-04-17 |
| TKJ4TK | Tarkim Havacilik | 2 | 2026-05-06 |
| TKJ4QU | - | 2 | 2026-04-16 |
| TKJ4BR | - | 2 | 2026-05-04 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | TKJ6UN | - | May 29, 15:30 UTC | May 29, 18:20 UTC | 2h 50m |
| 2026-05-29 | TKJ22D | - | May 29, 10:50 UTC | May 29, 14:05 UTC | 3h 15m |
| 2026-05-29 | TKJ5SA | AMS → ESB | May 29, 03:20 UTC | May 29, 08:55 UTC | 5h 35m |
| 2026-05-28 | TKJ7KE | BJV → SAW | May 28, 21:50 UTC | May 28, 22:20 UTC | 30m |
| 2026-05-28 | TKJ3DV | - | May 28, 15:40 UTC | May 28, 19:15 UTC | 3h 35m |
| 2026-05-27 | TKJ7LT | - | May 27, 21:40 UTC | May 28, 13:40 UTC | 16h 0m |
| 2026-05-27 | TKJ583 | ESB → TAS | May 27, 01:49 UTC | May 27, 22:40 UTC | 20h 51m |
| 2026-05-27 | TKJ583 | ESB → TAS | May 27, 01:39 UTC | May 27, 22:40 UTC | 21h 1m |
| 2026-05-26 | TKJ2QD | ESB → TZX | May 26, 21:49 UTC | May 26, 21:59 UTC | 10m |
| 2026-05-25 | TKJ2FN | - | May 25, 19:59 UTC | May 26, 12:10 UTC | 16h 10m |
| 2026-05-25 | TKJ6ZV | - | May 25, 18:25 UTC | May 25, 18:55 UTC | 30m |
| 2026-05-23 | TKJ583 | ESB → TAS | May 23, 17:50 UTC | May 24, 12:25 UTC | 18h 35m |
| 2026-05-23 | TKJ583 | ESB → TAS | May 23, 17:10 UTC | May 24, 12:25 UTC | 19h 15m |
| 2026-05-22 | TKJ584 | - | May 22, 21:50 UTC | May 23, 15:50 UTC | 17h 59m |
| 2026-05-22 | TKJ583 | ESB → TAS | May 22, 21:30 UTC | May 23, 15:50 UTC | 18h 19m |
| 2026-05-22 | TKJ583 | ESB → TAS | May 22, 15:55 UTC | May 23, 15:45 UTC | 23h 49m |
| 2026-05-22 | TKJ583 | ESB → TAS | May 22, 11:55 UTC | May 23, 10:10 UTC | 22h 15m |
| 2026-05-22 | TKJ583 | ESB → TAS | May 22, 09:50 UTC | May 23, 09:45 UTC | 23h 54m |
| 2026-05-22 | TKJ583 | ESB → TAS | May 22, 05:50 UTC | May 23, 05:40 UTC | 23h 49m |
| 2026-05-22 | TKJ584 | - | May 22, 04:55 UTC | May 22, 22:35 UTC | 17h 40m |
| 2026-05-21 | TKJ583 | ESB → TAS | May 21, 21:50 UTC | May 22, 21:45 UTC | 23h 55m |
| 2026-05-21 | TKJ583 | ESB → TAS | May 21, 11:50 UTC | May 22, 10:05 UTC | 22h 15m |
| 2026-05-21 | TKJ583 | ESB → TAS | May 21, 09:50 UTC | May 22, 09:45 UTC | 23h 55m |
| 2026-05-21 | TKJ583 | ESB → TAS | May 21, 09:40 UTC | May 22, 06:10 UTC | 20h 30m |
| 2026-05-21 | TKJ583 | ESB → TAS | May 21, 05:50 UTC | May 22, 05:45 UTC | 23h 55m |
| 2026-05-21 | TKJ583 | ESB → TAS | May 21, 04:50 UTC | May 21, 23:00 UTC | 18h 10m |
| 2026-05-20 | TKJ584 | - | May 20, 21:50 UTC | May 21, 21:45 UTC | 23h 55m |
| 2026-05-20 | TKJ583 | ESB → TAS | May 20, 21:25 UTC | May 21, 12:15 UTC | 14h 50m |
| 2026-05-20 | TKJ583 | ESB → TAS | May 20, 14:35 UTC | May 21, 11:40 UTC | 21h 5m |
| 2026-05-19 | TKJ6XU | - | May 19, 17:55 UTC | May 20, 14:35 UTC | 20h 41m |
| 2026-05-19 | TKJ79Q | - | May 19, 10:00 UTC | May 19, 16:45 UTC | 6h 45m |
| 2026-05-17 | TKJ6LF | - | May 17, 19:45 UTC | May 17, 20:01 UTC | 15m |
| 2026-05-17 | TKJ584 | - | May 17, 04:50 UTC | May 17, 18:45 UTC | 13h 55m |
| 2026-05-16 | TKJ584 | - | May 16, 21:50 UTC | May 17, 18:45 UTC | 20h 55m |
| 2026-05-16 | TKJ583 | ESB → TAS | May 16, 21:35 UTC | May 17, 18:45 UTC | 21h 10m |
| 2026-05-16 | TKJ583 | ESB → TAS | May 16, 12:05 UTC | May 17, 09:30 UTC | 21h 25m |
| 2026-05-16 | TKJ62X | TZX → ESB | May 16, 01:40 UTC | May 16, 02:05 UTC | 25m |
| 2026-05-15 | TKJ2QD | ESB → TZX | May 15, 11:50 UTC | May 15, 22:40 UTC | 10h 49m |
| 2026-05-14 | TKJ583 | ESB → TAS | May 14, 21:45 UTC | May 15, 10:10 UTC | 12h 25m |
| 2026-05-14 | TKJ583 | ESB → TAS | May 14, 10:50 UTC | May 15, 09:45 UTC | 22h 55m |
| 2026-05-14 | TKJ9NC | - | May 14, 09:20 UTC | May 14, 09:35 UTC | 15m |
| 2026-05-14 | TKJ7ZB | - | May 14, 01:50 UTC | May 14, 02:00 UTC | 10m |
| 2026-05-13 | TKJ5JC | ESB → AYT | May 13, 21:45 UTC | May 13, 22:00 UTC | 15m |
| 2026-05-12 | TKJ80C | - | May 12, 19:30 UTC | May 13, 14:55 UTC | 19h 25m |
| 2026-05-12 | TKJ80C | - | May 12, 17:20 UTC | May 13, 14:55 UTC | 21h 35m |
| 2026-05-12 | TKJ1NB | - | May 12, 12:20 UTC | May 12, 19:40 UTC | 7h 20m |
| 2026-05-12 | TKJ5VN | ESB → AYT | May 12, 10:35 UTC | May 12, 10:50 UTC | 15m |
| 2026-05-11 | TKJ2FN | - | May 11, 20:05 UTC | May 11, 20:25 UTC | 20m |
| 2026-05-11 | TKJ6ZV | - | May 11, 07:45 UTC | May 11, 18:55 UTC | 11h 10m |
| 2026-05-09 | TKJ584 | - | May 9, 21:45 UTC | May 10, 06:30 UTC | 8h 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-OHG page for operator, model, and routing details .