sensors Mode-S transponder
600B21
ICAO 24-bit transponder address · allocated to Azerbaijan
Currently assigned to 4K-SW888 · BOEING 747-400
- Hex
- 600B21
- Octal
- 30005441
- Decimal
- 6,294,305
- Country
- AZ
- Tail
- 4K-SW888
- Type
- B744
- Flights observed
- 98
- Distinct callsigns
- 20
- Country
- AZ
- Last broadcast
- 4h ago
Current position
Country allocation
The ICAO 24-bit address 600B21 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 |
|---|---|---|---|
| AZG7733 | - | 7 | 2026-04-14 |
| AZG6889 | Sakaviaservice | 7 | 2026-04-15 |
| AZG3941 | - | 7 | 2026-04-18 |
| AZG3942 | - | 5 | 2026-04-18 |
| AZG9492 | Sakaviaservice | 3 | 2026-05-26 |
| AZG572 | Sakaviaservice | 3 | 2026-04-20 |
| AZG393 | Sakaviaservice | 3 | 2026-05-17 |
| AZG3236 | Sakaviaservice | 3 | 2026-04-17 |
| AZG1922 | Sakaviaservice | 3 | 2026-05-15 |
| AZG9491 | Sakaviaservice | 2 | 2026-05-29 |
| AZG692 | Sakaviaservice | 2 | 2026-05-15 |
| AZG4882 | Sakaviaservice | 2 | 2026-05-19 |
| AZG423 | Sakaviaservice | 2 | 2026-04-18 |
| AZG394 | Sakaviaservice | 2 | 2026-05-17 |
| AZG3234 | Sakaviaservice | 2 | 2026-05-28 |
| AZG3233 | - | 2 | 2026-05-27 |
| AZG3039 | - | 2 | 2026-05-11 |
| AZG247 | Sakaviaservice | 2 | 2026-05-27 |
| AZG246 | Sakaviaservice | 2 | 2026-05-27 |
| AZG231 | Sakaviaservice | 2 | 2026-05-29 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | AZG9491 | HHN → LAX | May 29, 17:50 UTC | May 29, 20:55 UTC | 3h 5m |
| 2026-05-29 | AZG231 | VIE → HHN | May 29, 10:40 UTC | May 29, 15:00 UTC | 4h 20m |
| 2026-05-28 | AZG3234 | HHN → GYD | May 28, 05:25 UTC | May 28, 09:05 UTC | 3h 40m |
| 2026-05-27 | AZG3233 | - | May 27, 22:20 UTC | May 28, 02:30 UTC | 4h 10m |
| 2026-05-27 | AZG247 | HKG → HKG | May 27, 10:05 UTC | May 27, 10:20 UTC | 15m |
| 2026-05-27 | AZG246 | KGF → HKG | May 27, 07:40 UTC | May 27, 07:55 UTC | 15m |
| 2026-05-26 | AZG9493 | - | May 26, 11:44 UTC | May 27, 05:45 UTC | 18h 0m |
| 2026-05-26 | AZG9492 | LAX → KEF | May 26, 01:20 UTC | May 26, 14:20 UTC | 13h 0m |
| 2026-05-25 | AZG9492 | LAX → KEF | May 25, 22:49 UTC | May 26, 01:14 UTC | 2h 25m |
| 2026-05-25 | AZG9492 | LAX → KEF | May 25, 12:55 UTC | May 25, 20:55 UTC | 7h 59m |
| 2026-05-24 | AZG9491 | HHN → LAX | May 24, 23:00 UTC | May 25, 09:35 UTC | 10h 35m |
| 2026-05-24 | AZG3238 | HHN → GYD | May 24, 07:15 UTC | May 24, 19:25 UTC | 12h 10m |
| 2026-05-23 | AZG998 | MAD → GYD | May 23, 11:05 UTC | May 23, 23:55 UTC | 12h 51m |
| 2026-05-22 | AZG997 | - | May 22, 16:45 UTC | May 23, 05:15 UTC | 12h 29m |
| 2026-05-21 | AZG1573 | - | May 21, 19:50 UTC | May 22, 13:10 UTC | 17h 20m |
| 2026-05-20 | AZG247 | HKG → HKG | May 20, 08:45 UTC | May 20, 09:00 UTC | 15m |
| 2026-05-20 | AZG246 | KGF → HKG | May 20, 04:40 UTC | May 20, 05:15 UTC | 35m |
| 2026-05-19 | AZG4882 | ORD → HHN | May 19, 13:45 UTC | May 20, 02:30 UTC | 12h 45m |
| 2026-05-19 | AZG4882 | ORD → HHN | May 19, 02:20 UTC | May 19, 10:00 UTC | 7h 40m |
| 2026-05-18 | AZG4881 | LGG → GYD | May 18, 13:20 UTC | May 18, 22:45 UTC | 9h 24m |
| 2026-05-17 | AZG394 | BHX → GYD | May 17, 21:25 UTC | May 18, 08:10 UTC | 10h 45m |
| 2026-05-17 | AZG393 | GYD → BHX | May 17, 13:45 UTC | May 17, 18:45 UTC | 5h 0m |
| 2026-05-16 | AZG9798 | - | May 16, 09:21 UTC | May 16, 12:05 UTC | 2h 45m |
| 2026-05-16 | AZG9797 | - | May 16, 04:10 UTC | May 16, 05:40 UTC | 1h 30m |
| 2026-05-15 | AZG3095 | - | May 15, 20:45 UTC | May 16, 01:15 UTC | 4h 30m |
| 2026-05-15 | AZG692 | HKG → GYD | May 15, 09:35 UTC | May 15, 12:45 UTC | 3h 10m |
| 2026-05-15 | AZG692 | HKG → GYD | May 15, 06:40 UTC | May 15, 06:55 UTC | 15m |
| 2026-05-15 | AZG1922 | DMM → FRU | May 15, 02:30 UTC | May 15, 02:35 UTC | 5m |
| 2026-05-15 | AZG1922 | DMM → FRU | May 15, 01:45 UTC | May 15, 01:55 UTC | 10m |
| 2026-05-14 | AZG1922 | DMM → FRU | May 14, 20:30 UTC | May 14, 23:35 UTC | 3h 5m |
| 2026-05-13 | AZG1121 | - | May 13, 02:00 UTC | May 13, 02:10 UTC | 10m |
| 2026-05-12 | AZG5851 | - | May 12, 12:05 UTC | May 12, 15:05 UTC | 3h 0m |
| 2026-05-12 | AZG232 | HHN → GYD | May 12, 08:10 UTC | May 12, 09:20 UTC | 1h 10m |
| 2026-05-11 | AZG231 | VIE → HHN | May 11, 10:20 UTC | May 12, 06:05 UTC | 19h 45m |
| 2026-05-11 | AZG3039 | - | May 11, 08:20 UTC | May 12, 06:05 UTC | 21h 45m |
| 2026-05-11 | AZG3039 | - | May 11, 07:55 UTC | May 12, 06:05 UTC | 22h 11m |
| 2026-05-11 | AZG237 | GYD → HHN | May 11, 00:15 UTC | May 11, 04:25 UTC | 4h 10m |
| 2026-05-09 | AZG394 | BHX → GYD | May 9, 19:05 UTC | May 9, 23:44 UTC | 4h 40m |
| 2026-05-08 | AZG393 | GYD → BHX | May 8, 23:20 UTC | May 9, 15:50 UTC | 16h 30m |
| 2026-05-08 | AZG1673 | - | May 8, 01:04 UTC | May 8, 19:50 UTC | 18h 45m |
| 2026-05-07 | AZG1673 | - | May 7, 20:15 UTC | May 7, 21:30 UTC | 1h 15m |
| 2026-05-05 | AZG634 | SIN → DWC | May 5, 07:15 UTC | May 5, 12:45 UTC | 5h 30m |
| 2026-05-04 | AZG633 | - | May 4, 21:45 UTC | May 5, 03:00 UTC | 5h 15m |
| 2026-05-03 | AZG217 | TLV → GYD | May 3, 06:20 UTC | May 3, 08:20 UTC | 2h 0m |
| 2026-05-03 | AZG216 | - | May 3, 00:40 UTC | May 3, 03:05 UTC | 2h 25m |
| 2026-05-02 | AZG208 | AMS → GYD | May 2, 16:35 UTC | May 2, 19:15 UTC | 2h 40m |
| 2026-05-01 | AZG207 | GYD → AMS | May 1, 22:40 UTC | May 2, 12:40 UTC | 14h 0m |
| 2026-05-01 | AZG280 | GYD → VIE | May 1, 16:45 UTC | May 1, 18:45 UTC | 2h 0m |
| 2026-05-01 | AZG393 | GYD → BHX | May 1, 09:30 UTC | May 1, 14:30 UTC | 5h 0m |
| 2026-04-30 | AZG274 | - | Apr 30, 16:30 UTC | Apr 30, 20:00 UTC | 3h 30m |
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-SW888 page for operator, model, and routing details .