sensors Mode-S transponder
60084D
ICAO 24-bit transponder address · allocated to Azerbaijan
Currently assigned to 4K-AZ77 · AIRBUS A-320
- Hex
- 60084D
- Octal
- 30004115
- Decimal
- 6,293,581
- Country
- AZ
- Tail
- 4K-AZ77
- Type
- A320
- Flights observed
- 199
- Distinct callsigns
- 20
- Country
- AZ
- Last broadcast
- 1h ago
Last known position
Country allocation
The ICAO 24-bit address 60084D falls within the block assigned to Azerbaijan (AZ) by ICAO Annex 10, Volume III. Every aircraft registered in Azerbaijan 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 |
|---|---|---|---|
| AHY033 | - | 16 | 2026-07-12 |
| AHY034 | - | 11 | 2026-07-12 |
| AHY8224 | - | 9 | 2026-06-24 |
| AHY8233 | Azerbaijan Airlines | 8 | 2026-05-19 |
| AHY703 | - | 8 | 2026-07-03 |
| AHY055 | - | 8 | 2026-06-21 |
| AHY8234 | - | 7 | 2026-06-24 |
| AHY8223 | Azerbaijan Airlines | 7 | 2026-05-26 |
| AHY122 | - | 6 | 2026-07-08 |
| AHY121 | - | 6 | 2026-07-08 |
| AHY056 | Azerbaijan Airlines | 6 | 2026-05-29 |
| AHY075 | - | 5 | 2026-07-13 |
| AHY061 | - | 5 | 2026-07-01 |
| AHY8104 | - | 4 | 2026-06-23 |
| AHY8103 | - | 4 | 2026-06-22 |
| AHY175 | Azerbaijan Airlines | 4 | 2026-04-20 |
| AHY025 | - | 4 | 2026-07-14 |
| AHY8105 | Azerbaijan Airlines | 3 | 2026-05-01 |
| AHY8042 | Azerbaijan Airlines | 3 | 2026-04-25 |
| AHY704 | Azerbaijan Airlines | 3 | 2026-06-09 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | AHY026 | - | Jul 14, 08:05 UTC | Jul 14, 09:50 UTC | 1h 45m |
| 2026-07-14 | AHY025 | - | Jul 14, 04:15 UTC | Jul 14, 06:40 UTC | 2h 25m |
| 2026-07-13 | AHY076 | - | Jul 13, 09:15 UTC | Jul 13, 11:05 UTC | 1h 50m |
| 2026-07-13 | AHY075 | - | Jul 13, 05:01 UTC | Jul 13, 07:25 UTC | 2h 25m |
| 2026-07-12 | AHY034 | - | Jul 12, 10:55 UTC | Jul 12, 13:45 UTC | 2h 50m |
| 2026-07-12 | AHY033 | - | Jul 12, 05:55 UTC | Jul 12, 09:10 UTC | 3h 15m |
| 2026-07-10 | AHY2252 | - | Jul 10, 02:15 UTC | Jul 10, 02:35 UTC | 20m |
| 2026-07-10 | AHY2251 | - | Jul 10, 00:20 UTC | Jul 10, 00:45 UTC | 25m |
| 2026-07-09 | AHY5830 | - | Jul 9, 14:40 UTC | Jul 9, 14:50 UTC | 10m |
| 2026-07-09 | AHY5829 | - | Jul 9, 09:50 UTC | Jul 9, 10:25 UTC | 35m |
| 2026-07-08 | AHY122 | - | Jul 8, 10:25 UTC | Jul 8, 12:30 UTC | 2h 5m |
| 2026-07-08 | AHY121 | - | Jul 8, 06:00 UTC | Jul 8, 08:45 UTC | 2h 45m |
| 2026-07-07 | AHY022 | - | Jul 7, 10:05 UTC | Jul 7, 12:05 UTC | 2h 0m |
| 2026-07-07 | AHY021 | - | Jul 7, 05:40 UTC | Jul 7, 08:30 UTC | 2h 50m |
| 2026-07-05 | AHY034 | - | Jul 5, 12:15 UTC | Jul 5, 14:50 UTC | 2h 35m |
| 2026-07-04 | AHY033 | - | Jul 4, 17:05 UTC | Jul 5, 10:20 UTC | 17h 15m |
| 2026-07-04 | AHY8227 | - | Jul 4, 10:25 UTC | Jul 4, 16:00 UTC | 5h 35m |
| 2026-07-03 | AHY703 | - | Jul 3, 14:40 UTC | Jul 4, 07:40 UTC | 17h 0m |
| 2026-07-03 | AHY125 | - | Jul 3, 06:50 UTC | Jul 3, 13:25 UTC | 6h 35m |
| 2026-07-02 | AHY122 | KVD → LED | Jul 2, 12:10 UTC | Jul 3, 05:10 UTC | 17h 0m |
| 2026-07-02 | AHY121 | - | Jul 2, 07:40 UTC | Jul 2, 10:20 UTC | 2h 40m |
| 2026-07-01 | AHY121 | LED → KVD | Jul 1, 09:20 UTC | Jul 2, 09:15 UTC | 23h 55m |
| 2026-07-01 | AHY062 | - | Jul 1, 07:50 UTC | Jul 1, 09:45 UTC | 1h 55m |
| 2026-07-01 | AHY061 | - | Jul 1, 04:00 UTC | Jul 1, 06:20 UTC | 2h 20m |
| 2026-06-30 | AHY061 | - | Jun 30, 09:20 UTC | Jul 1, 06:20 UTC | 21h 0m |
| 2026-06-30 | AHY061 | - | Jun 30, 07:55 UTC | Jul 1, 06:20 UTC | 22h 25m |
| 2026-06-30 | AHY025 | - | Jun 30, 04:25 UTC | Jun 30, 06:50 UTC | 2h 25m |
| 2026-06-29 | AHY076 | - | Jun 29, 09:20 UTC | Jun 29, 11:14 UTC | 1h 55m |
| 2026-06-28 | AHY075 | - | Jun 28, 13:19 UTC | Jun 29, 07:25 UTC | 18h 5m |
| 2026-06-28 | AHY061 | - | Jun 28, 09:05 UTC | Jun 28, 11:25 UTC | 2h 20m |
| 2026-06-27 | AHY5122 | - | Jun 27, 12:19 UTC | Jun 27, 12:34 UTC | 15m |
| 2026-06-25 | AHY126 | - | Jun 25, 14:34 UTC | Jun 26, 06:54 UTC | 16h 20m |
| 2026-06-25 | AHY125 | AYT → AYT | Jun 25, 06:00 UTC | Jun 25, 13:20 UTC | 7h 20m |
| 2026-06-25 | AHY027 | - | Jun 25, 02:19 UTC | Jun 25, 04:49 UTC | 2h 30m |
| 2026-06-24 | AHY8238 | - | Jun 24, 21:54 UTC | Jun 24, 22:25 UTC | 30m |
| 2026-06-24 | AHY8237 | - | Jun 24, 20:14 UTC | Jun 24, 20:40 UTC | 25m |
| 2026-06-24 | AHY8226 | - | Jun 24, 17:29 UTC | Jun 24, 17:59 UTC | 30m |
| 2026-06-24 | AHY8225 | - | Jun 24, 15:39 UTC | Jun 24, 16:05 UTC | 25m |
| 2026-06-24 | AHY8234 | - | Jun 24, 13:05 UTC | Jun 24, 13:34 UTC | 30m |
| 2026-06-24 | AHY8224 | TBS → TBS | Jun 24, 07:54 UTC | Jun 24, 11:50 UTC | 3h 55m |
| 2026-06-23 | AHY8228 | BUS → TBS | Jun 23, 14:04 UTC | Jun 24, 06:45 UTC | 16h 40m |
| 2026-06-23 | AHY8104 | - | Jun 23, 07:49 UTC | Jun 23, 13:00 UTC | 5h 10m |
| 2026-06-22 | AHY8103 | - | Jun 22, 11:24 UTC | Jun 23, 06:04 UTC | 18h 40m |
| 2026-06-22 | AHY8103 | - | Jun 22, 09:34 UTC | Jun 23, 06:04 UTC | 20h 30m |
| 2026-06-21 | AHY055 | - | Jun 21, 13:20 UTC | Jun 22, 07:49 UTC | 18h 30m |
| 2026-06-21 | AHY055 | - | Jun 21, 13:00 UTC | Jun 22, 07:49 UTC | 18h 50m |
| 2026-06-21 | AHY061 | - | Jun 21, 06:29 UTC | Jun 21, 11:34 UTC | 5h 5m |
| 2026-06-20 | AHY8239 | - | Jun 20, 23:19 UTC | Jun 21, 05:10 UTC | 5h 50m |
| 2026-06-19 | AHY076 | - | Jun 19, 09:34 UTC | Jun 19, 11:24 UTC | 1h 50m |
| 2026-06-19 | AHY075 | - | Jun 19, 05:14 UTC | Jun 19, 07:39 UTC | 2h 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 4K-AZ77 page for operator, model, and routing details .