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
- 174
- Distinct callsigns
- 20
- Country
- AZ
- Last broadcast
- 8h ago
Last known 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 |
|---|---|---|---|
| AZG572 | Sakaviaservice | 8 | 2026-06-21 |
| AZG7733 | - | 7 | 2026-04-14 |
| AZG6889 | Sakaviaservice | 7 | 2026-04-15 |
| AZG3941 | - | 7 | 2026-04-18 |
| AZG3942 | - | 5 | 2026-04-18 |
| AZG394 | - | 5 | 2026-06-25 |
| AZG393 | Sakaviaservice | 5 | 2026-06-22 |
| AZG1673 | - | 5 | 2026-07-03 |
| AZG128 | Sakaviaservice | 5 | 2026-06-10 |
| AZG3236 | Sakaviaservice | 4 | 2026-06-19 |
| AZG3233 | - | 4 | 2026-07-01 |
| AZG9692 | Sakaviaservice | 3 | 2026-05-30 |
| AZG9492 | Sakaviaservice | 3 | 2026-05-26 |
| AZG3234 | Sakaviaservice | 3 | 2026-06-04 |
| AZG216 | - | 3 | 2026-06-22 |
| AZG1922 | Sakaviaservice | 3 | 2026-05-15 |
| AZG9491 | Sakaviaservice | 2 | 2026-05-29 |
| AZG903 | - | 2 | 2026-06-28 |
| AZG7342 | - | 2 | 2026-07-02 |
| AZG715 | - | 2 | 2026-06-07 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | AZG5789 | - | Jul 13, 14:30 UTC | Jul 13, 18:10 UTC | 3h 40m |
| 2026-07-13 | AZG5789 | - | Jul 13, 03:20 UTC | Jul 13, 12:45 UTC | 9h 25m |
| 2026-07-12 | AZG783 | - | Jul 12, 06:20 UTC | Jul 12, 17:25 UTC | 11h 5m |
| 2026-07-12 | AZG284 | - | Jul 12, 00:30 UTC | Jul 12, 04:01 UTC | 3h 30m |
| 2026-07-11 | AZG3238 | - | Jul 11, 10:00 UTC | Jul 11, 13:45 UTC | 3h 45m |
| 2026-07-10 | AZG3237 | - | Jul 10, 14:45 UTC | Jul 11, 06:20 UTC | 15h 35m |
| 2026-07-10 | AZG3319 | - | Jul 10, 10:30 UTC | Jul 10, 10:50 UTC | 20m |
| 2026-07-09 | AZG134 | - | Jul 9, 22:25 UTC | Jul 10, 09:45 UTC | 11h 20m |
| 2026-07-09 | AZG8586 | - | Jul 9, 03:40 UTC | Jul 9, 18:30 UTC | 14h 50m |
| 2026-07-08 | AZG8585 | - | Jul 8, 19:25 UTC | Jul 8, 23:50 UTC | 4h 25m |
| 2026-07-03 | AZG276 | - | Jul 3, 19:35 UTC | Jul 3, 23:05 UTC | 3h 30m |
| 2026-07-03 | AZG1673 | - | Jul 3, 01:05 UTC | Jul 3, 16:35 UTC | 15h 30m |
| 2026-07-02 | AZG1673 | - | Jul 2, 20:25 UTC | Jul 3, 16:35 UTC | 20h 10m |
| 2026-07-02 | AZG1673 | - | Jul 2, 17:15 UTC | Jul 3, 16:15 UTC | 23h 0m |
| 2026-07-02 | AZG6861 | - | Jul 2, 12:15 UTC | Jul 2, 13:00 UTC | 45m |
| 2026-07-02 | AZG7342 | AUH → AUH | Jul 2, 02:35 UTC | Jul 2, 02:45 UTC | 10m |
| 2026-07-01 | AZG7342 | - | Jul 1, 16:15 UTC | Jul 1, 22:05 UTC | 5h 50m |
| 2026-07-01 | AZG7341 | - | Jul 1, 11:40 UTC | Jul 1, 13:15 UTC | 1h 35m |
| 2026-07-01 | AZG3233 | - | Jul 1, 03:05 UTC | Jul 1, 07:05 UTC | 4h 0m |
| 2026-06-30 | AZG1247 | - | Jun 30, 11:25 UTC | Jun 30, 11:40 UTC | 15m |
| 2026-06-30 | AZG1246 | - | Jun 30, 07:05 UTC | Jun 30, 07:45 UTC | 40m |
| 2026-06-29 | AZG124 | ICN → GYD | Jun 29, 13:09 UTC | Jun 29, 13:24 UTC | 15m |
| 2026-06-29 | AZG904 | - | Jun 29, 08:14 UTC | Jun 29, 10:10 UTC | 1h 55m |
| 2026-06-28 | AZG903 | - | Jun 28, 11:50 UTC | Jun 29, 05:20 UTC | 17h 30m |
| 2026-06-28 | AZG903 | - | Jun 28, 08:44 UTC | Jun 29, 05:20 UTC | 20h 35m |
| 2026-06-27 | AZG631 | - | Jun 27, 22:49 UTC | Jun 28, 04:35 UTC | 5h 45m |
| 2026-06-27 | AZG202 | AMS → GYD | Jun 27, 13:24 UTC | Jun 27, 17:25 UTC | 4h 0m |
| 2026-06-27 | AZG201 | GYD → AMS | Jun 27, 02:35 UTC | Jun 27, 07:04 UTC | 4h 30m |
| 2026-06-25 | AZG394 | - | Jun 25, 12:04 UTC | Jun 25, 15:59 UTC | 3h 55m |
| 2026-06-24 | AZG394 | - | Jun 24, 21:19 UTC | Jun 24, 22:25 UTC | 1h 5m |
| 2026-06-22 | AZG393 | GYD → BHX | Jun 22, 11:35 UTC | Jun 22, 16:45 UTC | 5h 10m |
| 2026-06-22 | AZG217 | TLV → GYD | Jun 22, 06:10 UTC | Jun 22, 08:10 UTC | 2h 0m |
| 2026-06-22 | AZG216 | - | Jun 22, 00:20 UTC | Jun 22, 01:00 UTC | 40m |
| 2026-06-21 | AZG426 | - | Jun 21, 16:14 UTC | Jun 21, 20:09 UTC | 3h 55m |
| 2026-06-21 | AZG572 | HKG → HKG | Jun 21, 11:59 UTC | Jun 21, 12:10 UTC | 10m |
| 2026-06-21 | AZG572 | HKG → HKG | Jun 21, 05:49 UTC | Jun 21, 10:40 UTC | 4h 50m |
| 2026-06-21 | AZG572 | HKG → HKG | Jun 21, 05:00 UTC | Jun 21, 05:15 UTC | 15m |
| 2026-06-21 | AZG571 | GYD → HKG | Jun 21, 01:19 UTC | Jun 21, 01:55 UTC | 35m |
| 2026-06-20 | AZG9803 | - | Jun 20, 09:14 UTC | Jun 20, 14:50 UTC | 5h 35m |
| 2026-06-19 | AZG3236 | HHN → GYD | Jun 19, 17:49 UTC | Jun 19, 20:19 UTC | 2h 30m |
| 2026-06-19 | AZG3235 | - | Jun 19, 07:25 UTC | Jun 19, 11:30 UTC | 4h 5m |
| 2026-06-16 | AZG634 | SIN → DWC | Jun 16, 16:55 UTC | Jun 16, 22:00 UTC | 5h 6m |
| 2026-06-16 | AZG1634 | - | Jun 16, 11:49 UTC | Jun 16, 12:00 UTC | 10m |
| 2026-06-16 | AZG1633 | - | Jun 16, 08:15 UTC | Jun 16, 08:25 UTC | 10m |
| 2026-06-16 | AZG1633 | - | Jun 16, 06:40 UTC | Jun 16, 06:50 UTC | 10m |
| 2026-06-15 | AZG394 | BHX → GYD | Jun 15, 09:15 UTC | Jun 16, 02:54 UTC | 17h 40m |
| 2026-06-14 | AZG393 | GYD → BHX | Jun 14, 14:10 UTC | Jun 15, 06:04 UTC | 15h 54m |
| 2026-06-13 | AZG122 | - | Jun 13, 06:05 UTC | Jun 13, 06:20 UTC | 15m |
| 2026-06-13 | AZG121 | - | Jun 13, 02:35 UTC | Jun 13, 02:55 UTC | 20m |
| 2026-06-12 | AZG3824 | HHN → GYD | Jun 12, 12:20 UTC | Jun 13, 01:50 UTC | 13h 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 .