sensors Mode-S transponder
70620F
ICAO 24-bit transponder address · allocated to Kuwait
Currently assigned to 9K-CAN · AIRBUS A-320
- Hex
- 70620F
- Octal
- 34061017
- Decimal
- 7,365,135
- Country
- KW
- Tail
- 9K-CAN
- Type
- A320
- Flights observed
- 69
- Distinct callsigns
- 20
- Country
- KW
- Last broadcast
- 6h ago
Current position
Country allocation
The ICAO 24-bit address 70620F 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 |
|---|---|---|---|
| JZR214 | Jazeera Airways | 7 | 2026-06-05 |
| JZR121 | - | 5 | 2026-06-11 |
| JZR723 | - | 4 | 2026-05-25 |
| JZR732 | - | 3 | 2026-05-16 |
| JZR731 | - | 3 | 2026-05-15 |
| JZR724 | - | 3 | 2026-05-23 |
| JZR259 | - | 3 | 2026-06-10 |
| JZR210 | Jazeera Airways | 3 | 2026-06-06 |
| JZR824 | - | 2 | 2026-05-30 |
| JZR742 | Jazeera Airways | 2 | 2026-05-27 |
| JZR741 | Jazeera Airways | 2 | 2026-05-27 |
| JZR611 | - | 2 | 2026-05-26 |
| JZR402 | Jazeera Airways | 2 | 2026-06-16 |
| JZR401 | Jazeera Airways | 2 | 2026-06-16 |
| JZR262 | - | 2 | 2026-06-11 |
| JZR123 | - | 2 | 2026-05-29 |
| JZR122 | - | 2 | 2026-06-11 |
| NMA171 | Nesma Airlines | 1 | 2026-04-26 |
| NMA123 | Nesma Airlines | 1 | 2026-04-26 |
| NMA064 | Nesma Airlines | 1 | 2026-04-22 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-17 | JZR101 | - | Jun 17, 09:15 UTC | Jun 17, 09:40 UTC | 25m |
| 2026-06-16 | JZR402 | BOM → AQI | Jun 16, 21:40 UTC | Jun 16, 22:10 UTC | 30m |
| 2026-06-16 | JZR401 | AQI → BOM | Jun 16, 16:15 UTC | Jun 16, 19:40 UTC | 3h 25m |
| 2026-06-15 | JZR507 | - | Jun 15, 12:49 UTC | Jun 16, 01:00 UTC | 12h 10m |
| 2026-06-15 | JZR115 | - | Jun 15, 10:15 UTC | Jun 15, 11:00 UTC | 45m |
| 2026-06-11 | JZR262 | - | Jun 11, 21:30 UTC | Jun 12, 05:00 UTC | 7h 30m |
| 2026-06-11 | JZR122 | - | Jun 11, 15:50 UTC | Jun 11, 16:05 UTC | 15m |
| 2026-06-11 | JZR121 | - | Jun 11, 12:35 UTC | Jun 11, 13:40 UTC | 1h 5m |
| 2026-06-10 | JZR121 | - | Jun 10, 16:10 UTC | Jun 11, 13:40 UTC | 21h 30m |
| 2026-06-10 | JZR259 | - | Jun 10, 14:55 UTC | Jun 10, 15:15 UTC | 20m |
| 2026-06-08 | JZR820 | - | Jun 8, 22:50 UTC | Jun 9, 00:45 UTC | 1h 55m |
| 2026-06-08 | JZR209 | MCX → JED | Jun 8, 11:40 UTC | Jun 8, 20:35 UTC | 8h 55m |
| 2026-06-07 | JZR5746 | JED → MCX | Jun 7, 19:05 UTC | Jun 8, 08:45 UTC | 13h 40m |
| 2026-06-06 | JZR212 | JED → MCX | Jun 6, 21:20 UTC | Jun 7, 15:15 UTC | 17h 55m |
| 2026-06-06 | JZR210 | JED → MCX | Jun 6, 17:10 UTC | Jun 6, 19:19 UTC | 2h 10m |
| 2026-06-05 | JZR210 | JED → MCX | Jun 5, 20:35 UTC | Jun 6, 19:19 UTC | 22h 45m |
| 2026-06-05 | JZR5816 | MCX → JED | Jun 5, 18:45 UTC | Jun 6, 17:15 UTC | 22h 30m |
| 2026-06-05 | JZR214 | JED → MCX | Jun 5, 15:25 UTC | Jun 5, 16:20 UTC | 55m |
| 2026-06-04 | JZR214 | JED → MCX | Jun 4, 20:00 UTC | Jun 5, 16:20 UTC | 20h 20m |
| 2026-06-04 | JZR214 | JED → MCX | Jun 4, 18:25 UTC | Jun 5, 16:20 UTC | 21h 55m |
| 2026-06-04 | JZR214 | JED → MCX | Jun 4, 15:30 UTC | Jun 4, 16:20 UTC | 50m |
| 2026-06-03 | JZR214 | JED → MCX | Jun 3, 18:40 UTC | Jun 4, 16:20 UTC | 21h 40m |
| 2026-06-03 | JZR214 | JED → MCX | Jun 3, 14:15 UTC | Jun 3, 16:25 UTC | 2h 10m |
| 2026-06-02 | JZR214 | JED → MCX | Jun 2, 20:25 UTC | Jun 3, 16:25 UTC | 20h 0m |
| 2026-06-01 | JZR5812 | MCX → JED | Jun 1, 15:45 UTC | Jun 1, 17:45 UTC | 2h 0m |
| 2026-05-31 | JZR208 | JED → DME | May 31, 21:45 UTC | Jun 1, 13:30 UTC | 15h 45m |
| 2026-05-31 | JZR210 | JED → MCX | May 31, 10:45 UTC | May 31, 19:35 UTC | 8h 50m |
| 2026-05-30 | JZR824 | - | May 30, 19:05 UTC | May 31, 17:45 UTC | 22h 40m |
| 2026-05-30 | JZR824 | - | May 30, 17:25 UTC | May 31, 12:25 UTC | 19h 0m |
| 2026-05-29 | JZR408 | - | May 29, 23:10 UTC | May 30, 15:20 UTC | 16h 10m |
| 2026-05-29 | JZR407 | - | May 29, 18:35 UTC | May 29, 21:30 UTC | 2h 55m |
| 2026-05-29 | JZR123 | - | May 29, 05:00 UTC | May 29, 12:35 UTC | 7h 35m |
| 2026-05-29 | JZR259 | AMM → AMM | May 29, 03:20 UTC | May 29, 03:40 UTC | 20m |
| 2026-05-28 | JZR123 | - | May 28, 13:40 UTC | May 28, 14:45 UTC | 1h 5m |
| 2026-05-27 | JZR742 | SPX → AQI | May 27, 13:50 UTC | May 28, 13:45 UTC | 23h 55m |
| 2026-05-27 | JZR742 | SPX → AQI | May 27, 13:30 UTC | May 27, 13:55 UTC | 25m |
| 2026-05-27 | JZR741 | AQI → SPX | May 27, 10:20 UTC | May 27, 10:45 UTC | 25m |
| 2026-05-26 | JZR741 | AQI → SPX | May 26, 11:50 UTC | May 27, 10:45 UTC | 22h 55m |
| 2026-05-26 | JZR612 | - | May 26, 11:34 UTC | May 26, 12:05 UTC | 30m |
| 2026-05-26 | JZR611 | - | May 26, 08:45 UTC | May 26, 09:59 UTC | 1h 15m |
| 2026-05-25 | JZR611 | - | May 25, 09:50 UTC | May 26, 09:45 UTC | 23h 55m |
| 2026-05-25 | JZR723 | - | May 25, 07:50 UTC | May 25, 08:20 UTC | 30m |
| 2026-05-24 | JZR260 | ADJ → ADJ | May 24, 04:50 UTC | May 24, 05:05 UTC | 15m |
| 2026-05-24 | JZR259 | AMM → AMM | May 24, 03:25 UTC | May 24, 03:50 UTC | 25m |
| 2026-05-23 | JZR724 | - | May 23, 07:05 UTC | May 24, 03:50 UTC | 20h 45m |
| 2026-05-22 | JZR723 | - | May 22, 14:55 UTC | May 23, 06:10 UTC | 15h 14m |
| 2026-05-21 | JZR122 | - | May 21, 12:35 UTC | May 21, 12:45 UTC | 10m |
| 2026-05-19 | JZR402 | BOM → AQI | May 19, 21:25 UTC | May 20, 09:25 UTC | 12h 1m |
| 2026-05-19 | JZR401 | AQI → BOM | May 19, 16:50 UTC | May 19, 19:40 UTC | 2h 50m |
| 2026-05-18 | JZR724 | - | May 18, 09:00 UTC | May 18, 09:25 UTC | 25m |
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-CAN page for operator, model, and routing details .