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
- 187
- 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 |
| AZG692 | - | 5 | 2026-07-03 |
| AZG691 | Sakaviaservice | 5 | 2026-07-03 |
| AZG572 | Sakaviaservice | 5 | 2026-05-26 |
| AZG4872 | Sakaviaservice | 5 | 2026-04-18 |
| AZG647 | - | 4 | 2026-07-07 |
| AZG784 | Sakaviaservice | 3 | 2026-06-12 |
| AZG632 | Sakaviaservice | 3 | 2026-06-13 |
| AZG4881 | - | 3 | 2026-07-04 |
| AZG4871 | - | 3 | 2026-07-01 |
| AZG4861 | Sakaviaservice | 3 | 2026-06-11 |
| AZG3959 | - | 3 | 2026-04-14 |
| AZG394 | - | 3 | 2026-06-29 |
| AZG3823 | - | 3 | 2026-05-07 |
| AZG204 | Sakaviaservice | 3 | 2026-06-10 |
| AZG1922 | Sakaviaservice | 3 | 2026-04-16 |
| AZG9790 | - | 2 | 2026-06-23 |
| AZG903 | - | 2 | 2026-05-09 |
| AZG8892 | - | 2 | 2026-05-22 |
| AZG8321 | Sakaviaservice | 2 | 2026-05-29 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | AZG1582 | - | Jul 13, 12:05 UTC | Jul 14, 11:55 UTC | 23h 50m |
| 2026-07-13 | AZG1582 | - | Jul 13, 11:45 UTC | Jul 13, 15:30 UTC | 3h 45m |
| 2026-07-12 | AZG9991 | - | Jul 12, 12:30 UTC | Jul 13, 07:45 UTC | 19h 15m |
| 2026-07-12 | AZG395 | - | Jul 12, 03:40 UTC | Jul 12, 08:45 UTC | 5h 5m |
| 2026-07-11 | AZG208 | - | Jul 11, 19:15 UTC | Jul 11, 23:05 UTC | 3h 50m |
| 2026-07-11 | AZG207 | - | Jul 11, 08:35 UTC | Jul 11, 13:25 UTC | 4h 50m |
| 2026-07-10 | AZG234 | - | Jul 10, 20:50 UTC | Jul 11, 00:20 UTC | 3h 30m |
| 2026-07-10 | AZG233 | - | Jul 10, 12:20 UTC | Jul 10, 16:50 UTC | 4h 30m |
| 2026-07-10 | AZG274 | - | Jul 10, 03:35 UTC | Jul 10, 06:55 UTC | 3h 20m |
| 2026-07-09 | AZG1773 | - | Jul 9, 08:40 UTC | Jul 10, 00:25 UTC | 15h 45m |
| 2026-07-07 | AZG648 | - | Jul 7, 07:25 UTC | Jul 7, 07:45 UTC | 20m |
| 2026-07-07 | AZG647 | - | Jul 7, 02:55 UTC | Jul 7, 03:25 UTC | 30m |
| 2026-07-06 | AZG647 | - | Jul 6, 19:15 UTC | Jul 7, 01:10 UTC | 5h 55m |
| 2026-07-06 | AZG6789 | - | Jul 6, 10:40 UTC | Jul 6, 14:35 UTC | 3h 55m |
| 2026-07-05 | AZG6789 | - | Jul 5, 17:30 UTC | Jul 6, 02:40 UTC | 9h 10m |
| 2026-07-04 | AZG4881 | - | Jul 4, 19:35 UTC | Jul 4, 22:00 UTC | 2h 25m |
| 2026-07-04 | AZG4881 | - | Jul 4, 06:40 UTC | Jul 4, 15:25 UTC | 8h 45m |
| 2026-07-04 | AZG4881 | - | Jul 4, 00:25 UTC | Jul 4, 04:45 UTC | 4h 20m |
| 2026-07-03 | AZG692 | - | Jul 3, 12:55 UTC | Jul 3, 13:15 UTC | 20m |
| 2026-07-03 | AZG691 | NKW → HKG | Jul 3, 07:45 UTC | Jul 3, 08:15 UTC | 30m |
| 2026-07-02 | AZG691 | NKW → HKG | Jul 2, 23:35 UTC | Jul 3, 07:00 UTC | 7h 25m |
| 2026-07-02 | AZG4862 | - | Jul 2, 15:05 UTC | Jul 2, 19:05 UTC | 4h 0m |
| 2026-07-02 | AZG4862 | - | Jul 2, 05:25 UTC | Jul 2, 13:00 UTC | 7h 35m |
| 2026-07-01 | AZG4871 | - | Jul 1, 16:55 UTC | Jul 2, 01:25 UTC | 8h 30m |
| 2026-07-01 | AZG1312 | - | Jul 1, 00:25 UTC | Jul 1, 14:20 UTC | 13h 55m |
| 2026-06-30 | AZG1311 | - | Jun 30, 15:05 UTC | Jun 30, 21:10 UTC | 6h 5m |
| 2026-06-29 | AZG394 | - | Jun 29, 20:54 UTC | Jun 30, 11:00 UTC | 14h 6m |
| 2026-06-29 | AZG393 | GYD → BHX | Jun 29, 13:24 UTC | Jun 29, 14:34 UTC | 1h 10m |
| 2026-06-28 | AZG3220 | - | Jun 28, 05:34 UTC | Jun 28, 06:10 UTC | 35m |
| 2026-06-27 | AZG234 | HHN → GYD | Jun 27, 14:29 UTC | Jun 28, 01:50 UTC | 11h 20m |
| 2026-06-27 | AZG233 | GYD → HHN | Jun 27, 06:19 UTC | Jun 27, 10:29 UTC | 4h 10m |
| 2026-06-26 | AZG232 | HHN → GYD | Jun 26, 20:04 UTC | Jun 26, 23:55 UTC | 3h 50m |
| 2026-06-25 | AZG1673 | - | Jun 25, 21:50 UTC | Jun 26, 14:19 UTC | 16h 30m |
| 2026-06-24 | AZG648 | - | Jun 24, 12:20 UTC | Jun 24, 12:40 UTC | 20m |
| 2026-06-24 | AZG647 | DMM → HKG | Jun 24, 09:19 UTC | Jun 24, 09:55 UTC | 35m |
| 2026-06-24 | AZG647 | DMM → HKG | Jun 24, 01:39 UTC | Jun 24, 08:35 UTC | 6h 55m |
| 2026-06-23 | AZG9790 | - | Jun 23, 17:59 UTC | Jun 23, 20:34 UTC | 2h 35m |
| 2026-06-23 | AZG9790 | - | Jun 23, 06:44 UTC | Jun 23, 14:19 UTC | 7h 35m |
| 2026-06-22 | AZG783 | LUX → ORD | Jun 22, 18:09 UTC | Jun 23, 02:40 UTC | 8h 30m |
| 2026-06-22 | AZG9783 | - | Jun 22, 00:50 UTC | Jun 22, 15:54 UTC | 15h 5m |
| 2026-06-21 | AZG4701 | - | Jun 21, 04:20 UTC | Jun 21, 20:45 UTC | 16h 25m |
| 2026-06-20 | AZG333 | - | Jun 20, 22:10 UTC | Jun 21, 01:10 UTC | 3h 0m |
| 2026-06-20 | AZG333 | - | Jun 20, 20:45 UTC | Jun 20, 21:00 UTC | 15m |
| 2026-06-20 | AZG281 | VIE → JFK | Jun 20, 00:14 UTC | Jun 20, 16:44 UTC | 16h 30m |
| 2026-06-19 | AZG6723 | JFK → VIE | Jun 19, 01:50 UTC | Jun 19, 19:34 UTC | 17h 45m |
| 2026-06-18 | AZG6722 | - | Jun 18, 17:40 UTC | Jun 18, 21:55 UTC | 4h 15m |
| 2026-06-18 | AZG6721 | - | Jun 18, 05:35 UTC | Jun 18, 14:15 UTC | 8h 40m |
| 2026-06-17 | AZG6721 | - | Jun 17, 19:35 UTC | Jun 18, 02:25 UTC | 6h 50m |
| 2026-06-16 | AZG3822 | - | Jun 16, 11:35 UTC | Jun 16, 15:15 UTC | 3h 40m |
| 2026-06-15 | AZG217 | TLV → GYD | Jun 15, 22:00 UTC | Jun 16, 05:00 UTC | 7h 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 .