sensors Mode-S transponder
600865
ICAO 24-bit transponder address · allocated to Azerbaijan
Currently assigned to 4K-AZ101 · ILYUSHIN Il-76/82
- Hex
- 600865
- Octal
- 30004145
- Decimal
- 6,293,605
- Country
- AZ
- Tail
- 4K-AZ101
- Type
- IL76
- Flights observed
- 40
- Distinct callsigns
- 20
- Country
- AZ
- Last broadcast
- 11d ago
Last known position
Country allocation
The ICAO 24-bit address 600865 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 |
|---|---|---|---|
| AZQ4643 | - | 3 | 2026-05-19 |
| AZQ4113 | - | 3 | 2026-04-28 |
| AZQ881F | - | 2 | 2026-05-06 |
| AZQ880F | - | 2 | 2026-05-02 |
| AZQ6161 | - | 2 | 2026-05-22 |
| AZQ4101 | - | 2 | 2026-04-16 |
| AZQ267 | - | 2 | 2026-04-15 |
| AZQ8881 | - | 1 | 2026-05-05 |
| AZQ8880 | - | 1 | 2026-05-04 |
| AZQ6162 | - | 1 | 2026-05-22 |
| AZQ4672 | - | 1 | 2026-05-08 |
| AZQ4671 | Silk Way Airlines | 1 | 2026-05-08 |
| AZQ4644 | Silk Way Airlines | 1 | 2026-05-20 |
| AZQ4633 | - | 1 | 2026-05-19 |
| AZQ4624 | - | 1 | 2026-05-18 |
| AZQ4623 | - | 1 | 2026-05-18 |
| AZQ4622 | Silk Way Airlines | 1 | 2026-04-22 |
| AZQ4621 | Silk Way Airlines | 1 | 2026-04-22 |
| AZQ4614 | - | 1 | 2026-05-14 |
| AZQ4613 | - | 1 | 2026-05-14 |
Recent flights last 40
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-22 | AZQ6162 | - | May 22, 07:05 UTC | May 22, 10:45 UTC | 3h 40m |
| 2026-05-22 | AZQ6161 | - | May 22, 01:10 UTC | May 22, 04:50 UTC | 3h 40m |
| 2026-05-20 | AZQ4644 | TLV → KGL | May 20, 11:20 UTC | May 20, 13:55 UTC | 2h 35m |
| 2026-05-19 | AZQ4643 | - | May 19, 13:20 UTC | May 20, 08:30 UTC | 19h 11m |
| 2026-05-19 | AZQ4643 | - | May 19, 11:20 UTC | May 20, 08:30 UTC | 21h 11m |
| 2026-05-19 | AZQ4643 | TLV → TLV | May 19, 11:00 UTC | May 20, 08:30 UTC | 21h 31m |
| 2026-05-19 | AZQ4633 | - | May 19, 04:55 UTC | May 19, 07:40 UTC | 2h 45m |
| 2026-05-18 | AZQ4624 | - | May 18, 13:20 UTC | May 18, 15:50 UTC | 2h 30m |
| 2026-05-18 | AZQ4623 | - | May 18, 05:50 UTC | May 18, 08:50 UTC | 3h 0m |
| 2026-05-14 | AZQ4614 | - | May 14, 10:31 UTC | May 14, 13:20 UTC | 2h 50m |
| 2026-05-14 | AZQ4613 | - | May 14, 04:30 UTC | May 14, 07:55 UTC | 3h 25m |
| 2026-05-08 | AZQ4672 | - | May 8, 10:44 UTC | May 8, 13:45 UTC | 3h 0m |
| 2026-05-08 | AZQ4671 | GYD → GYD | May 8, 05:44 UTC | May 8, 07:55 UTC | 2h 10m |
| 2026-05-06 | AZQ881F | - | May 6, 07:20 UTC | May 6, 09:55 UTC | 2h 35m |
| 2026-05-05 | AZQ8881 | - | May 5, 14:10 UTC | May 5, 16:15 UTC | 2h 5m |
| 2026-05-05 | AZQ881F | - | May 5, 10:50 UTC | May 5, 12:35 UTC | 1h 45m |
| 2026-05-04 | AZQ8880 | - | May 4, 06:15 UTC | May 4, 08:30 UTC | 2h 15m |
| 2026-05-02 | AZQ880F | - | May 2, 23:15 UTC | May 3, 01:25 UTC | 2h 10m |
| 2026-05-02 | AZQ880F | - | May 2, 06:15 UTC | May 2, 08:05 UTC | 1h 50m |
| 2026-04-28 | AZQ4114 | - | Apr 28, 21:10 UTC | Apr 28, 23:35 UTC | 2h 25m |
| 2026-04-28 | AZQ4113 | - | Apr 28, 19:35 UTC | Apr 28, 19:45 UTC | 10m |
| 2026-04-28 | AZQ4113 | - | Apr 28, 16:55 UTC | Apr 28, 18:40 UTC | 1h 45m |
| 2026-04-27 | AZQ4113 | - | Apr 27, 19:20 UTC | Apr 28, 18:40 UTC | 23h 20m |
| 2026-04-27 | AZQ4112 | LEJ → GYD | Apr 27, 17:30 UTC | Apr 28, 17:15 UTC | 23h 45m |
| 2026-04-27 | AZQ4111 | GYD → LEJ | Apr 27, 10:10 UTC | Apr 27, 12:50 UTC | 2h 40m |
| 2026-04-26 | AZQ4224 | - | Apr 26, 01:10 UTC | Apr 26, 01:50 UTC | 40m |
| 2026-04-24 | AZQ4223 | - | Apr 24, 09:15 UTC | Apr 25, 00:25 UTC | 15h 10m |
| 2026-04-23 | AZQ4222 | MAA → MCT | Apr 23, 22:35 UTC | Apr 24, 06:55 UTC | 8h 20m |
| 2026-04-22 | AZQ4221 | GYD → MAA | Apr 22, 23:55 UTC | Apr 23, 23:10 UTC | 23h 15m |
| 2026-04-22 | AZQ4622 | ETM → GYD | Apr 22, 11:00 UTC | Apr 23, 00:55 UTC | 13h 55m |
| 2026-04-22 | AZQ4621 | GYD → VDA | Apr 22, 05:05 UTC | Apr 22, 08:20 UTC | 3h 15m |
| 2026-04-21 | AZQ4442 | - | Apr 21, 21:15 UTC | Apr 22, 00:45 UTC | 3h 30m |
| 2026-04-21 | AZQ4441 | - | Apr 21, 08:05 UTC | Apr 21, 19:50 UTC | 11h 45m |
| 2026-04-20 | AZQ6161 | GBB → BTS | Apr 20, 14:55 UTC | Apr 20, 19:05 UTC | 4h 10m |
| 2026-04-20 | AZQ4102 | - | Apr 20, 07:55 UTC | Apr 20, 10:15 UTC | 2h 20m |
| 2026-04-16 | AZQ4101 | - | Apr 16, 03:49 UTC | Apr 16, 04:14 UTC | 25m |
| 2026-04-16 | AZQ4101 | - | Apr 16, 01:35 UTC | Apr 16, 03:00 UTC | 1h 25m |
| 2026-04-15 | AZQ268 | - | Apr 15, 15:05 UTC | Apr 15, 15:50 UTC | 45m |
| 2026-04-15 | AZQ267 | - | Apr 15, 07:10 UTC | Apr 15, 07:20 UTC | 10m |
| 2026-04-15 | AZQ267 | - | Apr 15, 05:40 UTC | Apr 15, 06:55 UTC | 1h 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-AZ101 page for operator, model, and routing details .