sensors Mode-S transponder
600854
ICAO 24-bit transponder address · allocated to Azerbaijan
Currently assigned to 4K-AZ84 · AIRBUS A-320
- Hex
- 600854
- Octal
- 30004124
- Decimal
- 6,293,588
- Country
- AZ
- Tail
- 4K-AZ84
- Type
- A320
- Flights observed
- 236
- Distinct callsigns
- 20
- Country
- AZ
- Last broadcast
- Jul 26, 12:05 UTC
Current position
Country allocation
The ICAO 24-bit address 600854 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 |
|---|---|---|---|
| AHY807 | - | 11 | 2026-07-10 |
| AHY057 | Azerbaijan Airlines | 11 | 2026-07-22 |
| AHY033 | Azerbaijan Airlines | 11 | 2026-07-23 |
| AHY703 | - | 9 | 2026-06-20 |
| AHY058 | Azerbaijan Airlines | 8 | 2026-07-22 |
| AHY055 | - | 8 | 2026-07-13 |
| AHY8224 | - | 7 | 2026-07-12 |
| AHY034 | Azerbaijan Airlines | 7 | 2026-07-23 |
| AHY8234 | - | 6 | 2026-07-12 |
| AHY5830 | - | 6 | 2026-07-24 |
| AHY019 | Azerbaijan Airlines | 6 | 2026-06-04 |
| AHY8105 | - | 5 | 2026-07-19 |
| AHY121 | Azerbaijan Airlines | 5 | 2026-07-25 |
| AHY8233 | - | 4 | 2026-07-12 |
| AHY8227 | Azerbaijan Airlines | 4 | 2026-07-25 |
| AHY185 | Azerbaijan Airlines | 4 | 2026-06-12 |
| AHY122 | Azerbaijan Airlines | 4 | 2026-07-26 |
| AHY024 | - | 4 | 2026-07-07 |
| AHY023 | - | 4 | 2026-07-07 |
| AHY8226 | Azerbaijan Airlines | 3 | 2026-05-30 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | AHY122 | KVD → LED | Jul 26, 10:05 UTC | Jul 26, 12:05 UTC | 2h 0m |
| 2026-07-25 | AHY121 | LED → KVD | Jul 25, 16:25 UTC | Jul 26, 07:55 UTC | 15h 31m |
| 2026-07-25 | AHY8227 | GYD → BUS | Jul 25, 14:25 UTC | Jul 25, 15:20 UTC | 55m |
| 2026-07-25 | AHY5084 | HER → GYD | Jul 25, 06:55 UTC | Jul 25, 08:55 UTC | 2h 0m |
| 2026-07-25 | AHY5083 | GYD → HER | Jul 25, 02:25 UTC | Jul 25, 05:15 UTC | 2h 50m |
| 2026-07-24 | AHY5830 | - | Jul 24, 15:05 UTC | Jul 24, 15:15 UTC | 10m |
| 2026-07-24 | AHY020 | LED → GYD | Jul 24, 00:25 UTC | Jul 24, 11:40 UTC | 11h 15m |
| 2026-07-23 | AHY034 | TIV → GYD | Jul 23, 11:05 UTC | Jul 23, 13:40 UTC | 2h 35m |
| 2026-07-23 | AHY033 | GYD → TIV | Jul 23, 00:00 UTC | Jul 23, 09:25 UTC | 9h 25m |
| 2026-07-22 | AHY057 | GYD → DEL | Jul 22, 21:10 UTC | Jul 22, 22:10 UTC | 1h 0m |
| 2026-07-22 | AHY057 | GYD → DEL | Jul 22, 01:05 UTC | Jul 22, 22:10 UTC | 21h 5m |
| 2026-07-22 | AHY058 | DEL → GYD | Jul 22, 00:10 UTC | Jul 22, 22:10 UTC | 22h 0m |
| 2026-07-21 | AHY057 | - | Jul 21, 21:15 UTC | Jul 21, 22:20 UTC | 1h 5m |
| 2026-07-20 | AHY5830 | - | Jul 20, 14:10 UTC | Jul 20, 14:20 UTC | 10m |
| 2026-07-19 | AHY8106 | - | Jul 19, 13:15 UTC | Jul 19, 15:00 UTC | 1h 45m |
| 2026-07-19 | AHY8105 | - | Jul 19, 00:40 UTC | Jul 19, 11:45 UTC | 11h 5m |
| 2026-07-18 | AHY057 | - | Jul 18, 13:30 UTC | Jul 18, 22:30 UTC | 9h 0m |
| 2026-07-18 | AHY5084 | HER → GYD | Jul 18, 07:20 UTC | Jul 18, 12:30 UTC | 5h 10m |
| 2026-07-18 | AHY5083 | GYD → HER | Jul 18, 02:45 UTC | Jul 18, 05:25 UTC | 2h 41m |
| 2026-07-16 | AHY805 | - | Jul 16, 18:00 UTC | Jul 16, 22:15 UTC | 4h 15m |
| 2026-07-16 | AHY122 | - | Jul 16, 12:09 UTC | Jul 16, 14:20 UTC | 2h 10m |
| 2026-07-16 | AHY121 | DEL → TLV | Jul 16, 00:10 UTC | Jul 16, 10:45 UTC | 10h 35m |
| 2026-07-15 | AHY057 | - | Jul 15, 21:40 UTC | Jul 15, 22:35 UTC | 55m |
| 2026-07-14 | AHY022 | - | Jul 14, 10:00 UTC | Jul 14, 18:35 UTC | 8h 35m |
| 2026-07-13 | AHY021 | - | Jul 13, 22:55 UTC | Jul 14, 08:30 UTC | 9h 35m |
| 2026-07-13 | AHY056 | - | Jul 13, 09:10 UTC | Jul 13, 21:10 UTC | 12h 0m |
| 2026-07-13 | AHY055 | - | Jul 13, 04:35 UTC | Jul 13, 07:25 UTC | 2h 50m |
| 2026-07-12 | AHY8234 | - | Jul 12, 12:55 UTC | Jul 12, 13:20 UTC | 25m |
| 2026-07-12 | AHY8233 | - | Jul 12, 11:01 UTC | Jul 12, 11:30 UTC | 30m |
| 2026-07-12 | AHY8224 | - | Jul 12, 07:55 UTC | Jul 12, 08:25 UTC | 30m |
| 2026-07-11 | AHY060 | - | Jul 11, 21:50 UTC | Jul 12, 06:30 UTC | 8h 40m |
| 2026-07-11 | AHY059 | BUS → BOM | Jul 11, 13:35 UTC | Jul 11, 20:25 UTC | 6h 50m |
| 2026-07-11 | AHY8227 | - | Jul 11, 11:20 UTC | Jul 11, 12:15 UTC | 55m |
| 2026-07-11 | AHY5084 | - | Jul 11, 06:30 UTC | Jul 11, 08:45 UTC | 2h 15m |
| 2026-07-11 | AHY5083 | - | Jul 11, 02:15 UTC | Jul 11, 05:05 UTC | 2h 50m |
| 2026-07-10 | AHY807 | - | Jul 10, 06:45 UTC | Jul 10, 07:10 UTC | 25m |
| 2026-07-09 | AHY807 | - | Jul 9, 11:35 UTC | Jul 10, 07:10 UTC | 19h 35m |
| 2026-07-09 | AHY8230 | - | Jul 9, 06:05 UTC | Jul 9, 10:30 UTC | 4h 25m |
| 2026-07-09 | AHY8229 | - | Jul 9, 04:00 UTC | Jul 9, 04:25 UTC | 25m |
| 2026-07-08 | AHY2152 | - | Jul 8, 13:45 UTC | Jul 8, 14:05 UTC | 20m |
| 2026-07-08 | AHY2151 | - | Jul 8, 11:10 UTC | Jul 8, 11:40 UTC | 30m |
| 2026-07-08 | AHY8048 | - | Jul 8, 07:50 UTC | Jul 8, 08:45 UTC | 55m |
| 2026-07-08 | AHY8047 | - | Jul 8, 05:30 UTC | Jul 8, 06:40 UTC | 1h 10m |
| 2026-07-07 | AHY8047 | - | Jul 7, 09:05 UTC | Jul 8, 06:40 UTC | 21h 35m |
| 2026-07-07 | AHY024 | - | Jul 7, 08:45 UTC | Jul 8, 06:40 UTC | 21h 55m |
| 2026-07-07 | AHY023 | - | Jul 7, 05:00 UTC | Jul 7, 07:35 UTC | 2h 35m |
| 2026-07-06 | AHY110 | - | Jul 6, 11:10 UTC | Jul 6, 14:30 UTC | 3h 20m |
| 2026-07-05 | AHY109 | - | Jul 5, 15:05 UTC | Jul 6, 09:45 UTC | 18h 40m |
| 2026-07-05 | AHY109 | - | Jul 5, 14:40 UTC | Jul 6, 09:45 UTC | 19h 5m |
| 2026-07-05 | AHY8105 | - | Jul 5, 12:55 UTC | Jul 5, 13:10 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 4K-AZ84 page for operator, model, and routing details .