sensors Mode-S transponder
600804
ICAO 24-bit transponder address · allocated to Azerbaijan
Currently assigned to 4K-AZ04 · AIRBUS A-319
- Hex
- 600804
- Octal
- 30004004
- Decimal
- 6,293,508
- Country
- AZ
- Tail
- 4K-AZ04
- Type
- A319
- Flights observed
- 191
- Distinct callsigns
- 20
- Country
- AZ
- Last broadcast
- Jul 26, 17:45 UTC
Last known position
Country allocation
The ICAO 24-bit address 600804 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 |
|---|---|---|---|
| AHY8103 | Azerbaijan Airlines | 19 | 2026-07-25 |
| AHY025 | - | 13 | 2026-06-29 |
| AHY8041 | Azerbaijan Airlines | 11 | 2026-07-25 |
| AHY703 | Azerbaijan Airlines | 11 | 2026-07-24 |
| AHY8104 | Azerbaijan Airlines | 9 | 2026-07-26 |
| AHY023 | - | 9 | 2026-06-22 |
| AHY8042 | Azerbaijan Airlines | 6 | 2026-07-25 |
| AHY026 | - | 6 | 2026-06-29 |
| AHY8230 | Azerbaijan Airlines | 5 | 2026-06-11 |
| AHY8229 | Azerbaijan Airlines | 5 | 2026-06-11 |
| AHY8226 | Azerbaijan Airlines | 5 | 2026-05-17 |
| AHY175 | Azerbaijan Airlines | 5 | 2026-05-16 |
| AHY071 | - | 5 | 2026-06-30 |
| AHY8238 | Azerbaijan Airlines | 4 | 2026-05-17 |
| AHY8237 | Azerbaijan Airlines | 4 | 2026-05-12 |
| AHY704 | - | 4 | 2026-06-25 |
| AHY045 | Azerbaijan Airlines | 4 | 2026-06-07 |
| AHY027 | - | 4 | 2026-06-28 |
| AHY8225 | Azerbaijan Airlines | 3 | 2026-05-11 |
| AHY185 | Azerbaijan Airlines | 3 | 2026-05-28 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | AHY292 | - | Jul 26, 17:25 UTC | Jul 26, 17:45 UTC | 20m |
| 2026-07-26 | AHY8104 | SAW → GYD | Jul 26, 07:55 UTC | Jul 26, 15:30 UTC | 7h 35m |
| 2026-07-25 | AHY8103 | GYD → SAW | Jul 25, 21:10 UTC | Jul 26, 06:05 UTC | 8h 55m |
| 2026-07-25 | AHY8042 | ADB → GYD | Jul 25, 10:00 UTC | Jul 25, 19:30 UTC | 9h 30m |
| 2026-07-25 | AHY8041 | GYD → ADB | Jul 25, 05:55 UTC | Jul 25, 08:25 UTC | 2h 30m |
| 2026-07-24 | AHY703 | GYD → RMO | Jul 24, 06:20 UTC | Jul 24, 12:35 UTC | 6h 15m |
| 2026-07-23 | AHY703 | GYD → RMO | Jul 23, 09:05 UTC | Jul 24, 09:00 UTC | 23h 55m |
| 2026-07-23 | AHY8104 | SAW → GYD | Jul 23, 07:50 UTC | Jul 24, 07:00 UTC | 23h 10m |
| 2026-07-23 | AHY8103 | GYD → SAW | Jul 23, 04:05 UTC | Jul 23, 06:25 UTC | 2h 20m |
| 2026-07-22 | AHY2152 | - | Jul 22, 17:30 UTC | Jul 22, 17:50 UTC | 20m |
| 2026-07-22 | AHY122 | KVD → LED | Jul 22, 11:45 UTC | Jul 22, 15:50 UTC | 4h 5m |
| 2026-07-21 | AHY703 | GYD → RMO | Jul 21, 06:20 UTC | Jul 21, 23:50 UTC | 17h 30m |
| 2026-07-20 | AHY703 | GYD → RMO | Jul 20, 19:15 UTC | Jul 21, 12:30 UTC | 17h 15m |
| 2026-07-20 | AHY703 | GYD → RMO | Jul 20, 13:05 UTC | Jul 21, 12:30 UTC | 23h 25m |
| 2026-07-20 | AHY8105 | GYD → SAW | Jul 20, 09:20 UTC | Jul 20, 11:35 UTC | 2h 15m |
| 2026-07-20 | AHY8240 | TBS → GYD | Jul 20, 06:20 UTC | Jul 20, 06:45 UTC | 25m |
| 2026-07-20 | AHY8239 | GYD → TBS | Jul 20, 04:45 UTC | Jul 20, 05:15 UTC | 30m |
| 2026-07-07 | AHY8104 | - | Jul 7, 07:40 UTC | Jul 7, 08:05 UTC | 25m |
| 2026-07-06 | AHY8103 | - | Jul 6, 21:10 UTC | Jul 7, 06:10 UTC | 9h 0m |
| 2026-07-06 | AHY8104 | - | Jul 6, 07:45 UTC | Jul 6, 09:40 UTC | 1h 55m |
| 2026-07-06 | AHY8103 | - | Jul 6, 03:50 UTC | Jul 6, 06:15 UTC | 2h 25m |
| 2026-06-30 | AHY072 | - | Jun 30, 11:15 UTC | Jun 30, 14:30 UTC | 3h 15m |
| 2026-06-30 | AHY071 | - | Jun 30, 06:00 UTC | Jun 30, 09:50 UTC | 3h 50m |
| 2026-06-29 | AHY071 | - | Jun 29, 09:05 UTC | Jun 30, 09:00 UTC | 23h 56m |
| 2026-06-29 | AHY026 | - | Jun 29, 08:04 UTC | Jun 30, 07:00 UTC | 22h 55m |
| 2026-06-29 | AHY025 | - | Jun 29, 04:20 UTC | Jun 29, 06:44 UTC | 2h 25m |
| 2026-06-28 | AHY028 | - | Jun 28, 06:49 UTC | Jun 28, 16:14 UTC | 9h 25m |
| 2026-06-28 | AHY027 | - | Jun 28, 03:05 UTC | Jun 28, 05:34 UTC | 2h 30m |
| 2026-06-27 | AHY027 | - | Jun 27, 09:04 UTC | Jun 28, 05:34 UTC | 20h 30m |
| 2026-06-27 | AHY027 | - | Jun 27, 07:59 UTC | Jun 28, 05:34 UTC | 21h 35m |
| 2026-06-26 | AHY061 | - | Jun 26, 22:05 UTC | Jun 27, 06:25 UTC | 8h 20m |
| 2026-06-26 | AHY025 | - | Jun 26, 04:45 UTC | Jun 26, 09:59 UTC | 5h 15m |
| 2026-06-25 | AHY025 | - | Jun 25, 11:04 UTC | Jun 26, 09:59 UTC | 22h 55m |
| 2026-06-25 | AHY704 | - | Jun 25, 10:20 UTC | Jun 26, 08:34 UTC | 22h 15m |
| 2026-06-24 | AHY703 | - | Jun 24, 23:29 UTC | Jun 25, 07:45 UTC | 8h 15m |
| 2026-06-24 | AHY703 | - | Jun 24, 11:05 UTC | Jun 25, 07:45 UTC | 20h 40m |
| 2026-06-24 | AHY704 | - | Jun 24, 10:30 UTC | Jun 25, 07:45 UTC | 21h 15m |
| 2026-06-24 | AHY704 | - | Jun 24, 07:05 UTC | Jun 25, 07:00 UTC | 23h 55m |
| 2026-06-24 | AHY704 | - | Jun 24, 06:25 UTC | Jun 24, 23:34 UTC | 17h 10m |
| 2026-06-22 | AHY024 | - | Jun 22, 08:54 UTC | Jun 22, 10:55 UTC | 2h 0m |
| 2026-06-22 | AHY023 | - | Jun 22, 04:54 UTC | Jun 22, 07:30 UTC | 2h 35m |
| 2026-06-21 | AHY023 | - | Jun 21, 11:05 UTC | Jun 22, 07:30 UTC | 20h 25m |
| 2026-06-21 | AHY023 | - | Jun 21, 09:49 UTC | Jun 22, 07:30 UTC | 21h 40m |
| 2026-06-21 | AHY023 | - | Jun 21, 05:44 UTC | Jun 21, 08:25 UTC | 2h 40m |
| 2026-06-20 | AHY023 | - | Jun 20, 11:05 UTC | Jun 21, 08:25 UTC | 21h 20m |
| 2026-06-20 | AHY023 | - | Jun 20, 09:59 UTC | Jun 21, 08:25 UTC | 22h 25m |
| 2026-06-20 | AHY8041 | - | Jun 20, 05:59 UTC | Jun 20, 08:34 UTC | 2h 35m |
| 2026-06-19 | AHY024 | - | Jun 19, 08:34 UTC | Jun 19, 10:35 UTC | 2h 0m |
| 2026-06-19 | AHY023 | - | Jun 19, 04:39 UTC | Jun 19, 07:25 UTC | 2h 45m |
| 2026-06-18 | AHY023 | - | Jun 18, 11:50 UTC | Jun 19, 07:25 UTC | 19h 34m |
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-AZ04 page for operator, model, and routing details .