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
- 61
- Distinct callsigns
- 18
- Country
- AZ
- Last broadcast
- 6h ago
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 18 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| AHY805 | Azerbaijan Airlines | 9 | 2026-05-27 |
| AHY075 | Azerbaijan Airlines | 9 | 2026-05-25 |
| AHY121 | Azerbaijan Airlines | 6 | 2026-05-16 |
| AHY021 | Azerbaijan Airlines | 6 | 2026-05-29 |
| AHY181 | Azerbaijan Airlines | 5 | 2026-05-07 |
| AHY809 | Azerbaijan Airlines | 4 | 2026-05-20 |
| AHY5218 | - | 4 | 2026-05-18 |
| AHY122 | Azerbaijan Airlines | 4 | 2026-05-16 |
| AHY076 | Azerbaijan Airlines | 3 | 2026-05-25 |
| AHY807 | Azerbaijan Airlines | 2 | 2026-04-22 |
| AHY077 | Azerbaijan Airlines | 2 | 2026-05-23 |
| AHY810 | Azerbaijan Airlines | 1 | 2026-04-13 |
| AHY5217 | Azerbaijan Airlines | 1 | 2026-05-16 |
| AHY296 | - | 1 | 2026-05-29 |
| AHY295 | - | 1 | 2026-05-29 |
| AHY022 | Azerbaijan Airlines | 1 | 2026-05-27 |
| AHY008 | - | 1 | 2026-04-28 |
| AHY007 | - | 1 | 2026-04-28 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | AHY296 | - | May 29, 22:25 UTC | May 29, 22:40 UTC | 15m |
| 2026-05-29 | AHY295 | - | May 29, 20:25 UTC | May 29, 20:50 UTC | 25m |
| 2026-05-29 | AHY021 | GYD → TLV | May 29, 04:50 UTC | May 29, 05:05 UTC | 15m |
| 2026-05-27 | AHY805 | GYD → VKO | May 27, 19:35 UTC | May 27, 19:55 UTC | 20m |
| 2026-05-27 | AHY022 | TLV → GYD | May 27, 09:40 UTC | May 27, 11:50 UTC | 2h 10m |
| 2026-05-27 | AHY021 | GYD → TLV | May 27, 05:35 UTC | May 27, 08:10 UTC | 2h 35m |
| 2026-05-25 | AHY076 | IST → GYD | May 25, 10:05 UTC | May 25, 23:49 UTC | 13h 45m |
| 2026-05-25 | AHY075 | GYD → IST | May 25, 06:00 UTC | May 25, 07:10 UTC | 1h 10m |
| 2026-05-24 | AHY075 | GYD → IST | May 24, 06:20 UTC | May 25, 06:15 UTC | 23h 55m |
| 2026-05-23 | AHY077 | GYD → IST | May 23, 16:15 UTC | May 24, 06:45 UTC | 14h 30m |
| 2026-05-22 | AHY021 | GYD → TLV | May 22, 20:15 UTC | May 23, 08:15 UTC | 12h 0m |
| 2026-05-22 | AHY077 | GYD → IST | May 22, 17:05 UTC | May 22, 17:40 UTC | 35m |
| 2026-05-20 | AHY809 | GYD → VKO | May 20, 17:50 UTC | May 20, 18:35 UTC | 45m |
| 2026-05-18 | AHY5218 | - | May 18, 00:20 UTC | May 18, 19:15 UTC | 18h 54m |
| 2026-05-17 | AHY5218 | - | May 17, 22:40 UTC | May 18, 19:15 UTC | 20h 34m |
| 2026-05-17 | AHY5218 | - | May 17, 18:20 UTC | May 18, 18:15 UTC | 23h 55m |
| 2026-05-17 | AHY5218 | - | May 17, 15:35 UTC | May 18, 01:20 UTC | 9h 45m |
| 2026-05-16 | AHY5217 | GYD → JED | May 16, 18:20 UTC | May 17, 18:15 UTC | 23h 55m |
| 2026-05-16 | AHY122 | KVD → LED | May 16, 12:21 UTC | May 16, 18:40 UTC | 6h 20m |
| 2026-05-16 | AHY122 | KVD → LED | May 16, 12:11 UTC | May 16, 12:16 UTC | 5m |
| 2026-05-16 | AHY121 | LED → KVD | May 16, 09:45 UTC | May 16, 10:05 UTC | 20m |
| 2026-05-16 | AHY121 | LED → KVD | May 16, 07:35 UTC | May 16, 08:16 UTC | 40m |
| 2026-05-15 | AHY805 | GYD → VKO | May 15, 19:45 UTC | May 15, 20:30 UTC | 45m |
| 2026-05-15 | AHY805 | GYD → VKO | May 15, 18:55 UTC | May 15, 19:10 UTC | 15m |
| 2026-05-15 | AHY021 | GYD → TLV | May 15, 04:35 UTC | May 15, 07:05 UTC | 2h 30m |
| 2026-05-14 | AHY805 | GYD → VKO | May 14, 19:40 UTC | May 14, 20:00 UTC | 20m |
| 2026-05-14 | AHY076 | IST → GYD | May 14, 10:55 UTC | May 14, 18:40 UTC | 7h 45m |
| 2026-05-13 | AHY075 | GYD → IST | May 13, 17:05 UTC | May 14, 07:25 UTC | 14h 20m |
| 2026-05-13 | AHY021 | GYD → TLV | May 13, 05:25 UTC | May 13, 17:40 UTC | 12h 15m |
| 2026-05-12 | AHY021 | GYD → TLV | May 12, 17:10 UTC | May 13, 06:05 UTC | 12h 55m |
| 2026-05-11 | AHY805 | GYD → VKO | May 11, 18:20 UTC | May 12, 17:45 UTC | 23h 25m |
| 2026-05-11 | AHY122 | KVD → LED | May 11, 13:10 UTC | May 11, 18:50 UTC | 5h 41m |
| 2026-05-10 | AHY121 | LED → KVD | May 10, 16:20 UTC | May 11, 10:35 UTC | 18h 15m |
| 2026-05-10 | AHY121 | LED → KVD | May 10, 16:14 UTC | May 11, 10:35 UTC | 18h 20m |
| 2026-05-10 | AHY121 | LED → KVD | May 10, 10:19 UTC | May 11, 10:15 UTC | 23h 55m |
| 2026-05-10 | AHY122 | KVD → LED | May 10, 10:00 UTC | May 11, 08:15 UTC | 22h 15m |
| 2026-05-09 | AHY121 | LED → KVD | May 9, 18:15 UTC | May 10, 07:15 UTC | 13h 0m |
| 2026-05-08 | AHY805 | GYD → VKO | May 8, 18:30 UTC | May 9, 18:15 UTC | 23h 45m |
| 2026-05-08 | AHY805 | GYD → VKO | May 8, 10:25 UTC | May 8, 18:50 UTC | 8h 25m |
| 2026-05-07 | AHY181 | GYD → DME | May 7, 19:40 UTC | May 8, 10:25 UTC | 14h 45m |
| 2026-05-01 | AHY075 | GYD → IST | May 1, 05:05 UTC | May 1, 22:20 UTC | 17h 15m |
| 2026-04-30 | AHY075 | GYD → IST | Apr 30, 10:50 UTC | May 1, 06:25 UTC | 19h 35m |
| 2026-04-29 | AHY809 | GYD → VKO | Apr 29, 18:05 UTC | Apr 30, 11:00 UTC | 16h 54m |
| 2026-04-29 | AHY076 | IST → GYD | Apr 29, 10:30 UTC | Apr 29, 22:45 UTC | 12h 15m |
| 2026-04-28 | AHY008 | - | Apr 28, 21:25 UTC | Apr 29, 07:24 UTC | 10h 0m |
| 2026-04-28 | AHY007 | - | Apr 28, 14:15 UTC | Apr 28, 19:45 UTC | 5h 30m |
| 2026-04-27 | AHY181 | GYD → DME | Apr 27, 01:25 UTC | Apr 27, 07:20 UTC | 5h 55m |
| 2026-04-26 | AHY181 | GYD → DME | Apr 26, 09:50 UTC | Apr 27, 07:20 UTC | 21h 30m |
| 2026-04-25 | AHY075 | GYD → IST | Apr 25, 12:20 UTC | Apr 26, 06:25 UTC | 18h 5m |
| 2026-04-25 | AHY075 | GYD → IST | Apr 25, 11:00 UTC | Apr 26, 06:25 UTC | 19h 25m |
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 .