sensors Mode-S transponder
4BA8DA
ICAO 24-bit transponder address · allocated to Turkey
Currently assigned to TC-JFZ · BOEING 737-800
- Hex
- 4BA8DA
- Octal
- 22724332
- Decimal
- 4,958,426
- Country
- TR
- Tail
- TC-JFZ
- Type
- B738
- Flights observed
- 199
- Distinct callsigns
- 20
- Country
- TR
- Last broadcast
- 2d ago
Last known position
Country allocation
The ICAO 24-bit address 4BA8DA 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 |
|---|---|---|---|
| THY3032 | - | 8 | 2026-06-26 |
| TKJ13A | - | 5 | 2026-07-03 |
| THY3063 | - | 5 | 2026-06-27 |
| THY3033 | - | 5 | 2026-07-01 |
| TKJ8VB | Tarkim Havacilik | 4 | 2026-06-06 |
| TKJ5ED | Tarkim Havacilik | 4 | 2026-06-06 |
| TKJ3WS | Tarkim Havacilik | 4 | 2026-05-09 |
| TKJ9QF | Tarkim Havacilik | 3 | 2026-06-02 |
| TKJ7MK | - | 3 | 2026-07-11 |
| TKJ7AX | Tarkim Havacilik | 3 | 2026-04-16 |
| TKJ61W | - | 3 | 2026-07-11 |
| TKJ5KZ | Tarkim Havacilik | 3 | 2026-05-09 |
| TKJ5GL | Tarkim Havacilik | 3 | 2026-04-13 |
| TKJ35Z | Tarkim Havacilik | 3 | 2026-05-29 |
| TKJ2JY | Tarkim Havacilik | 3 | 2026-05-29 |
| TKJ214 | Tarkim Havacilik | 3 | 2026-05-09 |
| TKJ12T | - | 3 | 2026-04-13 |
| TKJ9YX | Tarkim Havacilik | 2 | 2026-05-31 |
| TKJ9ND | - | 2 | 2026-07-05 |
| TKJ8QP | - | 2 | 2026-04-18 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-11 | TKJ7MK | - | Jul 11, 17:35 UTC | Jul 11, 18:40 UTC | 1h 5m |
| 2026-07-11 | TKJ61W | - | Jul 11, 07:40 UTC | Jul 11, 15:55 UTC | 8h 15m |
| 2026-07-11 | TKJ6QZ | - | Jul 11, 05:20 UTC | Jul 11, 06:10 UTC | 50m |
| 2026-07-10 | TKJ2CZ | - | Jul 10, 16:35 UTC | Jul 10, 19:00 UTC | 2h 25m |
| 2026-07-10 | TKJ9UZ | - | Jul 10, 09:25 UTC | Jul 10, 15:00 UTC | 5h 35m |
| 2026-07-09 | TKJ5302 | - | Jul 9, 21:15 UTC | Jul 10, 08:10 UTC | 10h 55m |
| 2026-07-09 | TKJ6840 | - | Jul 9, 19:35 UTC | Jul 9, 20:10 UTC | 35m |
| 2026-07-09 | TKJ5TC | - | Jul 9, 09:10 UTC | Jul 9, 10:10 UTC | 1h 0m |
| 2026-07-09 | TKJ9CS | - | Jul 9, 03:25 UTC | Jul 9, 07:40 UTC | 4h 15m |
| 2026-07-08 | TKJ9DT | - | Jul 8, 08:15 UTC | Jul 8, 22:20 UTC | 14h 5m |
| 2026-07-08 | TKJ5381 | - | Jul 8, 00:40 UTC | Jul 8, 01:00 UTC | 20m |
| 2026-07-07 | TKJ5380 | - | Jul 7, 18:30 UTC | Jul 7, 22:05 UTC | 3h 35m |
| 2026-07-07 | TKJ5SE | - | Jul 7, 00:40 UTC | Jul 7, 02:10 UTC | 1h 30m |
| 2026-07-06 | TKJ35M | - | Jul 6, 21:55 UTC | Jul 6, 23:20 UTC | 1h 25m |
| 2026-07-06 | TKJ5XL | - | Jul 6, 15:40 UTC | Jul 6, 20:20 UTC | 4h 40m |
| 2026-07-06 | TKJ5KV | - | Jul 6, 13:55 UTC | Jul 6, 14:05 UTC | 10m |
| 2026-07-05 | TKJ9ND | - | Jul 5, 05:30 UTC | Jul 5, 06:05 UTC | 35m |
| 2026-07-04 | TKJ15E | - | Jul 4, 19:05 UTC | Jul 5, 04:30 UTC | 9h 25m |
| 2026-07-04 | TKJ2TA | - | Jul 4, 09:25 UTC | Jul 4, 17:25 UTC | 8h 0m |
| 2026-07-04 | TKJ1ZL | - | Jul 4, 02:05 UTC | Jul 4, 02:45 UTC | 40m |
| 2026-07-03 | TKJ4KW | - | Jul 3, 18:30 UTC | Jul 3, 22:55 UTC | 4h 25m |
| 2026-07-03 | TKJ13A | - | Jul 3, 16:40 UTC | Jul 3, 17:20 UTC | 40m |
| 2026-07-02 | TKJ13A | - | Jul 2, 21:35 UTC | Jul 3, 17:20 UTC | 19h 45m |
| 2026-07-01 | THY3033 | - | Jul 1, 19:10 UTC | Jul 2, 05:30 UTC | 10h 20m |
| 2026-06-29 | THY3033 | - | Jun 29, 19:09 UTC | Jun 30, 05:25 UTC | 10h 16m |
| 2026-06-28 | THY3033 | - | Jun 28, 19:09 UTC | Jun 29, 05:45 UTC | 10h 35m |
| 2026-06-27 | THY3063 | - | Jun 27, 19:19 UTC | Jun 28, 05:55 UTC | 10h 35m |
| 2026-06-26 | THY3032 | - | Jun 26, 19:04 UTC | Jun 27, 07:39 UTC | 12h 35m |
| 2026-06-25 | THY3032 | - | Jun 25, 19:05 UTC | Jun 26, 05:30 UTC | 10h 25m |
| 2026-06-24 | THY3032 | - | Jun 24, 19:20 UTC | Jun 24, 21:14 UTC | 1h 55m |
| 2026-06-24 | THY3063 | - | Jun 24, 05:09 UTC | Jun 24, 05:34 UTC | 25m |
| 2026-06-23 | THY3063 | - | Jun 23, 19:15 UTC | Jun 24, 04:24 UTC | 9h 10m |
| 2026-06-22 | THY3032 | - | Jun 22, 19:00 UTC | Jun 23, 05:34 UTC | 10h 35m |
| 2026-06-21 | THY3032 | - | Jun 21, 19:34 UTC | Jun 21, 21:24 UTC | 1h 50m |
| 2026-06-21 | THY3063 | - | Jun 21, 05:35 UTC | Jun 21, 05:59 UTC | 25m |
| 2026-06-20 | THY3062 | - | Jun 20, 19:09 UTC | Jun 20, 20:55 UTC | 1h 45m |
| 2026-06-20 | THY3033 | - | Jun 20, 06:35 UTC | Jun 20, 07:00 UTC | 25m |
| 2026-06-19 | THY3032 | - | Jun 19, 19:19 UTC | Jun 20, 05:49 UTC | 10h 30m |
| 2026-06-18 | THY3032 | - | Jun 18, 19:15 UTC | Jun 18, 21:00 UTC | 1h 45m |
| 2026-06-17 | THY3032 | - | Jun 17, 19:00 UTC | Jun 18, 05:40 UTC | 10h 40m |
| 2026-06-16 | THY3063 | - | Jun 16, 20:25 UTC | Jun 17, 06:40 UTC | 10h 15m |
| 2026-06-15 | THY3033 | - | Jun 15, 19:20 UTC | Jun 16, 05:50 UTC | 10h 30m |
| 2026-06-14 | TKJ5220 | - | Jun 14, 21:15 UTC | Jun 14, 22:05 UTC | 50m |
| 2026-06-14 | TKJ5ZF | - | Jun 14, 18:50 UTC | Jun 14, 19:40 UTC | 50m |
| 2026-06-14 | TKJ8UC | - | Jun 14, 17:05 UTC | Jun 14, 17:35 UTC | 30m |
| 2026-06-14 | TKJ1PR | - | Jun 14, 11:55 UTC | Jun 14, 15:00 UTC | 3h 5m |
| 2026-06-14 | TKJ8AT | SAW → SZF | Jun 14, 06:40 UTC | Jun 14, 09:45 UTC | 3h 5m |
| 2026-06-13 | TKJ9DB | - | Jun 13, 11:35 UTC | Jun 13, 17:15 UTC | 5h 40m |
| 2026-06-13 | TKJ1JF | - | Jun 13, 08:00 UTC | Jun 13, 08:40 UTC | 40m |
| 2026-06-13 | TKJ5UH | - | Jun 13, 06:10 UTC | Jun 13, 06:45 UTC | 35m |
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-JFZ page for operator, model, and routing details .