sensors Mode-S transponder
600850
ICAO 24-bit transponder address · allocated to Azerbaijan
Currently assigned to 4K-AZ80 · AIRBUS A-320
- Hex
- 600850
- Octal
- 30004120
- Decimal
- 6,293,584
- Country
- AZ
- Tail
- 4K-AZ80
- Type
- A320
- Flights observed
- 213
- Distinct callsigns
- 20
- Country
- AZ
- Last broadcast
- Jul 24, 15:25 UTC
Last known position
Country allocation
The ICAO 24-bit address 600850 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 | - | 13 | 2026-07-02 |
| AHY704 | - | 10 | 2026-07-02 |
| AHY059 | Azerbaijan Airlines | 10 | 2026-07-22 |
| AHY055 | Azerbaijan Airlines | 10 | 2026-07-21 |
| AHY8105 | - | 8 | 2026-06-22 |
| AHY034 | Azerbaijan Airlines | 8 | 2026-07-18 |
| AHY033 | Azerbaijan Airlines | 8 | 2026-07-18 |
| AHY060 | Azerbaijan Airlines | 7 | 2026-07-22 |
| AHY056 | Azerbaijan Airlines | 7 | 2026-07-20 |
| AHY057 | Azerbaijan Airlines | 6 | 2026-06-30 |
| AHY8106 | - | 5 | 2026-06-22 |
| AHY121 | - | 5 | 2026-07-21 |
| AHY8229 | - | 4 | 2026-06-13 |
| AHY5830 | - | 4 | 2026-06-15 |
| AHY5829 | - | 4 | 2026-06-05 |
| AHY075 | - | 4 | 2026-06-26 |
| AHY027 | Azerbaijan Airlines | 4 | 2026-07-24 |
| AHY8230 | Azerbaijan Airlines | 3 | 2026-06-13 |
| AHY809 | - | 3 | 2026-07-14 |
| AHY807 | Azerbaijan Airlines | 3 | 2026-06-05 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-24 | AHY2352 | - | Jul 24, 15:05 UTC | Jul 24, 15:25 UTC | 20m |
| 2026-07-24 | AHY028 | GYD → AYT | Jul 24, 06:35 UTC | Jul 24, 13:20 UTC | 6h 45m |
| 2026-07-24 | AHY027 | GYD → AYT | Jul 24, 02:30 UTC | Jul 24, 04:55 UTC | 2h 25m |
| 2026-07-22 | AHY060 | BOM → GYD | Jul 22, 23:10 UTC | Jul 23, 00:00 UTC | 50m |
| 2026-07-22 | AHY059 | GYD → BOM | Jul 22, 04:25 UTC | Jul 22, 21:25 UTC | 17h 0m |
| 2026-07-21 | AHY055 | GYD → SSH | Jul 21, 14:05 UTC | Jul 22, 11:40 UTC | 21h 35m |
| 2026-07-21 | AHY122 | KVD → LED | Jul 21, 12:05 UTC | Jul 22, 11:40 UTC | 23h 35m |
| 2026-07-21 | AHY121 | - | Jul 21, 07:45 UTC | Jul 21, 10:20 UTC | 2h 35m |
| 2026-07-20 | AHY056 | SSH → GYD | Jul 20, 09:20 UTC | Jul 20, 11:50 UTC | 2h 30m |
| 2026-07-20 | AHY055 | GYD → SSH | Jul 20, 04:50 UTC | Jul 20, 07:30 UTC | 2h 40m |
| 2026-07-19 | AHY8104 | SAW → GYD | Jul 19, 07:55 UTC | Jul 19, 09:45 UTC | 1h 50m |
| 2026-07-19 | AHY8103 | GYD → SAW | Jul 19, 03:45 UTC | Jul 19, 06:05 UTC | 2h 20m |
| 2026-07-18 | AHY034 | TIV → GYD | Jul 18, 11:15 UTC | Jul 18, 14:05 UTC | 2h 50m |
| 2026-07-18 | AHY033 | GYD → TIV | Jul 18, 06:00 UTC | Jul 18, 09:05 UTC | 3h 5m |
| 2026-07-17 | AHY034 | TIV → GYD | Jul 17, 10:50 UTC | Jul 17, 13:35 UTC | 2h 45m |
| 2026-07-16 | AHY033 | GYD → TIV | Jul 16, 21:15 UTC | Jul 17, 09:15 UTC | 12h 0m |
| 2026-07-16 | AHY059 | - | Jul 16, 18:25 UTC | Jul 16, 19:30 UTC | 1h 5m |
| 2026-07-15 | AHY2158 | - | Jul 15, 20:20 UTC | Jul 15, 20:40 UTC | 20m |
| 2026-07-15 | AHY2157 | - | Jul 15, 18:20 UTC | Jul 15, 18:45 UTC | 25m |
| 2026-07-14 | AHY809 | - | Jul 14, 05:30 UTC | Jul 14, 05:45 UTC | 15m |
| 2026-07-12 | AHY062 | - | Jul 12, 13:25 UTC | Jul 12, 15:25 UTC | 2h 0m |
| 2026-07-12 | AHY061 | - | Jul 12, 09:25 UTC | Jul 12, 11:40 UTC | 2h 15m |
| 2026-07-12 | AHY8240 | - | Jul 12, 06:25 UTC | Jul 12, 06:55 UTC | 30m |
| 2026-07-12 | AHY8240 | - | Jul 12, 04:30 UTC | Jul 12, 05:01 UTC | 30m |
| 2026-07-11 | AHY034 | - | Jul 11, 10:50 UTC | Jul 11, 13:35 UTC | 2h 45m |
| 2026-07-10 | AHY033 | - | Jul 10, 14:40 UTC | Jul 11, 09:15 UTC | 18h 35m |
| 2026-07-10 | AHY125 | - | Jul 10, 10:50 UTC | Jul 10, 13:25 UTC | 2h 35m |
| 2026-07-10 | AHY028 | - | Jul 10, 06:50 UTC | Jul 10, 08:30 UTC | 1h 40m |
| 2026-07-10 | AHY027 | - | Jul 10, 02:25 UTC | Jul 10, 04:55 UTC | 2h 30m |
| 2026-07-09 | AHY034 | - | Jul 9, 11:10 UTC | Jul 9, 13:45 UTC | 2h 35m |
| 2026-07-09 | AHY033 | - | Jul 9, 00:00 UTC | Jul 9, 09:35 UTC | 9h 35m |
| 2026-07-08 | AHY034 | - | Jul 8, 10:50 UTC | Jul 8, 22:20 UTC | 11h 30m |
| 2026-07-08 | AHY033 | - | Jul 8, 05:55 UTC | Jul 8, 09:00 UTC | 3h 5m |
| 2026-07-07 | AHY064 | - | Jul 7, 09:55 UTC | Jul 7, 13:30 UTC | 3h 35m |
| 2026-07-07 | AHY063 | - | Jul 7, 04:10 UTC | Jul 7, 08:35 UTC | 4h 25m |
| 2026-07-06 | AHY055 | - | Jul 6, 04:35 UTC | Jul 6, 11:50 UTC | 7h 15m |
| 2026-07-05 | AHY055 | - | Jul 5, 10:05 UTC | Jul 6, 10:00 UTC | 23h 55m |
| 2026-07-05 | AHY055 | - | Jul 5, 09:55 UTC | Jul 6, 07:25 UTC | 21h 30m |
| 2026-07-04 | AHY121 | - | Jul 4, 23:40 UTC | Jul 5, 07:30 UTC | 7h 50m |
| 2026-07-02 | AHY704 | - | Jul 2, 10:20 UTC | Jul 2, 12:35 UTC | 2h 15m |
| 2026-07-02 | AHY703 | - | Jul 2, 00:05 UTC | Jul 2, 08:55 UTC | 8h 50m |
| 2026-07-01 | AHY034 | - | Jul 1, 11:45 UTC | Jul 1, 22:20 UTC | 10h 35m |
| 2026-07-01 | AHY033 | - | Jul 1, 00:00 UTC | Jul 1, 09:00 UTC | 9h 0m |
| 2026-06-30 | AHY057 | GYD → DEL | Jun 30, 21:40 UTC | Jun 30, 22:35 UTC | 55m |
| 2026-06-30 | AHY126 | - | Jun 30, 14:40 UTC | Jun 30, 16:25 UTC | 1h 45m |
| 2026-06-30 | AHY125 | - | Jun 30, 06:10 UTC | Jun 30, 13:20 UTC | 7h 10m |
| 2026-06-30 | AHY027 | - | Jun 30, 02:15 UTC | Jun 30, 04:40 UTC | 2h 25m |
| 2026-06-28 | AHY060 | - | Jun 28, 23:14 UTC | Jun 29, 10:59 UTC | 11h 45m |
| 2026-06-28 | AHY059 | - | Jun 28, 20:09 UTC | Jun 28, 21:20 UTC | 1h 10m |
| 2026-06-28 | AHY026 | - | Jun 28, 08:09 UTC | Jun 28, 09:55 UTC | 1h 45m |
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-AZ80 page for operator, model, and routing details .