sensors Mode-S transponder
600B20
ICAO 24-bit transponder address · allocated to Azerbaijan
Currently assigned to 4K-SW800 · BOEING 747-400
- Hex
- 600B20
- Octal
- 30005440
- Decimal
- 6,294,304
- Country
- AZ
- Tail
- 4K-SW800
- Type
- B744
- Flights observed
- 114
- Distinct callsigns
- 20
- Country
- AZ
- Last broadcast
- 1h ago
Last known position
Country allocation
The ICAO 24-bit address 600B20 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 |
|---|---|---|---|
| AZG3958 | - | 16 | 2026-04-17 |
| AZG572 | Sakaviaservice | 5 | 2026-05-26 |
| AZG4872 | Sakaviaservice | 5 | 2026-04-18 |
| AZG692 | Sakaviaservice | 4 | 2026-05-18 |
| AZG691 | - | 3 | 2026-05-26 |
| AZG3959 | - | 3 | 2026-04-14 |
| AZG3823 | - | 3 | 2026-05-07 |
| AZG1922 | Sakaviaservice | 3 | 2026-04-16 |
| AZG903 | - | 2 | 2026-05-09 |
| AZG8892 | - | 2 | 2026-05-22 |
| AZG8321 | Sakaviaservice | 2 | 2026-05-29 |
| AZG8116 | Sakaviaservice | 2 | 2026-04-25 |
| AZG712 | Sakaviaservice | 2 | 2026-05-19 |
| AZG632 | Sakaviaservice | 2 | 2026-05-09 |
| AZG631 | - | 2 | 2026-05-08 |
| AZG5790 | Sakaviaservice | 2 | 2026-05-16 |
| AZG4871 | Sakaviaservice | 2 | 2026-04-24 |
| AZG3824 | - | 2 | 2026-05-08 |
| AZG3320 | - | 2 | 2026-05-13 |
| AZG280 | - | 2 | 2026-04-14 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | AZG8322 | - | May 29, 22:30 UTC | May 30, 04:00 UTC | 5h 30m |
| 2026-05-29 | AZG8321 | GYD → BLL | May 29, 01:45 UTC | May 29, 18:10 UTC | 16h 25m |
| 2026-05-28 | AZG8321 | GYD → BLL | May 28, 23:55 UTC | May 29, 18:10 UTC | 18h 15m |
| 2026-05-28 | AZG1923 | HKG → HKG | May 28, 23:05 UTC | May 28, 23:15 UTC | 10m |
| 2026-05-28 | AZG147 | - | May 28, 15:25 UTC | May 28, 15:55 UTC | 30m |
| 2026-05-27 | AZG6187 | - | May 27, 20:35 UTC | May 28, 08:25 UTC | 11h 50m |
| 2026-05-27 | AZG5131 | STR → MCT | May 27, 02:14 UTC | May 27, 16:50 UTC | 14h 35m |
| 2026-05-26 | AZG572 | HKG → HKG | May 26, 23:19 UTC | May 26, 23:35 UTC | 15m |
| 2026-05-26 | AZG691 | - | May 26, 17:50 UTC | May 26, 18:19 UTC | 30m |
| 2026-05-26 | AZG691 | - | May 26, 12:20 UTC | May 26, 15:49 UTC | 3h 30m |
| 2026-05-24 | AZG394 | BHX → GYD | May 24, 20:25 UTC | May 24, 23:35 UTC | 3h 10m |
| 2026-05-24 | AZG292 | - | May 24, 05:05 UTC | May 24, 13:35 UTC | 8h 30m |
| 2026-05-24 | AZG6118 | IAH → GYD | May 24, 01:25 UTC | May 24, 02:55 UTC | 1h 30m |
| 2026-05-23 | AZG6117 | IAH → LUX | May 23, 05:00 UTC | May 23, 23:15 UTC | 18h 16m |
| 2026-05-22 | AZG8892 | - | May 22, 16:20 UTC | May 23, 09:05 UTC | 16h 44m |
| 2026-05-22 | AZG8892 | - | May 22, 10:10 UTC | May 23, 09:05 UTC | 22h 55m |
| 2026-05-22 | AZG7730 | - | May 22, 08:05 UTC | May 23, 08:00 UTC | 23h 54m |
| 2026-05-22 | AZG272 | MXP → GYD | May 22, 06:25 UTC | May 23, 06:00 UTC | 23h 34m |
| 2026-05-21 | AZG271 | GYD → MXP | May 21, 23:15 UTC | May 22, 02:55 UTC | 3h 40m |
| 2026-05-21 | AZG219 | TLV → GYD | May 21, 01:15 UTC | May 21, 19:00 UTC | 17h 45m |
| 2026-05-20 | AZG219 | TLV → GYD | May 20, 20:05 UTC | May 21, 19:00 UTC | 22h 55m |
| 2026-05-20 | AZG129 | ICN → GYD | May 20, 19:50 UTC | May 21, 17:40 UTC | 21h 50m |
| 2026-05-20 | AZG128 | GYD → ICN | May 20, 16:25 UTC | May 20, 16:50 UTC | 25m |
| 2026-05-20 | AZG232 | HHN → GYD | May 20, 02:00 UTC | May 20, 15:50 UTC | 13h 51m |
| 2026-05-19 | AZG712 | LGG → GYD | May 19, 06:40 UTC | May 19, 16:50 UTC | 10h 10m |
| 2026-05-18 | AZG711 | - | May 18, 22:25 UTC | May 19, 02:40 UTC | 4h 15m |
| 2026-05-18 | AZG426 | DWC → DWC | May 18, 14:30 UTC | May 18, 15:00 UTC | 30m |
| 2026-05-18 | AZG692 | HKG → GYD | May 18, 05:30 UTC | May 18, 08:35 UTC | 3h 5m |
| 2026-05-18 | AZG692 | HKG → GYD | May 18, 02:45 UTC | May 18, 02:55 UTC | 10m |
| 2026-05-17 | AZG5792 | IAH → HHN | May 17, 06:45 UTC | May 17, 22:05 UTC | 15h 20m |
| 2026-05-17 | AZG5791 | HSV → LAX | May 17, 01:50 UTC | May 17, 04:05 UTC | 2h 15m |
| 2026-05-16 | AZG5790 | PIK → PIK | May 16, 20:30 UTC | May 16, 23:15 UTC | 2h 45m |
| 2026-05-16 | AZG5790 | PIK → PIK | May 16, 00:05 UTC | May 16, 23:15 UTC | 23h 10m |
| 2026-05-15 | AZG5789 | IAH → HHN | May 15, 16:55 UTC | May 16, 01:50 UTC | 8h 55m |
| 2026-05-14 | AZG5788 | HHN → GYD | May 14, 14:45 UTC | May 15, 10:00 UTC | 19h 15m |
| 2026-05-13 | AZG9804 | EBL → GYD | May 13, 16:05 UTC | May 14, 15:20 UTC | 23h 15m |
| 2026-05-13 | AZG3320 | - | May 13, 08:05 UTC | May 13, 16:40 UTC | 8h 35m |
| 2026-05-12 | AZG3320 | - | May 12, 18:40 UTC | May 13, 16:40 UTC | 22h 0m |
| 2026-05-11 | AZG692 | HKG → GYD | May 11, 16:15 UTC | May 11, 19:50 UTC | 3h 36m |
| 2026-05-11 | AZG692 | HKG → GYD | May 11, 13:35 UTC | May 11, 13:50 UTC | 15m |
| 2026-05-11 | AZG691 | - | May 11, 08:20 UTC | May 11, 09:05 UTC | 45m |
| 2026-05-10 | AZG124 | ICN → GYD | May 10, 13:40 UTC | May 10, 13:55 UTC | 15m |
| 2026-05-10 | AZG904 | NRT → GYD | May 10, 08:45 UTC | May 10, 10:45 UTC | 2h 0m |
| 2026-05-09 | AZG903 | - | May 9, 11:00 UTC | May 10, 05:10 UTC | 18h 10m |
| 2026-05-09 | AZG903 | - | May 9, 09:45 UTC | May 10, 05:10 UTC | 19h 25m |
| 2026-05-09 | AZG632 | SIN → GYD | May 9, 06:50 UTC | May 10, 05:10 UTC | 22h 20m |
| 2026-05-08 | AZG631 | - | May 8, 08:05 UTC | May 9, 02:40 UTC | 18h 35m |
| 2026-05-08 | AZG3824 | - | May 8, 06:04 UTC | May 9, 02:40 UTC | 20h 35m |
| 2026-05-07 | AZG3823 | - | May 7, 22:00 UTC | May 8, 02:09 UTC | 4h 9m |
| 2026-05-06 | AZG273 | JFK → MXP | May 6, 19:40 UTC | May 7, 10:40 UTC | 15h 0m |
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-SW800 page for operator, model, and routing details .