sensors Mode-S transponder
4BA8D2
ICAO 24-bit transponder address · allocated to Turkey
Currently assigned to TC-JFR · BOEING 737-800
- Hex
- 4BA8D2
- Octal
- 22724322
- Decimal
- 4,958,418
- Country
- TR
- Tail
- TC-JFR
- Type
- B738
- Flights observed
- 66
- Distinct callsigns
- 20
- Country
- TR
- Last broadcast
- 26d ago
Last known position
Country allocation
The ICAO 24-bit address 4BA8D2 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 |
|---|---|---|---|
| TKJ8NZ | - | 2 | 2026-04-17 |
| TKJ7AJ | Tarkim Havacilik | 2 | 2026-04-28 |
| TKJ7AD | Tarkim Havacilik | 2 | 2026-04-29 |
| TKJ6UK | - | 2 | 2026-04-16 |
| TKJ6QY | - | 2 | 2026-04-15 |
| TKJ5NE | - | 2 | 2026-04-28 |
| TKJ4EZ | Tarkim Havacilik | 2 | 2026-05-03 |
| TKJ2AZ | - | 2 | 2026-04-16 |
| TKJ214 | Tarkim Havacilik | 2 | 2026-04-18 |
| TKJ213 | Tarkim Havacilik | 2 | 2026-04-17 |
| TKJ1DJ | Tarkim Havacilik | 2 | 2026-05-03 |
| TKJ9ZE | Tarkim Havacilik | 1 | 2026-05-03 |
| TKJ9RL | Tarkim Havacilik | 1 | 2026-04-26 |
| TKJ9QF | Tarkim Havacilik | 1 | 2026-04-29 |
| TKJ9DT | - | 1 | 2026-04-16 |
| TKJ8XR | Tarkim Havacilik | 1 | 2026-04-20 |
| TKJ8VB | Tarkim Havacilik | 1 | 2026-04-23 |
| TKJ8JC | Tarkim Havacilik | 1 | 2026-04-27 |
| TKJ8HW | Tarkim Havacilik | 1 | 2026-04-30 |
| TKJ7ZJ | - | 1 | 2026-04-20 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-03 | TKJ4EZ | ADB → SAW | May 3, 16:50 UTC | May 3, 17:20 UTC | 30m |
| 2026-05-03 | TKJ1DJ | ESB → AJI | May 3, 15:10 UTC | May 3, 15:30 UTC | 20m |
| 2026-05-03 | TKJ9ZE | MUC → SAW | May 3, 11:15 UTC | May 3, 13:10 UTC | 1h 55m |
| 2026-05-02 | TKJ7UN | SAW → MUC | May 2, 18:55 UTC | May 3, 09:50 UTC | 14h 54m |
| 2026-05-02 | TKJ5KZ | SAW → BGY | May 2, 11:10 UTC | May 2, 13:35 UTC | 2h 25m |
| 2026-05-02 | TKJ3WS | ESB → CDG | May 2, 06:45 UTC | May 2, 09:20 UTC | 2h 35m |
| 2026-05-01 | TKJ2FM | - | May 1, 12:30 UTC | May 1, 13:10 UTC | 40m |
| 2026-05-01 | TKJ1QC | SAW → SKP | May 1, 10:15 UTC | May 1, 11:05 UTC | 50m |
| 2026-04-30 | TKJ8HW | ECN → SAW | Apr 30, 17:00 UTC | Apr 30, 17:45 UTC | 45m |
| 2026-04-30 | TKJ11V | ESB → SAW | Apr 30, 14:15 UTC | Apr 30, 15:05 UTC | 50m |
| 2026-04-29 | TKJ6RK | - | Apr 29, 20:55 UTC | Apr 29, 21:05 UTC | 10m |
| 2026-04-29 | TKJ7AD | TZX → SAW | Apr 29, 08:40 UTC | Apr 29, 19:35 UTC | 10h 56m |
| 2026-04-29 | TKJ9QF | SAW → TZX | Apr 29, 07:15 UTC | Apr 29, 07:35 UTC | 20m |
| 2026-04-28 | TKJ7AJ | KSY → ESB | Apr 28, 11:20 UTC | Apr 28, 11:30 UTC | 10m |
| 2026-04-28 | TKJ5NE | - | Apr 28, 09:50 UTC | Apr 28, 10:15 UTC | 25m |
| 2026-04-27 | TKJ7KQ | - | Apr 27, 16:00 UTC | Apr 27, 16:30 UTC | 30m |
| 2026-04-27 | TKJ8JC | YEI → DIY | Apr 27, 14:40 UTC | Apr 27, 14:55 UTC | 15m |
| 2026-04-26 | TKJ9RL | TZX → SAW | Apr 26, 19:10 UTC | Apr 27, 07:20 UTC | 12h 10m |
| 2026-04-26 | TKJ7AJ | KSY → ESB | Apr 26, 11:10 UTC | Apr 26, 11:30 UTC | 20m |
| 2026-04-26 | TKJ5NE | - | Apr 26, 09:20 UTC | Apr 26, 09:40 UTC | 20m |
| 2026-04-26 | TKJ3AG | SAW → SSH | Apr 26, 06:30 UTC | Apr 26, 06:45 UTC | 15m |
| 2026-04-26 | TKJ2DZ | SAW → BEG | Apr 26, 04:40 UTC | Apr 26, 05:15 UTC | 35m |
| 2026-04-24 | TKJ5MR | TBS → SAW | Apr 24, 11:40 UTC | Apr 24, 12:15 UTC | 35m |
| 2026-04-24 | TKJ68A | SAW → TZX | Apr 24, 10:15 UTC | Apr 24, 10:30 UTC | 15m |
| 2026-04-23 | TKJ8VB | VIE → SAW | Apr 23, 10:50 UTC | Apr 23, 12:40 UTC | 1h 50m |
| 2026-04-23 | TKJ5ED | SAW → VIE | Apr 23, 03:05 UTC | Apr 23, 09:30 UTC | 6h 26m |
| 2026-04-22 | TKJ50X | PRN → SAW | Apr 22, 23:15 UTC | Apr 22, 23:30 UTC | 15m |
| 2026-04-22 | TKJ4EZ | ADB → SAW | Apr 22, 16:05 UTC | Apr 22, 16:30 UTC | 25m |
| 2026-04-22 | TKJ1DJ | ESB → AJI | Apr 22, 14:15 UTC | Apr 22, 14:50 UTC | 35m |
| 2026-04-21 | TKJ7AD | TZX → SAW | Apr 21, 09:50 UTC | Apr 21, 15:55 UTC | 6h 5m |
| 2026-04-20 | TKJ2RY | - | Apr 20, 16:15 UTC | Apr 20, 17:45 UTC | 1h 30m |
| 2026-04-20 | TKJ8XR | ESB → STR | Apr 20, 13:10 UTC | Apr 20, 14:55 UTC | 1h 45m |
| 2026-04-20 | TKJ7ZJ | - | Apr 20, 06:45 UTC | Apr 20, 07:25 UTC | 40m |
| 2026-04-19 | TKJ6841 | - | Apr 19, 17:40 UTC | Apr 19, 17:50 UTC | 10m |
| 2026-04-19 | TKJ6840 | - | Apr 19, 16:05 UTC | Apr 19, 16:25 UTC | 20m |
| 2026-04-19 | TKJ20Q | - | Apr 19, 10:50 UTC | Apr 19, 12:50 UTC | 2h 0m |
| 2026-04-19 | TKJ3LB | ADB → ESB | Apr 19, 07:20 UTC | Apr 19, 09:40 UTC | 2h 20m |
| 2026-04-18 | TKJ214 | RUH → SAW | Apr 18, 07:25 UTC | Apr 18, 08:00 UTC | 35m |
| 2026-04-18 | TKJ214 | RUH → SAW | Apr 18, 06:50 UTC | Apr 18, 07:20 UTC | 30m |
| 2026-04-17 | TKJ213 | SAW → RUH | Apr 17, 23:25 UTC | Apr 18, 00:15 UTC | 50m |
| 2026-04-17 | TKJ213 | SAW → RUH | Apr 17, 22:45 UTC | Apr 18, 13:50 UTC | 15h 5m |
| 2026-04-17 | TKJ8NZ | - | Apr 17, 11:20 UTC | Apr 17, 11:30 UTC | 10m |
| 2026-04-17 | TKJ8NZ | - | Apr 17, 10:55 UTC | Apr 17, 11:15 UTC | 20m |
| 2026-04-17 | TKJ1PQ | - | Apr 17, 09:25 UTC | Apr 17, 09:50 UTC | 25m |
| 2026-04-16 | TKJ4BJ | - | Apr 16, 18:10 UTC | Apr 16, 18:55 UTC | 45m |
| 2026-04-16 | TKJ13A | - | Apr 16, 16:30 UTC | Apr 16, 17:05 UTC | 35m |
| 2026-04-16 | TKJ9DT | - | Apr 16, 13:15 UTC | Apr 16, 14:35 UTC | 1h 20m |
| 2026-04-16 | TKJ2YS | - | Apr 16, 09:54 UTC | Apr 16, 11:04 UTC | 1h 10m |
| 2026-04-16 | TKJ2AZ | - | Apr 16, 07:09 UTC | Apr 16, 07:29 UTC | 20m |
| 2026-04-16 | TKJ6UK | - | Apr 16, 05:24 UTC | Apr 16, 05:49 UTC | 25m |
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-JFR page for operator, model, and routing details .