sensors Mode-S transponder
4BA9F5
ICAO 24-bit transponder address · allocated to Turkey
Currently assigned to TC-JOU · AIRBUS A-330-200
- Hex
- 4BA9F5
- Octal
- 22724765
- Decimal
- 4,958,709
- Country
- TR
- Tail
- TC-JOU
- Type
- A332
- Flights observed
- 66
- Distinct callsigns
- 20
- Country
- TR
- Last broadcast
- 27d ago
Last known position
Country allocation
The ICAO 24-bit address 4BA9F5 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 |
|---|---|---|---|
| THY6435 | Turkish Airlines | 6 | 2026-04-18 |
| THY6541 | Turkish Airlines | 3 | 2026-04-30 |
| THY6467 | Turkish Airlines | 3 | 2026-04-22 |
| THY6453 | Turkish Airlines | 3 | 2026-04-30 |
| THY6439 | Turkish Airlines | 3 | 2026-04-28 |
| THY6419 | Turkish Airlines | 3 | 2026-04-25 |
| THY6338 | Turkish Airlines | 3 | 2026-04-20 |
| THY6119 | Turkish Airlines | 3 | 2026-04-26 |
| THY6118 | Turkish Airlines | 3 | 2026-04-25 |
| THY6643 | Turkish Airlines | 2 | 2026-04-14 |
| THY6320 | Turkish Airlines | 2 | 2026-04-23 |
| THY6319 | Turkish Airlines | 2 | 2026-04-21 |
| THY6287 | Turkish Airlines | 2 | 2026-04-16 |
| THY6286 | Turkish Airlines | 2 | 2026-04-15 |
| THY6211 | Turkish Airlines | 2 | 2026-04-29 |
| THY6131 | Turkish Airlines | 2 | 2026-05-02 |
| THY6110 | - | 2 | 2026-04-26 |
| THY6102 | Turkish Airlines | 2 | 2026-04-19 |
| THY6065 | - | 2 | 2026-04-13 |
| THY6062 | - | 2 | 2026-04-13 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-02 | THY6131 | AMM → CAI | May 2, 16:05 UTC | May 2, 21:25 UTC | 5h 20m |
| 2026-05-02 | THY6131 | AMM → CAI | May 2, 08:40 UTC | May 2, 13:00 UTC | 4h 20m |
| 2026-05-01 | THY6510 | PRG → IST | May 1, 19:35 UTC | May 1, 21:20 UTC | 1h 45m |
| 2026-05-01 | THY6509 | AMM → TLV | May 1, 14:25 UTC | May 1, 16:15 UTC | 1h 50m |
| 2026-05-01 | THY6502 | - | May 1, 10:30 UTC | May 1, 11:30 UTC | 1h 0m |
| 2026-05-01 | THY6501 | IST → BEG | May 1, 06:00 UTC | May 1, 07:10 UTC | 1h 10m |
| 2026-04-30 | THY6453 | IST → BLL | Apr 30, 17:45 UTC | Apr 30, 19:45 UTC | 2h 0m |
| 2026-04-30 | THY6453 | IST → BLL | Apr 30, 12:40 UTC | Apr 30, 15:35 UTC | 2h 55m |
| 2026-04-30 | THY6453 | IST → BLL | Apr 30, 05:40 UTC | Apr 30, 09:50 UTC | 4h 10m |
| 2026-04-30 | THY6541 | IST → HEL | Apr 30, 00:15 UTC | Apr 30, 02:20 UTC | 2h 5m |
| 2026-04-29 | THY6541 | IST → HEL | Apr 29, 21:40 UTC | Apr 29, 22:40 UTC | 1h 0m |
| 2026-04-29 | THY6541 | IST → HEL | Apr 29, 16:10 UTC | Apr 29, 19:15 UTC | 3h 5m |
| 2026-04-29 | THY6211 | CIT → IST | Apr 29, 08:20 UTC | Apr 29, 09:35 UTC | 1h 16m |
| 2026-04-28 | THY6211 | CIT → IST | Apr 28, 13:35 UTC | Apr 29, 09:35 UTC | 20h 0m |
| 2026-04-28 | THY6091 | - | Apr 28, 11:10 UTC | Apr 28, 12:00 UTC | 50m |
| 2026-04-28 | THY6439 | IST → ALG | Apr 28, 05:15 UTC | Apr 28, 07:10 UTC | 1h 55m |
| 2026-04-28 | THY6439 | IST → ALG | Apr 28, 00:55 UTC | Apr 28, 02:30 UTC | 1h 35m |
| 2026-04-27 | THY6439 | IST → ALG | Apr 27, 20:00 UTC | Apr 27, 22:55 UTC | 2h 55m |
| 2026-04-26 | THY6110 | - | Apr 26, 14:15 UTC | Apr 27, 07:40 UTC | 17h 25m |
| 2026-04-26 | THY6110 | - | Apr 26, 09:20 UTC | Apr 27, 07:40 UTC | 22h 20m |
| 2026-04-26 | THY6119 | HKG → IST | Apr 26, 08:05 UTC | Apr 27, 07:15 UTC | 23h 10m |
| 2026-04-26 | THY6119 | HKG → IST | Apr 26, 02:35 UTC | Apr 26, 18:40 UTC | 16h 5m |
| 2026-04-25 | THY6118 | IST → MAA | Apr 25, 17:35 UTC | Apr 25, 22:05 UTC | 4h 30m |
| 2026-04-25 | THY6419 | ZRH → IST | Apr 25, 10:20 UTC | Apr 25, 12:25 UTC | 2h 5m |
| 2026-04-25 | THY6419 | ZRH → IST | Apr 25, 02:25 UTC | Apr 25, 08:00 UTC | 5h 35m |
| 2026-04-24 | THY6419 | ZRH → IST | Apr 24, 17:35 UTC | Apr 25, 00:35 UTC | 7h 0m |
| 2026-04-24 | THY6420 | ZRH → IST | Apr 24, 02:10 UTC | Apr 24, 14:15 UTC | 12h 5m |
| 2026-04-23 | THY6320 | ORD → IST | Apr 23, 22:55 UTC | Apr 23, 23:30 UTC | 35m |
| 2026-04-23 | THY6320 | ORD → IST | Apr 23, 09:40 UTC | Apr 23, 21:10 UTC | 11h 30m |
| 2026-04-23 | THY6512 | IST → NBO | Apr 23, 04:10 UTC | Apr 23, 06:35 UTC | 2h 25m |
| 2026-04-22 | THY6511 | IST → IST | Apr 22, 22:35 UTC | Apr 23, 01:05 UTC | 2h 30m |
| 2026-04-22 | THY6467 | BOM → IST | Apr 22, 12:40 UTC | Apr 22, 15:30 UTC | 2h 50m |
| 2026-04-22 | THY6467 | BOM → IST | Apr 22, 08:30 UTC | Apr 22, 10:35 UTC | 2h 5m |
| 2026-04-22 | THY6467 | BOM → IST | Apr 22, 01:35 UTC | Apr 22, 05:20 UTC | 3h 45m |
| 2026-04-21 | THY6139 | HKG → BOM | Apr 21, 21:15 UTC | Apr 21, 22:30 UTC | 1h 15m |
| 2026-04-21 | THY6138 | CDG → CDG | Apr 21, 16:05 UTC | Apr 21, 17:30 UTC | 1h 25m |
| 2026-04-21 | THY6319 | ATL → ORD | Apr 21, 08:45 UTC | Apr 21, 10:05 UTC | 1h 20m |
| 2026-04-20 | THY6319 | ATL → ORD | Apr 20, 22:00 UTC | Apr 20, 22:15 UTC | 15m |
| 2026-04-20 | THY6338 | ZRH → IST | Apr 20, 19:20 UTC | Apr 20, 19:30 UTC | 10m |
| 2026-04-20 | THY6338 | ZRH → IST | Apr 20, 15:50 UTC | Apr 20, 17:20 UTC | 1h 30m |
| 2026-04-20 | THY6338 | ZRH → IST | Apr 20, 05:55 UTC | Apr 20, 10:10 UTC | 4h 15m |
| 2026-04-19 | THY6103 | BLR → IST | Apr 19, 16:55 UTC | Apr 19, 23:40 UTC | 6h 45m |
| 2026-04-19 | THY6102 | FRU → HKG | Apr 19, 14:00 UTC | Apr 19, 14:15 UTC | 15m |
| 2026-04-19 | THY6102 | FRU → HKG | Apr 19, 07:45 UTC | Apr 19, 12:05 UTC | 4h 20m |
| 2026-04-19 | THY6430 | MXP → IST | Apr 19, 02:25 UTC | Apr 19, 04:25 UTC | 2h 0m |
| 2026-04-18 | THY6429 | HKG → IST | Apr 18, 21:30 UTC | Apr 18, 23:45 UTC | 2h 15m |
| 2026-04-18 | THY6435 | MST → ORD | Apr 18, 13:25 UTC | Apr 18, 15:25 UTC | 2h 0m |
| 2026-04-18 | THY6435 | MST → ORD | Apr 18, 08:15 UTC | Apr 18, 09:20 UTC | 1h 5m |
| 2026-04-18 | THY6435 | MST → ORD | Apr 18, 05:05 UTC | Apr 18, 10:35 UTC | 5h 30m |
| 2026-04-18 | THY6435 | MST → ORD | Apr 18, 02:05 UTC | Apr 18, 02:35 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-JOU page for operator, model, and routing details .