sensors Mode-S transponder
600852
ICAO 24-bit transponder address · allocated to Azerbaijan
Currently assigned to 4K-AZ82 · BOEING 767-300
- Hex
- 600852
- Octal
- 30004122
- Decimal
- 6,293,586
- Country
- AZ
- Tail
- 4K-AZ82
- Type
- B763
- Flights observed
- 179
- Distinct callsigns
- 20
- Country
- AZ
- Last broadcast
- Jul 26, 21:35 UTC
Last known position
Country allocation
The ICAO 24-bit address 600852 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 | 17 | 2026-06-28 |
| AHY809 | Azerbaijan Airlines | 14 | 2026-07-22 |
| AHY805 | - | 13 | 2026-06-24 |
| AHY075 | Azerbaijan Airlines | 13 | 2026-07-19 |
| AHY807 | Azerbaijan Airlines | 11 | 2026-07-25 |
| AHY803 | Azerbaijan Airlines | 9 | 2026-06-29 |
| AHY076 | - | 9 | 2026-07-19 |
| AHY122 | Azerbaijan Airlines | 8 | 2026-06-28 |
| AHY021 | Azerbaijan Airlines | 8 | 2026-06-29 |
| AHY810 | Azerbaijan Airlines | 7 | 2026-07-19 |
| AHY022 | Azerbaijan Airlines | 6 | 2026-06-05 |
| AHY808 | Azerbaijan Airlines | 5 | 2026-07-26 |
| AHY181 | Azerbaijan Airlines | 5 | 2026-07-18 |
| AHY007 | - | 5 | 2026-06-30 |
| AHY806 | - | 4 | 2026-06-24 |
| AHY182 | Azerbaijan Airlines | 4 | 2026-07-20 |
| AHY077 | Azerbaijan Airlines | 4 | 2026-05-30 |
| AHY024 | Azerbaijan Airlines | 4 | 2026-07-23 |
| AHY023 | Azerbaijan Airlines | 4 | 2026-07-22 |
| AHY5220 | - | 3 | 2026-05-18 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | AHY808 | VKO → GYD | Jul 26, 12:30 UTC | Jul 26, 21:35 UTC | 9h 5m |
| 2026-07-25 | AHY807 | GYD → VKO | Jul 25, 21:05 UTC | Jul 26, 07:40 UTC | 10h 36m |
| 2026-07-23 | AHY024 | BJV → GYD | Jul 23, 09:00 UTC | Jul 23, 10:55 UTC | 1h 55m |
| 2026-07-22 | AHY023 | GYD → BJV | Jul 22, 22:15 UTC | Jul 23, 07:20 UTC | 9h 5m |
| 2026-07-22 | AHY809 | GYD → VKO | Jul 22, 19:20 UTC | Jul 22, 20:40 UTC | 1h 20m |
| 2026-07-21 | AHY809 | GYD → VKO | Jul 21, 20:15 UTC | Jul 21, 20:40 UTC | 25m |
| 2026-07-21 | AHY808 | VKO → GYD | Jul 21, 10:05 UTC | Jul 21, 10:20 UTC | 15m |
| 2026-07-21 | AHY807 | GYD → VKO | Jul 21, 07:20 UTC | Jul 21, 07:55 UTC | 35m |
| 2026-07-21 | AHY807 | GYD → VKO | Jul 21, 06:30 UTC | Jul 21, 06:50 UTC | 20m |
| 2026-07-20 | AHY182 | DME → GYD | Jul 20, 10:35 UTC | Jul 21, 06:50 UTC | 20h 15m |
| 2026-07-20 | AHY182 | DME → GYD | Jul 20, 10:20 UTC | Jul 21, 06:50 UTC | 20h 29m |
| 2026-07-19 | AHY810 | VKO → GYD | Jul 19, 23:40 UTC | Jul 20, 08:40 UTC | 9h 0m |
| 2026-07-19 | AHY076 | - | Jul 19, 09:20 UTC | Jul 19, 21:55 UTC | 12h 35m |
| 2026-07-19 | AHY075 | GYD → IST | Jul 19, 05:05 UTC | Jul 19, 07:25 UTC | 2h 20m |
| 2026-07-18 | AHY075 | GYD → IST | Jul 18, 10:40 UTC | Jul 19, 07:25 UTC | 20h 45m |
| 2026-07-18 | AHY181 | GYD → DME | Jul 18, 07:05 UTC | Jul 18, 08:25 UTC | 1h 20m |
| 2026-07-18 | AHY2254 | - | Jul 18, 02:14 UTC | Jul 18, 02:35 UTC | 20m |
| 2026-07-17 | AHY2253 | - | Jul 17, 23:35 UTC | Jul 18, 00:00 UTC | 25m |
| 2026-07-16 | AHY322 | TLV → GYD | Jul 16, 21:55 UTC | Jul 16, 23:25 UTC | 1h 30m |
| 2026-07-16 | AHY321 | - | Jul 16, 04:40 UTC | Jul 16, 20:35 UTC | 15h 55m |
| 2026-07-13 | AHY024 | - | Jul 13, 08:40 UTC | Jul 13, 18:40 UTC | 10h 0m |
| 2026-07-12 | AHY023 | - | Jul 12, 22:40 UTC | Jul 13, 07:05 UTC | 8h 25m |
| 2026-07-12 | AHY809 | - | Jul 12, 19:15 UTC | Jul 12, 20:35 UTC | 1h 20m |
| 2026-07-12 | AHY076 | - | Jul 12, 09:10 UTC | Jul 12, 10:55 UTC | 1h 45m |
| 2026-07-11 | AHY075 | - | Jul 11, 22:15 UTC | Jul 12, 07:20 UTC | 9h 5m |
| 2026-07-11 | AHY809 | - | Jul 11, 19:10 UTC | Jul 11, 20:25 UTC | 1h 15m |
| 2026-07-04 | AHY024 | - | Jul 4, 14:00 UTC | Jul 5, 06:25 UTC | 16h 25m |
| 2026-07-04 | AHY023 | - | Jul 4, 09:55 UTC | Jul 4, 12:25 UTC | 2h 30m |
| 2026-07-03 | AHY076 | - | Jul 3, 10:35 UTC | Jul 4, 10:30 UTC | 23h 55m |
| 2026-07-03 | AHY076 | - | Jul 3, 09:55 UTC | Jul 3, 11:40 UTC | 1h 45m |
| 2026-07-02 | AHY075 | - | Jul 2, 14:15 UTC | Jul 3, 08:10 UTC | 17h 55m |
| 2026-07-01 | AHY181 | - | Jul 1, 22:00 UTC | Jul 2, 12:30 UTC | 14h 30m |
| 2026-07-01 | AHY808 | - | Jul 1, 10:10 UTC | Jul 1, 20:30 UTC | 10h 20m |
| 2026-06-30 | AHY008 | - | Jun 30, 22:05 UTC | Jul 1, 08:05 UTC | 10h 0m |
| 2026-06-30 | AHY007 | TLV → LHR | Jun 30, 09:45 UTC | Jun 30, 20:30 UTC | 10h 45m |
| 2026-06-29 | AHY021 | GYD → TLV | Jun 29, 20:19 UTC | Jun 30, 08:15 UTC | 11h 56m |
| 2026-06-29 | AHY803 | GYD → VKO | Jun 29, 17:19 UTC | Jun 29, 18:34 UTC | 1h 15m |
| 2026-06-28 | AHY122 | KVD → LED | Jun 28, 11:59 UTC | Jun 28, 14:09 UTC | 2h 10m |
| 2026-06-28 | AHY121 | LED → KVD | Jun 28, 07:40 UTC | Jun 28, 10:19 UTC | 2h 40m |
| 2026-06-27 | AHY121 | LED → KVD | Jun 27, 07:59 UTC | Jun 27, 11:14 UTC | 3h 15m |
| 2026-06-26 | AHY121 | LED → KVD | Jun 26, 12:34 UTC | Jun 27, 11:14 UTC | 22h 40m |
| 2026-06-26 | AHY121 | LED → KVD | Jun 26, 12:00 UTC | Jun 27, 10:29 UTC | 22h 30m |
| 2026-06-26 | AHY121 | LED → KVD | Jun 26, 07:45 UTC | Jun 26, 10:20 UTC | 2h 35m |
| 2026-06-25 | AHY122 | KVD → LED | Jun 25, 14:20 UTC | Jun 25, 16:24 UTC | 2h 5m |
| 2026-06-25 | AHY121 | LED → KVD | Jun 25, 06:44 UTC | Jun 25, 12:04 UTC | 5h 20m |
| 2026-06-24 | AHY806 | - | Jun 24, 22:04 UTC | Jun 25, 05:05 UTC | 7h 0m |
| 2026-06-24 | AHY805 | - | Jun 24, 10:19 UTC | Jun 24, 20:24 UTC | 10h 5m |
| 2026-06-24 | AHY807 | - | Jun 24, 07:50 UTC | Jun 24, 08:09 UTC | 20m |
| 2026-06-23 | AHY806 | - | Jun 23, 21:14 UTC | Jun 24, 06:55 UTC | 9h 40m |
| 2026-06-23 | AHY805 | - | Jun 23, 09:40 UTC | Jun 23, 19:34 UTC | 9h 55m |
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-AZ82 page for operator, model, and routing details .