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
- 94
- Distinct callsigns
- 20
- Country
- AZ
- Last broadcast
- 56m ago
Last known 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 |
|---|---|---|---|
| AHY703 | Azerbaijan Airlines | 8 | 2026-05-08 |
| AHY033 | Azerbaijan Airlines | 6 | 2026-05-29 |
| AHY058 | Azerbaijan Airlines | 5 | 2026-04-27 |
| AHY055 | Azerbaijan Airlines | 5 | 2026-05-20 |
| AHY8234 | Azerbaijan Airlines | 4 | 2026-05-24 |
| AHY8224 | Azerbaijan Airlines | 4 | 2026-05-18 |
| AHY019 | Azerbaijan Airlines | 4 | 2026-05-17 |
| AHY8233 | Azerbaijan Airlines | 3 | 2026-05-24 |
| AHY8223 | Azerbaijan Airlines | 3 | 2026-05-24 |
| AHY807 | Azerbaijan Airlines | 3 | 2026-05-28 |
| AHY185 | Azerbaijan Airlines | 3 | 2026-05-16 |
| AHY175 | Azerbaijan Airlines | 3 | 2026-05-03 |
| AHY057 | Azerbaijan Airlines | 3 | 2026-05-18 |
| AHY8226 | Azerbaijan Airlines | 2 | 2026-05-27 |
| AHY812 | Azerbaijan Airlines | 2 | 2026-05-28 |
| AHY8041 | Azerbaijan Airlines | 2 | 2026-04-28 |
| AHY804 | Azerbaijan Airlines | 2 | 2026-04-27 |
| AHY803 | Azerbaijan Airlines | 2 | 2026-04-26 |
| AHY704 | Azerbaijan Airlines | 2 | 2026-04-17 |
| AHY5830 | - | 2 | 2026-05-04 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-30 | AHY034 | TIV → GYD | May 30, 10:40 UTC | May 30, 13:00 UTC | 2h 20m |
| 2026-05-29 | AHY033 | GYD → TIV | May 29, 23:25 UTC | May 30, 09:25 UTC | 10h 0m |
| 2026-05-29 | AHY8106 | SAW → GYD | May 29, 13:05 UTC | May 29, 21:55 UTC | 8h 50m |
| 2026-05-29 | AHY8105 | GYD → SAW | May 29, 04:10 UTC | May 29, 11:50 UTC | 7h 40m |
| 2026-05-28 | AHY5041 | - | May 28, 23:50 UTC | May 29, 02:40 UTC | 2h 50m |
| 2026-05-28 | AHY812 | VKO → GYD | May 28, 19:00 UTC | May 28, 19:40 UTC | 40m |
| 2026-05-28 | AHY5829 | - | May 28, 09:40 UTC | May 28, 10:05 UTC | 25m |
| 2026-05-28 | AHY807 | GYD → VKO | May 28, 07:00 UTC | May 28, 07:20 UTC | 20m |
| 2026-05-27 | AHY8238 | TBS → GYD | May 27, 21:55 UTC | May 27, 22:20 UTC | 25m |
| 2026-05-27 | AHY8226 | TBS → GYD | May 27, 17:15 UTC | May 27, 20:50 UTC | 3h 35m |
| 2026-05-27 | AHY8225 | GYD → TBS | May 27, 15:30 UTC | May 27, 16:00 UTC | 30m |
| 2026-05-26 | AHY076 | IST → GYD | May 26, 10:10 UTC | May 26, 11:20 UTC | 1h 10m |
| 2026-05-26 | AHY076 | IST → GYD | May 26, 09:15 UTC | May 26, 09:25 UTC | 10m |
| 2026-05-26 | AHY075 | GYD → IST | May 26, 06:59 UTC | May 26, 07:15 UTC | 15m |
| 2026-05-25 | AHY075 | GYD → IST | May 25, 23:30 UTC | May 26, 06:14 UTC | 6h 45m |
| 2026-05-24 | AHY8234 | TBS → GYD | May 24, 13:05 UTC | May 24, 13:30 UTC | 25m |
| 2026-05-24 | AHY8233 | GYD → TBS | May 24, 07:50 UTC | May 24, 11:50 UTC | 4h 0m |
| 2026-05-24 | AHY8223 | GYD → TBS | May 24, 05:55 UTC | May 24, 06:30 UTC | 35m |
| 2026-05-20 | AHY055 | GYD → SSH | May 20, 04:25 UTC | May 20, 17:30 UTC | 13h 6m |
| 2026-05-19 | AHY055 | GYD → SSH | May 19, 13:20 UTC | May 20, 11:40 UTC | 22h 21m |
| 2026-05-19 | AHY122 | KVD → LED | May 19, 12:00 UTC | May 20, 11:00 UTC | 23h 1m |
| 2026-05-19 | AHY121 | LED → KVD | May 19, 01:45 UTC | May 19, 10:10 UTC | 8h 25m |
| 2026-05-18 | AHY057 | GYD → DEL | May 18, 23:30 UTC | May 19, 00:15 UTC | 45m |
| 2026-05-18 | AHY8234 | TBS → GYD | May 18, 12:45 UTC | May 18, 13:10 UTC | 25m |
| 2026-05-18 | AHY8233 | GYD → TBS | May 18, 11:00 UTC | May 18, 11:30 UTC | 30m |
| 2026-05-18 | AHY8224 | TBS → GYD | May 18, 07:55 UTC | May 18, 08:20 UTC | 25m |
| 2026-05-18 | AHY8223 | GYD → TBS | May 18, 06:01 UTC | May 18, 06:55 UTC | 55m |
| 2026-05-17 | AHY019 | GYD → LED | May 17, 17:05 UTC | May 17, 20:25 UTC | 3h 20m |
| 2026-05-17 | AHY8234 | TBS → GYD | May 17, 13:01 UTC | May 17, 13:31 UTC | 30m |
| 2026-05-17 | AHY8224 | TBS → GYD | May 17, 08:05 UTC | May 17, 11:35 UTC | 3h 30m |
| 2026-05-16 | AHY185 | GYD → DME | May 16, 17:50 UTC | May 17, 06:35 UTC | 12h 45m |
| 2026-05-16 | AHY185 | GYD → DME | May 16, 06:10 UTC | May 16, 18:25 UTC | 12h 15m |
| 2026-05-13 | AHY4115 | - | May 13, 12:05 UTC | May 13, 13:55 UTC | 1h 50m |
| 2026-05-10 | AHY019 | GYD → LED | May 10, 23:25 UTC | May 11, 19:00 UTC | 19h 36m |
| 2026-05-10 | AHY019 | GYD → LED | May 10, 19:54 UTC | May 11, 19:00 UTC | 23h 6m |
| 2026-05-10 | AHY807 | GYD → VKO | May 10, 05:45 UTC | May 10, 07:40 UTC | 1h 55m |
| 2026-05-09 | AHY186 | DME → GYD | May 9, 22:00 UTC | May 9, 22:30 UTC | 30m |
| 2026-05-09 | AHY033 | GYD → TIV | May 9, 06:15 UTC | May 9, 18:30 UTC | 12h 15m |
| 2026-05-08 | AHY033 | GYD → TIV | May 8, 19:20 UTC | May 9, 18:30 UTC | 23h 10m |
| 2026-05-08 | AHY033 | GYD → TIV | May 8, 11:25 UTC | May 9, 11:00 UTC | 23h 35m |
| 2026-05-08 | AHY033 | GYD → TIV | May 8, 10:19 UTC | May 9, 09:00 UTC | 22h 40m |
| 2026-05-08 | AHY703 | GYD → RMO | May 8, 06:14 UTC | May 8, 08:44 UTC | 2h 30m |
| 2026-05-06 | AHY033 | GYD → TIV | May 6, 06:00 UTC | May 6, 13:15 UTC | 7h 15m |
| 2026-05-05 | AHY020 | LED → GYD | May 5, 22:01 UTC | May 5, 22:35 UTC | 35m |
| 2026-05-05 | AHY8224 | TBS → GYD | May 5, 08:05 UTC | May 5, 08:30 UTC | 25m |
| 2026-05-05 | AHY8223 | GYD → TBS | May 5, 06:25 UTC | May 5, 06:55 UTC | 30m |
| 2026-05-04 | AHY5830 | - | May 4, 17:10 UTC | May 4, 17:20 UTC | 10m |
| 2026-05-03 | AHY175 | GYD → IST | May 3, 07:25 UTC | May 3, 13:30 UTC | 6h 5m |
| 2026-05-01 | AHY703 | GYD → RMO | May 1, 06:15 UTC | May 1, 19:40 UTC | 13h 25m |
| 2026-04-30 | AHY703 | GYD → RMO | Apr 30, 23:50 UTC | May 1, 19:40 UTC | 19h 50m |
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 .