sensors Mode-S transponder
4BA8F3
ICAO 24-bit transponder address · allocated to Turkey
Currently assigned to TC-JGS · BOEING 737-800
- Hex
- 4BA8F3
- Octal
- 22724363
- Decimal
- 4,958,451
- Country
- TR
- Tail
- TC-JGS
- Type
- B738
- Flights observed
- 273
- Distinct callsigns
- 20
- Country
- TR
- Last broadcast
- Jul 26, 22:45 UTC
Last known position
Country allocation
The ICAO 24-bit address 4BA8F3 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 |
|---|---|---|---|
| TKJ5MR | Tarkim Havacilik | 6 | 2026-05-27 |
| THY3120 | Turkish Airlines | 6 | 2026-07-26 |
| THY3032 | Turkish Airlines | 6 | 2026-07-20 |
| TKJ68A | Tarkim Havacilik | 5 | 2026-05-27 |
| TKJ214 | Tarkim Havacilik | 5 | 2026-04-15 |
| THY3033 | Turkish Airlines | 5 | 2026-07-24 |
| TKJ93J | - | 4 | 2026-06-27 |
| TKJ8UC | - | 4 | 2026-05-28 |
| TKJ5ZF | - | 4 | 2026-05-28 |
| TKJ4LQ | Tarkim Havacilik | 4 | 2026-05-31 |
| TKJ30H | Tarkim Havacilik | 4 | 2026-04-13 |
| TKJ213 | Tarkim Havacilik | 4 | 2026-04-14 |
| THY3068 | Turkish Airlines | 4 | 2026-07-26 |
| TKJ97R | - | 3 | 2026-06-26 |
| TKJ8NZ | - | 3 | 2026-05-30 |
| TKJ6YR | - | 3 | 2026-06-30 |
| TKJ6WM | - | 3 | 2026-04-13 |
| TKJ6QY | - | 3 | 2026-06-22 |
| TKJ5EY | - | 3 | 2026-06-22 |
| TKJ24R | - | 3 | 2026-06-22 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | THY3120 | AYT → CGN | Jul 26, 14:35 UTC | Jul 26, 22:45 UTC | 8h 10m |
| 2026-07-26 | THY3068 | DLM → LED | Jul 26, 01:00 UTC | Jul 26, 09:50 UTC | 8h 51m |
| 2026-07-25 | THY3120 | AYT → CGN | Jul 25, 14:00 UTC | Jul 25, 23:40 UTC | 9h 40m |
| 2026-07-25 | THY6978 | - | Jul 25, 12:00 UTC | Jul 25, 12:20 UTC | 20m |
| 2026-07-24 | THY3033 | RIX → AYT | Jul 24, 20:30 UTC | Jul 25, 10:25 UTC | 13h 55m |
| 2026-07-23 | THY3033 | RIX → AYT | Jul 23, 20:10 UTC | Jul 24, 06:20 UTC | 10h 10m |
| 2026-07-22 | THY3033 | RIX → AYT | Jul 22, 19:55 UTC | Jul 23, 11:35 UTC | 15h 40m |
| 2026-07-21 | THY3062 | BTZ → GLA | Jul 21, 19:40 UTC | Jul 22, 05:25 UTC | 9h 45m |
| 2026-07-20 | THY3032 | AYT → RIX | Jul 20, 19:45 UTC | Jul 21, 06:55 UTC | 11h 9m |
| 2026-07-19 | THY3032 | - | Jul 19, 19:50 UTC | Jul 19, 21:45 UTC | 1h 55m |
| 2026-07-18 | THY3062 | - | Jul 18, 20:20 UTC | Jul 18, 22:10 UTC | 1h 50m |
| 2026-07-18 | THY3098 | AYT → HAM | Jul 18, 08:20 UTC | Jul 18, 09:35 UTC | 1h 15m |
| 2026-07-17 | THY6961 | SAW → IST | Jul 17, 23:45 UTC | Jul 18, 00:29 UTC | 45m |
| 2026-07-17 | TKJ5043 | - | Jul 17, 15:35 UTC | Jul 17, 18:05 UTC | 2h 30m |
| 2026-07-17 | TKJ5042 | - | Jul 17, 10:00 UTC | Jul 17, 12:55 UTC | 2h 55m |
| 2026-07-17 | TKJ9YV | - | Jul 17, 05:04 UTC | Jul 17, 07:50 UTC | 2h 45m |
| 2026-07-16 | TKJ5227 | - | Jul 16, 21:45 UTC | Jul 16, 22:25 UTC | 40m |
| 2026-07-15 | THY3068 | - | Jul 15, 18:05 UTC | Jul 16, 02:50 UTC | 8h 45m |
| 2026-07-14 | THY3120 | - | Jul 14, 19:45 UTC | Jul 15, 05:10 UTC | 9h 24m |
| 2026-07-14 | THY3124 | - | Jul 14, 07:10 UTC | Jul 14, 17:55 UTC | 10h 45m |
| 2026-07-12 | THY3120 | - | Jul 12, 14:30 UTC | Jul 12, 17:45 UTC | 3h 15m |
| 2026-07-11 | THY3068 | - | Jul 11, 18:00 UTC | Jul 11, 20:05 UTC | 2h 5m |
| 2026-07-11 | THY3124 | - | Jul 11, 04:25 UTC | Jul 11, 06:25 UTC | 2h 0m |
| 2026-07-10 | THY3120 | - | Jul 10, 14:40 UTC | Jul 11, 00:10 UTC | 9h 30m |
| 2026-07-08 | THY3068 | - | Jul 8, 17:50 UTC | Jul 9, 02:50 UTC | 9h 0m |
| 2026-07-07 | THY3120 | - | Jul 7, 20:05 UTC | Jul 8, 06:15 UTC | 10h 10m |
| 2026-07-07 | THY3124 | - | Jul 7, 07:05 UTC | Jul 7, 10:30 UTC | 3h 25m |
| 2026-07-06 | TKJ5289 | - | Jul 6, 17:30 UTC | Jul 6, 21:15 UTC | 3h 45m |
| 2026-07-06 | THY3033 | - | Jul 6, 11:00 UTC | Jul 6, 11:20 UTC | 20m |
| 2026-07-05 | THY3032 | - | Jul 5, 19:10 UTC | Jul 6, 10:15 UTC | 15h 5m |
| 2026-07-04 | THY3062 | - | Jul 4, 19:25 UTC | Jul 4, 21:20 UTC | 1h 55m |
| 2026-07-04 | THY3033 | - | Jul 4, 16:25 UTC | Jul 4, 16:45 UTC | 20m |
| 2026-07-04 | THY3032 | - | Jul 4, 07:00 UTC | Jul 4, 12:05 UTC | 5h 5m |
| 2026-07-03 | THY3032 | - | Jul 3, 19:10 UTC | Jul 3, 21:00 UTC | 1h 50m |
| 2026-07-02 | THY3032 | - | Jul 2, 18:50 UTC | Jul 3, 05:35 UTC | 10h 45m |
| 2026-07-01 | TKJ5232 | - | Jul 1, 07:30 UTC | Jul 1, 08:35 UTC | 1h 5m |
| 2026-06-30 | TKJ9DB | - | Jun 30, 15:35 UTC | Jun 30, 17:25 UTC | 1h 50m |
| 2026-06-30 | TKJ6YR | - | Jun 30, 11:45 UTC | Jun 30, 13:35 UTC | 1h 50m |
| 2026-06-30 | TKJ5BQ | NKT → SAW | Jun 30, 05:15 UTC | Jun 30, 10:00 UTC | 4h 45m |
| 2026-06-29 | TKJ90U | - | Jun 29, 10:34 UTC | Jun 29, 13:09 UTC | 2h 35m |
| 2026-06-29 | TKJ51D | - | Jun 29, 06:09 UTC | Jun 29, 08:44 UTC | 2h 35m |
| 2026-06-29 | TKJ3XP | - | Jun 29, 01:29 UTC | Jun 29, 02:05 UTC | 35m |
| 2026-06-28 | TKJ6YL | - | Jun 28, 21:45 UTC | Jun 28, 22:20 UTC | 35m |
| 2026-06-28 | TKJ4SG | - | Jun 28, 16:14 UTC | Jun 28, 18:55 UTC | 2h 40m |
| 2026-06-28 | TKJ2ER | - | Jun 28, 09:15 UTC | Jun 28, 14:25 UTC | 5h 10m |
| 2026-06-28 | TKJ5NK | - | Jun 28, 07:14 UTC | Jun 28, 07:50 UTC | 35m |
| 2026-06-28 | TKJ4HD | - | Jun 28, 00:15 UTC | Jun 28, 03:05 UTC | 2h 50m |
| 2026-06-27 | TKJ4EP | - | Jun 27, 10:14 UTC | Jun 27, 22:29 UTC | 12h 15m |
| 2026-06-27 | TKJ93J | - | Jun 27, 07:19 UTC | Jun 27, 08:10 UTC | 50m |
| 2026-06-27 | TKJ1TP | - | Jun 27, 05:39 UTC | Jun 27, 06:19 UTC | 40m |
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-JGS page for operator, model, and routing details .