sensors Mode-S transponder
4B8394
ICAO 24-bit transponder address · allocated to Turkey
Currently assigned to TC-J3
- Hex
- 4B8394
- Octal
- 22701624
- Decimal
- 4,948,884
- Country
- TR
- Tail
- TC-J3
- Type
- BTB2
- Flights observed
- 35
- Distinct callsigns
- 1
- Country
- TR
- Last broadcast
- Jul 26, 07:05 UTC
Last known position
Country allocation
The ICAO 24-bit address 4B8394 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 1 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| ASLAN03 | - | 35 | 2026-07-25 |
Recent flights last 35
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-25 | ASLAN03 | - | Jul 25, 21:20 UTC | Jul 26, 07:05 UTC | 9h 46m |
| 2026-07-23 | ASLAN03 | - | Jul 23, 19:35 UTC | Jul 24, 07:20 UTC | 11h 45m |
| 2026-07-21 | ASLAN03 | - | Jul 21, 22:05 UTC | Jul 22, 05:25 UTC | 7h 20m |
| 2026-07-21 | ASLAN03 | - | Jul 21, 20:15 UTC | Jul 21, 21:20 UTC | 1h 5m |
| 2026-07-20 | ASLAN03 | - | Jul 20, 19:40 UTC | Jul 21, 06:35 UTC | 10h 54m |
| 2026-07-18 | ASLAN03 | - | Jul 18, 20:35 UTC | Jul 19, 10:05 UTC | 13h 30m |
| 2026-07-17 | ASLAN03 | - | Jul 17, 01:25 UTC | Jul 17, 08:30 UTC | 7h 5m |
| 2026-07-16 | ASLAN03 | - | Jul 16, 22:00 UTC | Jul 16, 23:29 UTC | 1h 30m |
| 2026-07-15 | ASLAN03 | - | Jul 15, 20:25 UTC | Jul 16, 08:15 UTC | 11h 50m |
| 2026-07-13 | ASLAN03 | - | Jul 13, 20:45 UTC | Jul 14, 09:20 UTC | 12h 35m |
| 2026-07-09 | ASLAN03 | - | Jul 9, 19:55 UTC | Jul 10, 08:10 UTC | 12h 15m |
| 2026-07-03 | ASLAN03 | - | Jul 3, 20:45 UTC | Jul 3, 21:10 UTC | 25m |
| 2026-07-01 | ASLAN03 | - | Jul 1, 00:30 UTC | Jul 1, 09:00 UTC | 8h 30m |
| 2026-06-30 | ASLAN03 | - | Jun 30, 21:45 UTC | Jun 30, 23:55 UTC | 2h 10m |
| 2026-06-28 | ASLAN03 | - | Jun 28, 19:14 UTC | Jun 29, 03:25 UTC | 8h 10m |
| 2026-06-27 | ASLAN03 | - | Jun 27, 19:59 UTC | Jun 28, 03:55 UTC | 7h 55m |
| 2026-06-25 | ASLAN03 | - | Jun 25, 20:05 UTC | Jun 26, 07:10 UTC | 11h 5m |
| 2026-06-22 | ASLAN03 | - | Jun 22, 03:45 UTC | Jun 22, 07:19 UTC | 3h 35m |
| 2026-06-21 | ASLAN03 | - | Jun 21, 20:40 UTC | Jun 21, 23:40 UTC | 3h 0m |
| 2026-06-14 | ASLAN03 | - | Jun 14, 22:40 UTC | Jun 15, 09:30 UTC | 10h 50m |
| 2026-06-11 | ASLAN03 | - | Jun 11, 22:30 UTC | Jun 12, 10:20 UTC | 11h 51m |
| 2026-06-06 | ASLAN03 | - | Jun 6, 19:19 UTC | Jun 7, 07:15 UTC | 11h 55m |
| 2026-06-03 | ASLAN03 | - | Jun 3, 19:25 UTC | Jun 4, 07:35 UTC | 12h 10m |
| 2026-06-01 | ASLAN03 | - | Jun 1, 19:40 UTC | Jun 2, 07:45 UTC | 12h 5m |
| 2026-05-30 | ASLAN03 | - | May 30, 18:15 UTC | May 31, 01:11 UTC | 6h 56m |
| 2026-05-25 | ASLAN03 | - | May 25, 20:59 UTC | May 25, 21:40 UTC | 40m |
| 2026-05-06 | ASLAN03 | - | May 6, 10:05 UTC | May 7, 00:20 UTC | 14h 14m |
| 2026-04-29 | ASLAN03 | - | Apr 29, 09:00 UTC | Apr 29, 22:55 UTC | 13h 55m |
| 2026-04-27 | ASLAN03 | - | Apr 27, 08:45 UTC | Apr 27, 22:05 UTC | 13h 20m |
| 2026-04-20 | ASLAN03 | - | Apr 20, 23:50 UTC | Apr 21, 11:50 UTC | 12h 0m |
| 2026-04-13 | ASLAN03 | - | Apr 13, 19:50 UTC | Apr 13, 21:30 UTC | 1h 40m |
| 2026-04-13 | ASLAN03 | - | Apr 13, 16:15 UTC | Apr 13, 20:10 UTC | 3h 55m |
| 2026-04-13 | ASLAN03 | - | Apr 13, 15:50 UTC | Apr 13, 19:45 UTC | 3h 55m |
| 2026-04-13 | ASLAN03 | - | Apr 13, 12:20 UTC | Apr 13, 16:15 UTC | 3h 55m |
| 2026-04-13 | ASLAN03 | - | Apr 13, 11:50 UTC | Apr 13, 12:15 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-J3 page for operator, model, and routing details .