sensors Mode-S transponder
4BA9C2
ICAO 24-bit transponder address · allocated to Turkey
Currently assigned to TC-JNB · AIRBUS A-330-200
- Hex
- 4BA9C2
- Octal
- 22724702
- Decimal
- 4,958,658
- Country
- TR
- Tail
- TC-JNB
- Type
- A332
- Flights observed
- 232
- Distinct callsigns
- 20
- Country
- TR
- Last broadcast
- 1h ago
Last known position
Country allocation
The ICAO 24-bit address 4BA9C2 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 |
|---|---|---|---|
| THY707 | - | 17 | 2026-06-20 |
| THY8DP | Turkish Airlines | 9 | 2026-06-29 |
| THY7AU | - | 9 | 2026-06-29 |
| THY571 | Turkish Airlines | 8 | 2026-04-20 |
| THY37R | Turkish Airlines | 7 | 2026-06-26 |
| THY2DJ | Turkish Airlines | 7 | 2026-05-01 |
| THY8DL | Turkish Airlines | 6 | 2026-05-27 |
| THY67F | - | 5 | 2026-06-22 |
| THY5TP | - | 5 | 2026-06-15 |
| THY5AR | Turkish Airlines | 5 | 2026-06-15 |
| THY577 | - | 5 | 2026-07-01 |
| THY369 | - | 5 | 2026-07-13 |
| THY8LG | - | 4 | 2026-06-16 |
| THY706 | - | 4 | 2026-06-18 |
| THY1QG | - | 4 | 2026-07-02 |
| THY9QA | Turkish Airlines | 3 | 2026-06-20 |
| THY8WM | - | 3 | 2026-06-25 |
| THY7KT | Turkish Airlines | 3 | 2026-04-16 |
| THY6MG | - | 3 | 2026-07-13 |
| THY6EN | - | 3 | 2026-06-27 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | THY3ME | - | Jul 14, 10:50 UTC | Jul 14, 13:10 UTC | 2h 20m |
| 2026-07-14 | THY1SW | - | Jul 14, 01:35 UTC | Jul 14, 02:00 UTC | 25m |
| 2026-07-13 | THY6MG | - | Jul 13, 18:00 UTC | Jul 13, 20:20 UTC | 2h 20m |
| 2026-07-13 | THY3NV | - | Jul 13, 12:45 UTC | Jul 13, 15:25 UTC | 2h 40m |
| 2026-07-13 | THY369 | - | Jul 13, 09:00 UTC | Jul 13, 09:25 UTC | 25m |
| 2026-07-12 | THY369 | - | Jul 12, 22:40 UTC | Jul 13, 08:20 UTC | 9h 40m |
| 2026-07-12 | THY5NX | - | Jul 12, 18:20 UTC | Jul 12, 20:15 UTC | 1h 55m |
| 2026-07-12 | THY3ED | - | Jul 12, 14:25 UTC | Jul 12, 16:40 UTC | 2h 15m |
| 2026-07-12 | THY6884 | - | Jul 12, 09:20 UTC | Jul 12, 12:01 UTC | 2h 40m |
| 2026-07-02 | THY1QG | - | Jul 2, 04:30 UTC | Jul 2, 07:25 UTC | 2h 55m |
| 2026-07-01 | THY577 | - | Jul 1, 15:50 UTC | Jul 2, 01:45 UTC | 9h 55m |
| 2026-07-01 | THY7WF | - | Jul 1, 09:50 UTC | Jul 1, 12:55 UTC | 3h 5m |
| 2026-07-01 | THY7RS | - | Jul 1, 05:05 UTC | Jul 1, 07:50 UTC | 2h 45m |
| 2026-06-30 | THY577 | - | Jun 30, 16:25 UTC | Jul 1, 02:20 UTC | 9h 55m |
| 2026-06-30 | THY4RG | - | Jun 30, 08:55 UTC | Jun 30, 11:45 UTC | 2h 50m |
| 2026-06-30 | THY6FX | - | Jun 30, 04:25 UTC | Jun 30, 07:05 UTC | 2h 40m |
| 2026-06-29 | THY8DP | STR → VKO | Jun 29, 17:19 UTC | Jun 29, 20:19 UTC | 3h 0m |
| 2026-06-29 | THY7AU | - | Jun 29, 12:29 UTC | Jun 29, 15:19 UTC | 2h 50m |
| 2026-06-29 | THY369 | - | Jun 29, 09:20 UTC | Jun 29, 09:44 UTC | 25m |
| 2026-06-28 | THY368 | - | Jun 28, 22:45 UTC | Jun 29, 08:39 UTC | 9h 55m |
| 2026-06-28 | THY5NX | - | Jun 28, 18:19 UTC | Jun 28, 20:25 UTC | 2h 5m |
| 2026-06-28 | THY3ED | DUB → IST | Jun 28, 14:45 UTC | Jun 28, 16:45 UTC | 2h 0m |
| 2026-06-28 | THY8RF | - | Jun 28, 09:30 UTC | Jun 28, 12:50 UTC | 3h 20m |
| 2026-06-28 | THY8CX | - | Jun 28, 04:25 UTC | Jun 28, 07:34 UTC | 3h 10m |
| 2026-06-27 | THY347 | - | Jun 27, 14:09 UTC | Jun 28, 02:25 UTC | 12h 15m |
| 2026-06-27 | THY6EN | - | Jun 27, 09:00 UTC | Jun 27, 11:25 UTC | 2h 25m |
| 2026-06-27 | THY4VH | - | Jun 27, 04:54 UTC | Jun 27, 07:10 UTC | 2h 15m |
| 2026-06-26 | THY37R | IST → ABV | Jun 26, 12:29 UTC | Jun 27, 02:09 UTC | 13h 40m |
| 2026-06-26 | THY4AX | - | Jun 26, 06:29 UTC | Jun 26, 09:35 UTC | 3h 5m |
| 2026-06-25 | THY8WM | - | Jun 25, 16:59 UTC | Jun 25, 19:59 UTC | 3h 0m |
| 2026-06-25 | THY4RG | - | Jun 25, 09:50 UTC | Jun 25, 12:30 UTC | 2h 40m |
| 2026-06-25 | THY6FX | - | Jun 25, 04:14 UTC | Jun 25, 06:55 UTC | 2h 40m |
| 2026-06-24 | THY577 | - | Jun 24, 15:49 UTC | Jun 25, 01:59 UTC | 10h 10m |
| 2026-06-24 | THY8RF | - | Jun 24, 09:39 UTC | Jun 24, 12:50 UTC | 3h 10m |
| 2026-06-24 | THY8CX | - | Jun 24, 04:00 UTC | Jun 24, 07:10 UTC | 3h 10m |
| 2026-06-23 | THY577 | - | Jun 23, 16:09 UTC | Jun 24, 02:05 UTC | 9h 55m |
| 2026-06-23 | THY6EN | - | Jun 23, 10:49 UTC | Jun 23, 13:05 UTC | 2h 15m |
| 2026-06-23 | THY4VH | - | Jun 23, 06:44 UTC | Jun 23, 09:05 UTC | 2h 20m |
| 2026-06-22 | THY28J | - | Jun 22, 16:14 UTC | Jun 23, 04:09 UTC | 11h 55m |
| 2026-06-22 | THY67F | - | Jun 22, 09:49 UTC | Jun 22, 10:15 UTC | 25m |
| 2026-06-21 | THY67F | - | Jun 21, 22:20 UTC | Jun 22, 09:19 UTC | 11h 0m |
| 2026-06-21 | THY3EG | - | Jun 21, 17:24 UTC | Jun 21, 20:05 UTC | 2h 40m |
| 2026-06-21 | THY6MF | - | Jun 21, 12:44 UTC | Jun 21, 15:30 UTC | 2h 45m |
| 2026-06-20 | THY707 | - | Jun 20, 22:25 UTC | Jun 21, 09:20 UTC | 10h 55m |
| 2026-06-20 | THY2JV | - | Jun 20, 19:04 UTC | Jun 20, 20:05 UTC | 1h 0m |
| 2026-06-20 | THY9QA | BLQ → IST | Jun 20, 16:24 UTC | Jun 20, 17:14 UTC | 50m |
| 2026-06-20 | THY8FU | - | Jun 20, 10:25 UTC | Jun 20, 12:54 UTC | 2h 30m |
| 2026-06-20 | THY2FB | - | Jun 20, 05:39 UTC | Jun 20, 07:59 UTC | 2h 20m |
| 2026-06-19 | THY707 | - | Jun 19, 00:05 UTC | Jun 19, 09:40 UTC | 9h 34m |
| 2026-06-18 | THY706 | - | Jun 18, 22:45 UTC | Jun 18, 23:15 UTC | 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-JNB page for operator, model, and routing details .