sensors Mode-S transponder
706058
ICAO 24-bit transponder address · allocated to Kuwait
Currently assigned to 9K-AOE · BOEING 777-300ER
- Hex
- 706058
- Octal
- 34060130
- Decimal
- 7,364,696
- Country
- KW
- Tail
- 9K-AOE
- Type
- B77W
- Flights observed
- 108
- Distinct callsigns
- 20
- Country
- KW
- Last broadcast
- 14h ago
Last known position
Country allocation
The ICAO 24-bit address 706058 falls within the block assigned to Kuwait (KW) by ICAO Annex 10, Volume III. Every aircraft registered in Kuwait 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 |
|---|---|---|---|
| KAC541 | Kuwait Airways | 11 | 2026-06-27 |
| KAC283 | Kuwait Airways | 6 | 2026-07-22 |
| KAC102 | Kuwait Airways | 6 | 2026-07-24 |
| KAC542 | - | 5 | 2026-07-25 |
| KAC419 | - | 5 | 2026-06-30 |
| KAC284 | Kuwait Airways | 5 | 2026-07-22 |
| KAC110 | - | 5 | 2026-05-27 |
| KAC122 | - | 4 | 2026-06-21 |
| KAC105 | Kuwait Airways | 4 | 2026-06-14 |
| KAC420 | - | 3 | 2026-07-01 |
| KAC415 | Kuwait Airways | 3 | 2026-05-06 |
| KAC109 | - | 3 | 2026-05-25 |
| KAC106 | Kuwait Airways | 3 | 2026-06-14 |
| KAC104 | Kuwait Airways | 3 | 2026-06-17 |
| KAC103 | Kuwait Airways | 3 | 2026-06-16 |
| KAC101 | Kuwait Airways | 3 | 2026-07-24 |
| KAC676 | Kuwait Airways | 2 | 2026-07-23 |
| KAC564 | - | 2 | 2026-07-02 |
| KAC563 | - | 2 | 2026-07-02 |
| KAC546 | - | 2 | 2026-07-25 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | KAC411 | - | Jul 26, 18:40 UTC | Jul 26, 21:25 UTC | 2h 45m |
| 2026-07-25 | KAC542 | - | Jul 25, 16:30 UTC | Jul 25, 16:50 UTC | 20m |
| 2026-07-25 | KAC546 | - | Jul 25, 08:05 UTC | Jul 25, 08:35 UTC | 30m |
| 2026-07-24 | KAC102 | LHR → KWI | Jul 24, 16:05 UTC | Jul 25, 05:30 UTC | 13h 25m |
| 2026-07-24 | KAC101 | KWI → LHR | Jul 24, 00:25 UTC | Jul 24, 13:35 UTC | 13h 10m |
| 2026-07-23 | KAC676 | DXB → KWI | Jul 23, 17:25 UTC | Jul 23, 22:45 UTC | 5h 20m |
| 2026-07-22 | KAC284 | DAC → KWI | Jul 22, 23:05 UTC | Jul 23, 15:50 UTC | 16h 45m |
| 2026-07-22 | KAC283 | KWI → DAC | Jul 22, 18:45 UTC | Jul 22, 21:40 UTC | 2h 55m |
| 2026-07-03 | KAC284 | - | Jul 3, 20:50 UTC | Jul 4, 01:40 UTC | 4h 50m |
| 2026-07-03 | KAC283 | - | Jul 3, 10:00 UTC | Jul 3, 19:05 UTC | 9h 5m |
| 2026-07-02 | KAC544 | - | Jul 2, 23:10 UTC | Jul 3, 08:20 UTC | 9h 10m |
| 2026-07-02 | KAC564 | - | Jul 2, 14:50 UTC | Jul 2, 20:45 UTC | 5h 55m |
| 2026-07-02 | KAC563 | - | Jul 2, 12:55 UTC | Jul 2, 13:15 UTC | 20m |
| 2026-07-01 | KAC420 | - | Jul 1, 23:05 UTC | Jul 2, 06:35 UTC | 7h 30m |
| 2026-06-30 | KAC419 | - | Jun 30, 22:05 UTC | Jul 1, 17:55 UTC | 19h 50m |
| 2026-06-30 | KAC419 | - | Jun 30, 20:05 UTC | Jul 1, 17:55 UTC | 21h 50m |
| 2026-06-30 | KAC102 | LHR → KWI | Jun 30, 18:05 UTC | Jul 1, 17:55 UTC | 23h 50m |
| 2026-06-30 | KAC102 | LHR → KWI | Jun 30, 17:45 UTC | Jul 1, 16:00 UTC | 22h 15m |
| 2026-06-29 | KAC101 | KWI → LHR | Jun 29, 21:34 UTC | Jun 30, 12:40 UTC | 15h 5m |
| 2026-06-29 | KAC412 | - | Jun 29, 04:20 UTC | Jun 29, 19:20 UTC | 15h 0m |
| 2026-06-28 | KAC411 | - | Jun 28, 12:35 UTC | Jun 29, 01:10 UTC | 12h 35m |
| 2026-06-28 | KAC155 | - | Jun 28, 08:50 UTC | Jun 28, 10:15 UTC | 1h 25m |
| 2026-06-27 | KAC541 | KWI → CAI | Jun 27, 13:40 UTC | Jun 27, 14:00 UTC | 20m |
| 2026-06-26 | KAC544 | - | Jun 26, 23:25 UTC | Jun 26, 23:55 UTC | 30m |
| 2026-06-26 | KAC543 | KWI → CAI | Jun 26, 20:15 UTC | Jun 26, 20:29 UTC | 15m |
| 2026-06-26 | KAC564 | - | Jun 26, 14:29 UTC | Jun 26, 14:39 UTC | 10m |
| 2026-06-26 | KAC563 | AMM → AMM | Jun 26, 12:50 UTC | Jun 26, 13:04 UTC | 15m |
| 2026-06-25 | KAC284 | DAC → KWI | Jun 25, 22:10 UTC | Jun 26, 03:00 UTC | 4h 50m |
| 2026-06-25 | KAC283 | KWI → DAC | Jun 25, 15:29 UTC | Jun 25, 20:19 UTC | 4h 50m |
| 2026-06-24 | KAC420 | - | Jun 24, 21:14 UTC | Jun 25, 04:35 UTC | 7h 20m |
| 2026-06-24 | KAC419 | - | Jun 24, 11:20 UTC | Jun 24, 17:59 UTC | 6h 40m |
| 2026-06-22 | KAC156 | - | Jun 22, 14:05 UTC | Jun 22, 15:40 UTC | 1h 35m |
| 2026-06-22 | KAC155 | - | Jun 22, 01:10 UTC | Jun 22, 10:19 UTC | 9h 10m |
| 2026-06-21 | KAC122 | - | Jun 21, 13:15 UTC | Jun 21, 23:10 UTC | 9h 55m |
| 2026-06-20 | KAC121 | - | Jun 20, 18:10 UTC | Jun 21, 10:49 UTC | 16h 40m |
| 2026-06-20 | KAC107 | GVA → LHR | Jun 20, 10:25 UTC | Jun 20, 13:49 UTC | 3h 25m |
| 2026-06-19 | KAC107 | GVA → LHR | Jun 19, 16:29 UTC | Jun 20, 13:49 UTC | 21h 20m |
| 2026-06-19 | KAC286 | - | Jun 19, 01:39 UTC | Jun 19, 13:50 UTC | 12h 10m |
| 2026-06-18 | KAC285 | - | Jun 18, 16:10 UTC | Jun 19, 00:14 UTC | 8h 4m |
| 2026-06-18 | KAC285 | - | Jun 18, 00:20 UTC | Jun 19, 00:00 UTC | 23h 40m |
| 2026-06-17 | KAC417 | - | Jun 17, 22:05 UTC | Jun 18, 22:00 UTC | 23h 55m |
| 2026-06-17 | KAC104 | LHR → KWI | Jun 17, 11:05 UTC | Jun 18, 02:00 UTC | 14h 55m |
| 2026-06-16 | KAC103 | KWI → LHR | Jun 16, 17:05 UTC | Jun 17, 08:20 UTC | 15h 16m |
| 2026-06-15 | KAC541 | KWI → CAI | Jun 15, 20:04 UTC | Jun 16, 15:00 UTC | 18h 55m |
| 2026-06-15 | KAC102 | LHR → KWI | Jun 15, 18:04 UTC | Jun 16, 15:00 UTC | 20h 55m |
| 2026-06-15 | KAC102 | LHR → KWI | Jun 15, 16:09 UTC | Jun 16, 15:00 UTC | 22h 50m |
| 2026-06-14 | KAC106 | LHR → KWI | Jun 14, 21:15 UTC | Jun 15, 13:10 UTC | 15h 54m |
| 2026-06-14 | KAC105 | KWI → LHR | Jun 14, 08:05 UTC | Jun 14, 19:00 UTC | 10h 55m |
| 2026-06-13 | KAC545 | - | Jun 13, 23:20 UTC | Jun 14, 05:50 UTC | 6h 30m |
| 2026-06-13 | KAC543 | KWI → CAI | Jun 13, 20:45 UTC | Jun 13, 21:00 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 9K-AOE page for operator, model, and routing details .