sensors Mode-S transponder
600851
ICAO 24-bit transponder address · allocated to Azerbaijan
Currently assigned to 4K-AZ81 · BOEING 767-300
- Hex
- 600851
- Octal
- 30004121
- Decimal
- 6,293,585
- Country
- AZ
- Tail
- 4K-AZ81
- Type
- B763
- Flights observed
- 136
- Distinct callsigns
- 20
- Country
- AZ
- Last broadcast
- Jul 26, 22:15 UTC
Last known position
Country allocation
The ICAO 24-bit address 600851 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 |
|---|---|---|---|
| AHY121 | Azerbaijan Airlines | 19 | 2026-06-23 |
| AHY075 | Azerbaijan Airlines | 17 | 2026-07-26 |
| AHY021 | - | 13 | 2026-07-18 |
| AHY805 | Azerbaijan Airlines | 9 | 2026-05-27 |
| AHY122 | Azerbaijan Airlines | 9 | 2026-06-24 |
| AHY023 | Azerbaijan Airlines | 9 | 2026-07-25 |
| AHY076 | Azerbaijan Airlines | 7 | 2026-07-26 |
| AHY022 | Azerbaijan Airlines | 6 | 2026-07-18 |
| AHY809 | - | 5 | 2026-07-01 |
| AHY5239 | - | 5 | 2026-06-05 |
| AHY181 | Azerbaijan Airlines | 5 | 2026-05-07 |
| AHY5218 | - | 4 | 2026-05-18 |
| AHY5246 | Azerbaijan Airlines | 3 | 2026-06-07 |
| AHY077 | - | 3 | 2026-06-29 |
| AHY024 | Azerbaijan Airlines | 3 | 2026-07-20 |
| AHY008 | - | 3 | 2026-06-02 |
| AHY007 | - | 3 | 2026-06-02 |
| AHY807 | Azerbaijan Airlines | 2 | 2026-04-22 |
| AHY8003 | Azerbaijan Airlines | 2 | 2026-07-21 |
| AHY182 | Azerbaijan Airlines | 2 | 2026-06-27 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | AHY076 | IST → GYD | Jul 26, 09:15 UTC | Jul 26, 22:15 UTC | 13h 0m |
| 2026-07-26 | AHY075 | GYD → IST | Jul 26, 05:10 UTC | Jul 26, 07:25 UTC | 2h 16m |
| 2026-07-25 | AHY075 | GYD → IST | Jul 25, 10:20 UTC | Jul 26, 07:25 UTC | 21h 6m |
| 2026-07-25 | AHY075 | GYD → IST | Jul 25, 09:10 UTC | Jul 26, 07:25 UTC | 22h 16m |
| 2026-07-25 | AHY023 | GYD → BJV | Jul 25, 04:45 UTC | Jul 25, 07:30 UTC | 2h 45m |
| 2026-07-24 | AHY023 | GYD → BJV | Jul 24, 10:20 UTC | Jul 25, 07:30 UTC | 21h 10m |
| 2026-07-24 | AHY023 | GYD → BJV | Jul 24, 08:45 UTC | Jul 25, 07:30 UTC | 22h 45m |
| 2026-07-24 | AHY023 | GYD → BJV | Jul 24, 04:30 UTC | Jul 24, 07:10 UTC | 2h 40m |
| 2026-07-21 | AHY8003 | GYD → ESB | Jul 21, 16:35 UTC | Jul 22, 10:25 UTC | 17h 50m |
| 2026-07-21 | AHY8003 | GYD → ESB | Jul 21, 08:50 UTC | Jul 22, 05:25 UTC | 20h 35m |
| 2026-07-20 | AHY024 | BJV → GYD | Jul 20, 09:15 UTC | Jul 20, 11:20 UTC | 2h 5m |
| 2026-07-20 | AHY023 | GYD → BJV | Jul 20, 04:45 UTC | Jul 20, 07:10 UTC | 2h 25m |
| 2026-07-18 | AHY332 | TLV → GYD | Jul 18, 20:55 UTC | Jul 18, 22:55 UTC | 2h 0m |
| 2026-07-18 | AHY331 | GYD → TLV | Jul 18, 17:00 UTC | Jul 18, 19:35 UTC | 2h 35m |
| 2026-07-18 | AHY022 | TLV → GYD | Jul 18, 09:25 UTC | Jul 18, 11:30 UTC | 2h 5m |
| 2026-07-18 | AHY021 | - | Jul 18, 05:25 UTC | Jul 18, 08:00 UTC | 2h 35m |
| 2026-07-17 | AHY021 | - | Jul 17, 10:20 UTC | Jul 18, 08:00 UTC | 21h 41m |
| 2026-07-17 | AHY021 | TLV → TLV | Jul 17, 08:59 UTC | Jul 18, 08:00 UTC | 23h 1m |
| 2026-07-17 | AHY021 | - | Jul 17, 04:35 UTC | Jul 17, 07:25 UTC | 2h 50m |
| 2026-07-15 | AHY024 | - | Jul 15, 09:05 UTC | Jul 15, 11:05 UTC | 2h 0m |
| 2026-07-15 | AHY023 | - | Jul 15, 04:40 UTC | Jul 15, 06:00 UTC | 1h 20m |
| 2026-07-14 | AHY023 | - | Jul 14, 08:20 UTC | Jul 15, 06:00 UTC | 21h 39m |
| 2026-07-14 | AHY023 | - | Jul 14, 07:50 UTC | Jul 15, 06:00 UTC | 22h 9m |
| 2026-07-10 | AHY076 | - | Jul 10, 10:10 UTC | Jul 10, 11:50 UTC | 1h 40m |
| 2026-07-10 | AHY075 | - | Jul 10, 05:50 UTC | Jul 10, 07:15 UTC | 1h 25m |
| 2026-07-02 | AHY024 | - | Jul 2, 08:50 UTC | Jul 2, 10:50 UTC | 2h 0m |
| 2026-07-02 | AHY023 | - | Jul 2, 04:40 UTC | Jul 2, 07:15 UTC | 2h 35m |
| 2026-07-01 | AHY809 | - | Jul 1, 20:35 UTC | Jul 1, 20:45 UTC | 10m |
| 2026-07-01 | AHY022 | TLV → GYD | Jul 1, 09:35 UTC | Jul 1, 11:05 UTC | 1h 30m |
| 2026-06-30 | AHY076 | - | Jun 30, 10:20 UTC | Jul 1, 06:10 UTC | 19h 50m |
| 2026-06-30 | AHY076 | - | Jun 30, 09:25 UTC | Jul 1, 06:10 UTC | 20h 45m |
| 2026-06-29 | AHY075 | - | Jun 29, 20:09 UTC | Jun 30, 07:30 UTC | 11h 21m |
| 2026-06-29 | AHY077 | - | Jun 29, 18:10 UTC | Jun 29, 18:30 UTC | 20m |
| 2026-06-29 | AHY022 | TLV → GYD | Jun 29, 09:50 UTC | Jun 29, 17:24 UTC | 7h 35m |
| 2026-06-29 | AHY021 | GYD → TLV | Jun 29, 05:45 UTC | Jun 29, 08:14 UTC | 2h 30m |
| 2026-06-27 | AHY182 | DME → GYD | Jun 27, 10:40 UTC | Jun 27, 11:04 UTC | 25m |
| 2026-06-24 | AHY122 | KVD → LED | Jun 24, 11:59 UTC | Jun 24, 14:04 UTC | 2h 5m |
| 2026-06-23 | AHY121 | LED → KVD | Jun 23, 18:10 UTC | Jun 24, 10:14 UTC | 16h 5m |
| 2026-06-23 | AHY121 | LED → KVD | Jun 23, 12:20 UTC | Jun 24, 10:14 UTC | 21h 55m |
| 2026-06-23 | AHY121 | LED → KVD | Jun 23, 11:49 UTC | Jun 24, 10:14 UTC | 22h 25m |
| 2026-06-22 | AHY121 | LED → KVD | Jun 22, 16:20 UTC | Jun 23, 10:19 UTC | 18h 0m |
| 2026-06-22 | AHY121 | LED → KVD | Jun 22, 16:05 UTC | Jun 23, 10:19 UTC | 18h 15m |
| 2026-06-21 | AHY122 | KVD → LED | Jun 21, 11:59 UTC | Jun 21, 13:15 UTC | 1h 15m |
| 2026-06-21 | AHY121 | LED → KVD | Jun 21, 07:34 UTC | Jun 21, 08:25 UTC | 50m |
| 2026-06-19 | AHY122 | KVD → LED | Jun 19, 11:49 UTC | Jun 19, 12:34 UTC | 45m |
| 2026-06-19 | AHY121 | LED → KVD | Jun 19, 07:39 UTC | Jun 19, 10:24 UTC | 2h 45m |
| 2026-06-18 | AHY121 | LED → KVD | Jun 18, 12:20 UTC | Jun 19, 10:24 UTC | 22h 4m |
| 2026-06-18 | AHY121 | LED → KVD | Jun 18, 12:05 UTC | Jun 19, 10:14 UTC | 22h 9m |
| 2026-06-17 | AHY121 | LED → KVD | Jun 17, 22:10 UTC | Jun 18, 10:35 UTC | 12h 25m |
| 2026-06-17 | AHY121 | LED → KVD | Jun 17, 12:20 UTC | Jun 18, 10:35 UTC | 22h 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-AZ81 page for operator, model, and routing details .