sensors Mode-S transponder
4BAA48
ICAO 24-bit transponder address · allocated to Turkey
Currently assigned to TC-JRH · AIRBUS A-321
- Hex
- 4BAA48
- Octal
- 22725110
- Decimal
- 4,958,792
- Country
- TR
- Tail
- TC-JRH
- Type
- A321
- Flights observed
- 53
- Distinct callsigns
- 20
- Country
- TR
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 4BAA48 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 |
|---|---|---|---|
| THY9EC | Turkish Airlines | 6 | 2026-05-15 |
| THY8EV | - | 5 | 2026-05-13 |
| THY1SM | Turkish Airlines | 5 | 2026-06-01 |
| THY5322 | Turkish Airlines | 4 | 2026-04-23 |
| THY2GR | Turkish Airlines | 4 | 2026-05-11 |
| THY7JT | Turkish Airlines | 3 | 2026-05-09 |
| THY3UJ | - | 3 | 2026-04-17 |
| THY8ML | Turkish Airlines | 2 | 2026-05-10 |
| THY4TJ | Turkish Airlines | 2 | 2026-05-08 |
| THY1TC | Turkish Airlines | 2 | 2026-05-15 |
| THY1LK | Turkish Airlines | 2 | 2026-05-10 |
| THY1KB | - | 2 | 2026-05-03 |
| THY9DM | Turkish Airlines | 1 | 2026-05-13 |
| THY7UJ | Turkish Airlines | 1 | 2026-04-15 |
| THY7CE | Turkish Airlines | 1 | 2026-05-04 |
| THY6985 | - | 1 | 2026-05-16 |
| THY6959 | - | 1 | 2026-04-26 |
| THY6947 | - | 1 | 2026-04-13 |
| THY4KR | Turkish Airlines | 1 | 2026-05-13 |
| THY2TS | Turkish Airlines | 1 | 2026-04-17 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-01 | THY1SM | AYT → VKO | Jun 1, 08:30 UTC | Jun 1, 20:15 UTC | 11h 45m |
| 2026-05-31 | - | - | May 31, 20:00 UTC | Jun 1, 08:30 UTC | 12h 30m |
| 2026-05-30 | THY1SM | AYT → VKO | May 30, 20:05 UTC | May 31, 20:00 UTC | 23h 55m |
| 2026-05-30 | THY1SM | AYT → VKO | May 30, 08:20 UTC | May 30, 20:30 UTC | 12h 10m |
| 2026-05-21 | - | - | May 21, 01:10 UTC | May 21, 01:30 UTC | 20m |
| 2026-05-17 | - | - | May 17, 07:55 UTC | May 17, 13:20 UTC | 5h 25m |
| 2026-05-16 | THY6985 | - | May 16, 14:11 UTC | May 16, 15:10 UTC | 1h 0m |
| 2026-05-15 | THY1TC | LED → AYT | May 15, 17:45 UTC | May 16, 02:15 UTC | 8h 30m |
| 2026-05-15 | THY9EC | AYT → LED | May 15, 17:05 UTC | May 15, 17:15 UTC | 10m |
| 2026-05-13 | THY4KR | IST → WAW | May 13, 17:55 UTC | May 14, 03:30 UTC | 9h 35m |
| 2026-05-13 | THY9DM | BJV → LED | May 13, 12:45 UTC | May 13, 16:15 UTC | 3h 30m |
| 2026-05-13 | THY8EV | - | May 13, 07:55 UTC | May 13, 10:45 UTC | 2h 50m |
| 2026-05-13 | THY8EV | - | May 13, 06:20 UTC | May 13, 06:30 UTC | 10m |
| 2026-05-11 | THY2GR | AMS → IST | May 11, 17:15 UTC | May 11, 21:15 UTC | 4h 0m |
| 2026-05-10 | THY1LK | IST → BJV | May 10, 18:15 UTC | May 11, 03:30 UTC | 9h 15m |
| 2026-05-10 | THY8ML | VKO → AYT | May 10, 05:30 UTC | May 10, 15:39 UTC | 10h 10m |
| 2026-05-10 | THY1LK | IST → BJV | May 10, 00:55 UTC | May 10, 03:10 UTC | 2h 15m |
| 2026-05-09 | THY2CU | IST → HTY | May 9, 18:10 UTC | May 9, 21:34 UTC | 3h 25m |
| 2026-05-09 | THY8ML | VKO → AYT | May 9, 11:25 UTC | May 9, 15:25 UTC | 4h 0m |
| 2026-05-09 | THY7JT | AYT → VKO | May 9, 05:35 UTC | May 9, 09:10 UTC | 3h 35m |
| 2026-05-08 | THY2GR | AMS → IST | May 8, 17:45 UTC | May 9, 03:00 UTC | 9h 15m |
| 2026-05-08 | THY4TJ | MSR → IST | May 8, 06:14 UTC | May 8, 09:39 UTC | 3h 25m |
| 2026-05-07 | THY2GR | AMS → IST | May 7, 17:05 UTC | May 8, 02:39 UTC | 9h 34m |
| 2026-05-06 | THY9EC | AYT → LED | May 6, 16:55 UTC | May 6, 20:45 UTC | 3h 49m |
| 2026-05-05 | THY9EC | AYT → LED | May 5, 16:45 UTC | May 6, 02:30 UTC | 9h 45m |
| 2026-05-04 | THY7CE | LED → AYT | May 4, 17:10 UTC | May 5, 02:25 UTC | 9h 16m |
| 2026-05-04 | THY4TJ | MSR → IST | May 4, 00:25 UTC | May 4, 09:50 UTC | 9h 25m |
| 2026-05-03 | THY1KB | - | May 3, 05:25 UTC | May 3, 21:24 UTC | 16h 0m |
| 2026-05-02 | THY9EC | AYT → LED | May 2, 17:05 UTC | May 3, 03:25 UTC | 10h 20m |
| 2026-05-01 | THY9EC | AYT → LED | May 1, 16:40 UTC | May 2, 02:15 UTC | 9h 35m |
| 2026-04-30 | THY1SM | AYT → VKO | Apr 30, 17:25 UTC | May 1, 03:25 UTC | 10h 0m |
| 2026-04-30 | THY1KB | - | Apr 30, 05:05 UTC | Apr 30, 14:25 UTC | 9h 20m |
| 2026-04-29 | THY8EV | - | Apr 29, 16:35 UTC | Apr 30, 02:05 UTC | 9h 29m |
| 2026-04-28 | THY8EV | - | Apr 28, 16:50 UTC | Apr 29, 02:30 UTC | 9h 40m |
| 2026-04-27 | THY8EV | - | Apr 27, 16:35 UTC | Apr 28, 02:00 UTC | 9h 25m |
| 2026-04-26 | THY1TC | LED → AYT | Apr 26, 22:35 UTC | Apr 27, 02:05 UTC | 3h 30m |
| 2026-04-26 | THY9EC | AYT → LED | Apr 26, 16:45 UTC | Apr 26, 20:55 UTC | 4h 10m |
| 2026-04-26 | THY7JT | AYT → VKO | Apr 26, 05:25 UTC | Apr 26, 14:55 UTC | 9h 30m |
| 2026-04-26 | THY6959 | - | Apr 26, 03:30 UTC | Apr 26, 04:20 UTC | 50m |
| 2026-04-25 | THY1SM | AYT → VKO | Apr 25, 17:35 UTC | Apr 25, 22:30 UTC | 4h 55m |
| 2026-04-25 | THY7JT | AYT → VKO | Apr 25, 05:20 UTC | Apr 25, 13:05 UTC | 7h 45m |
| 2026-04-24 | THY2GR | AMS → IST | Apr 24, 16:55 UTC | Apr 25, 02:30 UTC | 9h 35m |
| 2026-04-23 | THY5322 | IST → MED | Apr 23, 20:45 UTC | Apr 24, 12:05 UTC | 15h 20m |
| 2026-04-23 | THY5322 | IST → MED | Apr 23, 16:05 UTC | Apr 24, 12:05 UTC | 20h 0m |
| 2026-04-23 | THY5322 | IST → MED | Apr 23, 15:35 UTC | Apr 24, 12:05 UTC | 20h 30m |
| 2026-04-23 | THY5322 | IST → MED | Apr 23, 12:40 UTC | Apr 24, 12:00 UTC | 23h 20m |
| 2026-04-17 | THY3UJ | - | Apr 17, 18:10 UTC | Apr 17, 18:40 UTC | 30m |
| 2026-04-17 | THY2TS | IST → MQM | Apr 17, 05:45 UTC | Apr 17, 05:55 UTC | 10m |
| 2026-04-16 | THY1RW | - | Apr 16, 15:30 UTC | Apr 16, 15:45 UTC | 15m |
| 2026-04-15 | THY3UJ | - | Apr 15, 18:15 UTC | Apr 15, 18:30 UTC | 15m |
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-JRH page for operator, model, and routing details .