sensors Mode-S transponder
600BBE
ICAO 24-bit transponder address · allocated to Azerbaijan
Currently assigned to 4K-SW008 · BOEING 747-400
- Hex
- 600BBE
- Octal
- 30005676
- Decimal
- 6,294,462
- Country
- AZ
- Tail
- 4K-SW008
- Type
- B744
- Flights observed
- 102
- Distinct callsigns
- 20
- Country
- AZ
- Last broadcast
- 43m ago
Last known position
Country allocation
The ICAO 24-bit address 600BBE 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 |
|---|---|---|---|
| AZG393 | Sakaviaservice | 6 | 2026-06-01 |
| AZG692 | Sakaviaservice | 5 | 2026-05-25 |
| AZG723 | Sakaviaservice | 4 | 2026-05-19 |
| AZG5323 | - | 4 | 2026-05-22 |
| AZG3232 | Sakaviaservice | 4 | 2026-05-05 |
| AZG3231 | Sakaviaservice | 4 | 2026-05-05 |
| AZG9692 | Sakaviaservice | 3 | 2026-05-23 |
| AZG634 | Sakaviaservice | 3 | 2026-05-26 |
| AZG633 | - | 3 | 2026-05-26 |
| AZG4871 | Sakaviaservice | 3 | 2026-05-30 |
| AZG394 | Sakaviaservice | 3 | 2026-06-01 |
| AZG3319 | Sakaviaservice | 3 | 2026-05-21 |
| AZG2249 | - | 3 | 2026-05-02 |
| AZG219 | Sakaviaservice | 3 | 2026-05-11 |
| AZG1881 | - | 3 | 2026-04-16 |
| AZG903 | - | 2 | 2026-05-17 |
| AZG5452 | - | 2 | 2026-05-28 |
| AZG4882 | Sakaviaservice | 2 | 2026-05-03 |
| AZG4004 | - | 2 | 2026-04-18 |
| AZG4001 | Sakaviaservice | 2 | 2026-04-17 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-02 | AZG3822 | HHN → GYD | Jun 2, 19:50 UTC | Jun 2, 23:30 UTC | 3h 40m |
| 2026-06-02 | AZG1673 | - | Jun 2, 02:25 UTC | Jun 2, 16:15 UTC | 13h 50m |
| 2026-06-01 | AZG1673 | - | Jun 1, 23:55 UTC | Jun 2, 00:10 UTC | 15m |
| 2026-06-01 | AZG394 | BHX → GYD | Jun 1, 10:10 UTC | Jun 1, 23:15 UTC | 13h 5m |
| 2026-06-01 | AZG393 | GYD → BHX | Jun 1, 01:55 UTC | Jun 1, 07:05 UTC | 5h 10m |
| 2026-05-31 | AZG393 | GYD → BHX | May 31, 09:35 UTC | Jun 1, 07:05 UTC | 21h 30m |
| 2026-05-31 | AZG393 | GYD → BHX | May 31, 08:45 UTC | Jun 1, 05:30 UTC | 20h 45m |
| 2026-05-30 | AZG5990 | GSP → ATH | May 30, 17:45 UTC | May 31, 09:45 UTC | 16h 0m |
| 2026-05-30 | AZG4871 | GYD → ORD | May 30, 11:55 UTC | May 30, 13:10 UTC | 1h 15m |
| 2026-05-29 | AZG4871 | GYD → ORD | May 29, 23:00 UTC | May 30, 07:10 UTC | 8h 10m |
| 2026-05-29 | AZG4871 | GYD → ORD | May 29, 06:30 UTC | May 29, 17:50 UTC | 11h 20m |
| 2026-05-28 | AZG5452 | - | May 28, 09:35 UTC | May 29, 06:50 UTC | 21h 15m |
| 2026-05-28 | AZG5452 | - | May 28, 08:20 UTC | May 29, 06:50 UTC | 22h 30m |
| 2026-05-28 | AZG5451 | - | May 28, 01:25 UTC | May 28, 02:35 UTC | 1h 10m |
| 2026-05-27 | AZG1247 | JFK → HHN | May 27, 12:15 UTC | May 27, 12:30 UTC | 15m |
| 2026-05-27 | AZG1246 | - | May 27, 09:00 UTC | May 27, 09:35 UTC | 35m |
| 2026-05-26 | AZG634 | SIN → DWC | May 26, 14:50 UTC | May 26, 20:29 UTC | 5h 40m |
| 2026-05-26 | AZG633 | - | May 26, 01:14 UTC | May 26, 06:44 UTC | 5h 30m |
| 2026-05-25 | AZG633 | - | May 25, 08:15 UTC | May 26, 06:44 UTC | 22h 29m |
| 2026-05-25 | AZG692 | HKG → GYD | May 25, 06:05 UTC | May 26, 02:39 UTC | 20h 34m |
| 2026-05-25 | AZG692 | HKG → GYD | May 25, 03:15 UTC | May 25, 03:30 UTC | 15m |
| 2026-05-23 | AZG9692 | LAX → ORD | May 23, 22:55 UTC | May 24, 11:05 UTC | 12h 10m |
| 2026-05-23 | AZG9692 | LAX → ORD | May 23, 13:05 UTC | May 23, 21:00 UTC | 7h 56m |
| 2026-05-23 | AZG9692 | LAX → ORD | May 23, 07:05 UTC | May 23, 10:25 UTC | 3h 20m |
| 2026-05-22 | AZG5323 | - | May 22, 23:30 UTC | May 23, 04:30 UTC | 4h 59m |
| 2026-05-22 | AZG5323 | - | May 22, 18:35 UTC | May 22, 21:00 UTC | 2h 25m |
| 2026-05-22 | AZG5323 | - | May 22, 07:40 UTC | May 22, 15:10 UTC | 7h 30m |
| 2026-05-22 | AZG5323 | - | May 22, 01:50 UTC | May 22, 02:55 UTC | 1h 5m |
| 2026-05-21 | AZG3319 | GYD → BOM | May 21, 09:15 UTC | May 21, 09:55 UTC | 40m |
| 2026-05-20 | AZG634 | SIN → DWC | May 20, 15:55 UTC | May 21, 08:15 UTC | 16h 20m |
| 2026-05-19 | AZG724 | LGG → GYD | May 19, 16:40 UTC | May 20, 08:45 UTC | 16h 6m |
| 2026-05-19 | AZG723 | GYD → LGG | May 19, 12:20 UTC | May 19, 13:35 UTC | 1h 15m |
| 2026-05-19 | AZG723 | GYD → LGG | May 19, 09:15 UTC | May 19, 12:15 UTC | 3h 0m |
| 2026-05-18 | AZG723 | GYD → LGG | May 18, 13:35 UTC | May 19, 12:15 UTC | 22h 39m |
| 2026-05-18 | AZG723 | GYD → LGG | May 18, 13:15 UTC | May 19, 11:30 UTC | 22h 14m |
| 2026-05-18 | AZG904 | NRT → GYD | May 18, 08:10 UTC | May 18, 10:00 UTC | 1h 50m |
| 2026-05-17 | AZG903 | - | May 17, 09:35 UTC | May 18, 05:15 UTC | 19h 40m |
| 2026-05-17 | AZG903 | - | May 17, 09:05 UTC | May 18, 05:15 UTC | 20h 10m |
| 2026-05-16 | AZG998 | MAD → GYD | May 16, 13:35 UTC | May 17, 05:05 UTC | 15h 30m |
| 2026-05-15 | AZG997 | - | May 15, 18:50 UTC | May 16, 08:36 UTC | 13h 46m |
| 2026-05-15 | AZG235 | ORD → HHN | May 15, 10:30 UTC | May 15, 14:45 UTC | 4h 15m |
| 2026-05-13 | AZG071 | - | May 13, 15:35 UTC | May 13, 15:55 UTC | 20m |
| 2026-05-11 | AZG219 | TLV → GYD | May 11, 06:35 UTC | May 11, 08:40 UTC | 2h 5m |
| 2026-05-11 | AZG218 | GYD → TLV | May 11, 00:34 UTC | May 11, 03:10 UTC | 2h 35m |
| 2026-05-10 | AZG764 | LGG → GYD | May 10, 09:45 UTC | May 10, 13:40 UTC | 3h 55m |
| 2026-05-10 | AZG763 | STN → GYD | May 10, 01:55 UTC | May 10, 06:20 UTC | 4h 25m |
| 2026-05-09 | AZG534 | DAC → GYD | May 9, 14:20 UTC | May 9, 16:25 UTC | 2h 5m |
| 2026-05-08 | AZG3939 | - | May 8, 21:55 UTC | May 9, 11:05 UTC | 13h 10m |
| 2026-05-08 | AZG3938 | - | May 8, 12:34 UTC | May 8, 18:50 UTC | 6h 15m |
| 2026-05-07 | AZG692 | HKG → GYD | May 7, 23:45 UTC | May 7, 23:59 UTC | 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-SW008 page for operator, model, and routing details .