sensors Mode-S transponder
600B26
ICAO 24-bit transponder address · allocated to Azerbaijan
Currently assigned to 4K-BBH · BOEING 747-8
- Hex
- 600B26
- Octal
- 30005446
- Decimal
- 6,294,310
- Country
- AZ
- Tail
- 4K-BBH
- Type
- B748
- Flights observed
- 62
- Distinct callsigns
- 20
- Country
- AZ
- Last broadcast
- 24d ago
Last known position
Country allocation
The ICAO 24-bit address 600B26 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 |
|---|---|---|---|
| AZG5721 | Sakaviaservice | 6 | 2026-04-13 |
| AZG4861 | Sakaviaservice | 6 | 2026-04-23 |
| AZG5789 | - | 5 | 2026-04-14 |
| AZG4972 | Sakaviaservice | 5 | 2026-04-17 |
| AZG246 | Sakaviaservice | 5 | 2026-04-15 |
| AZG1571 | Sakaviaservice | 4 | 2026-04-17 |
| AZG624 | - | 3 | 2026-04-30 |
| AZG998 | Sakaviaservice | 2 | 2026-05-01 |
| AZG997 | - | 2 | 2026-05-01 |
| AZG625 | Sakaviaservice | 2 | 2026-04-30 |
| AZG4881 | Sakaviaservice | 2 | 2026-04-27 |
| AZG4862 | Sakaviaservice | 2 | 2026-04-24 |
| AZG3321 | Sakaviaservice | 2 | 2026-04-30 |
| AZG128 | Sakaviaservice | 2 | 2026-05-04 |
| AZG4882 | Sakaviaservice | 1 | 2026-04-27 |
| AZG3238 | Sakaviaservice | 1 | 2026-04-18 |
| AZG3237 | - | 1 | 2026-04-18 |
| AZG247 | - | 1 | 2026-04-15 |
| AZG233 | Sakaviaservice | 1 | 2026-04-22 |
| AZG206 | Sakaviaservice | 1 | 2026-05-05 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-05 | AZG206 | AMS → AMS | May 5, 15:35 UTC | May 5, 19:45 UTC | 4h 10m |
| 2026-05-05 | AZG205 | GYD → GYD | May 5, 08:00 UTC | May 5, 12:30 UTC | 4h 30m |
| 2026-05-04 | AZG129 | ICN → GYD | May 4, 19:30 UTC | May 4, 19:45 UTC | 15m |
| 2026-05-04 | AZG128 | GYD → ICN | May 4, 16:20 UTC | May 4, 16:40 UTC | 20m |
| 2026-05-04 | AZG128 | GYD → ICN | May 4, 15:05 UTC | May 4, 15:30 UTC | 25m |
| 2026-05-03 | AZG039 | GYD → PVG | May 3, 15:50 UTC | May 4, 15:30 UTC | 23h 40m |
| 2026-05-01 | AZG998 | MAD → GYD | May 1, 19:50 UTC | May 2, 00:35 UTC | 4h 45m |
| 2026-05-01 | AZG997 | - | May 1, 09:10 UTC | May 1, 14:45 UTC | 5h 35m |
| 2026-04-30 | AZG625 | HKG → HKG | Apr 30, 21:45 UTC | Apr 30, 22:05 UTC | 20m |
| 2026-04-30 | AZG624 | - | Apr 30, 15:10 UTC | Apr 30, 18:45 UTC | 3h 35m |
| 2026-04-30 | AZG3321 | GYD → BOM | Apr 30, 09:50 UTC | Apr 30, 10:40 UTC | 50m |
| 2026-04-30 | AZG3321 | GYD → BOM | Apr 30, 08:50 UTC | Apr 30, 09:05 UTC | 15m |
| 2026-04-29 | AZG204 | AMS → GYD | Apr 29, 19:55 UTC | Apr 29, 23:50 UTC | 3h 54m |
| 2026-04-29 | AZG203 | BRU → GYD | Apr 29, 11:25 UTC | Apr 29, 16:15 UTC | 4h 50m |
| 2026-04-29 | AZG1148 | HKG → HKG | Apr 29, 00:25 UTC | Apr 29, 00:45 UTC | 20m |
| 2026-04-28 | AZG1147 | TAS → GYD | Apr 28, 20:20 UTC | Apr 28, 20:40 UTC | 20m |
| 2026-04-27 | AZG4882 | ORD → HHN | Apr 27, 18:05 UTC | Apr 28, 05:15 UTC | 11h 10m |
| 2026-04-27 | AZG4881 | LGG → GYD | Apr 27, 03:25 UTC | Apr 27, 12:35 UTC | 9h 10m |
| 2026-04-26 | AZG4881 | LGG → GYD | Apr 26, 21:15 UTC | Apr 27, 01:35 UTC | 4h 20m |
| 2026-04-26 | AZG998 | MAD → GYD | Apr 26, 08:45 UTC | Apr 26, 13:40 UTC | 4h 55m |
| 2026-04-25 | AZG997 | - | Apr 25, 23:25 UTC | Apr 26, 04:40 UTC | 5h 15m |
| 2026-04-24 | AZG4862 | ORD → GYD | Apr 24, 15:35 UTC | Apr 24, 19:20 UTC | 3h 45m |
| 2026-04-24 | AZG4862 | ORD → GYD | Apr 24, 05:45 UTC | Apr 24, 13:50 UTC | 8h 5m |
| 2026-04-23 | AZG4861 | GYD → ORD | Apr 23, 17:40 UTC | Apr 24, 01:35 UTC | 7h 55m |
| 2026-04-23 | AZG4861 | GYD → ORD | Apr 23, 02:35 UTC | Apr 23, 15:30 UTC | 12h 55m |
| 2026-04-22 | AZG233 | GYD → HHN | Apr 22, 18:05 UTC | Apr 22, 22:10 UTC | 4h 5m |
| 2026-04-19 | AZG625 | HKG → HKG | Apr 19, 20:45 UTC | Apr 19, 21:05 UTC | 20m |
| 2026-04-19 | AZG624 | - | Apr 19, 17:40 UTC | Apr 19, 18:00 UTC | 20m |
| 2026-04-19 | AZG624 | - | Apr 19, 08:15 UTC | Apr 19, 15:35 UTC | 7h 20m |
| 2026-04-18 | AZG3238 | HHN → GYD | Apr 18, 21:50 UTC | Apr 19, 01:35 UTC | 3h 45m |
| 2026-04-18 | AZG3237 | - | Apr 18, 02:50 UTC | Apr 18, 18:35 UTC | 15h 45m |
| 2026-04-17 | AZG1571 | AVV → HKG | Apr 17, 22:10 UTC | Apr 17, 22:35 UTC | 25m |
| 2026-04-17 | AZG1571 | AVV → HKG | Apr 17, 19:25 UTC | Apr 17, 20:25 UTC | 1h 0m |
| 2026-04-17 | AZG1571 | AVV → HKG | Apr 17, 18:55 UTC | Apr 17, 19:20 UTC | 25m |
| 2026-04-17 | AZG1571 | AVV → HKG | Apr 17, 15:25 UTC | Apr 17, 16:20 UTC | 55m |
| 2026-04-17 | AZG4972 | ORD → HHN | Apr 17, 09:20 UTC | Apr 17, 09:55 UTC | 35m |
| 2026-04-17 | AZG4972 | ORD → HHN | Apr 17, 07:20 UTC | Apr 17, 09:15 UTC | 1h 55m |
| 2026-04-17 | AZG4972 | ORD → HHN | Apr 17, 03:20 UTC | Apr 17, 04:35 UTC | 1h 16m |
| 2026-04-16 | AZG4972 | ORD → HHN | Apr 16, 21:14 UTC | Apr 16, 23:10 UTC | 1h 55m |
| 2026-04-16 | AZG4972 | ORD → HHN | Apr 16, 20:50 UTC | Apr 16, 21:10 UTC | 20m |
| 2026-04-16 | AZG4861 | GYD → ORD | Apr 16, 15:15 UTC | Apr 16, 16:10 UTC | 55m |
| 2026-04-16 | AZG4861 | GYD → ORD | Apr 16, 07:09 UTC | Apr 16, 09:05 UTC | 1h 55m |
| 2026-04-16 | AZG4861 | GYD → ORD | Apr 16, 06:29 UTC | Apr 16, 07:05 UTC | 35m |
| 2026-04-16 | AZG4861 | GYD → ORD | Apr 16, 03:55 UTC | Apr 16, 05:05 UTC | 1h 10m |
| 2026-04-15 | AZG247 | - | Apr 15, 14:35 UTC | Apr 15, 14:50 UTC | 14m |
| 2026-04-15 | AZG246 | KGF → HKG | Apr 15, 11:05 UTC | Apr 15, 11:35 UTC | 30m |
| 2026-04-15 | AZG246 | KGF → HKG | Apr 15, 09:00 UTC | Apr 15, 09:20 UTC | 20m |
| 2026-04-15 | AZG246 | KGF → HKG | Apr 15, 07:55 UTC | Apr 15, 08:55 UTC | 1h 0m |
| 2026-04-15 | AZG246 | KGF → HKG | Apr 15, 05:05 UTC | Apr 15, 05:15 UTC | 10m |
| 2026-04-15 | AZG246 | KGF → HKG | Apr 15, 04:15 UTC | Apr 15, 04:45 UTC | 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-BBH page for operator, model, and routing details .