sensors Mode-S transponder
7114F0
ICAO 24-bit transponder address · allocated to Saudi Arabia
Currently assigned to HZ-ASAK · AIRBUS A-321neo
- Hex
- 7114F0
- Octal
- 34212360
- Decimal
- 7,410,928
- Country
- SA
- Tail
- HZ-ASAK
- Type
- A21N
- Flights observed
- 115
- Distinct callsigns
- 20
- Country
- SA
- Last broadcast
- 58m ago
Last known position
Country allocation
The ICAO 24-bit address 7114F0 falls within the block assigned to Saudi Arabia (SA) by ICAO Annex 10, Volume III. Every aircraft registered in Saudi Arabia 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 |
|---|---|---|---|
| SVA596 | - | 6 | 2026-06-22 |
| SVA261 | Saudi Arabian Airlines | 6 | 2026-06-06 |
| SVA278 | - | 5 | 2026-07-07 |
| SVA275 | - | 5 | 2026-07-07 |
| SVA266 | Saudi Arabian Airlines | 4 | 2026-06-07 |
| SVA260 | Saudi Arabian Airlines | 4 | 2026-05-03 |
| SVA251 | Saudi Arabian Airlines | 4 | 2026-06-02 |
| SVA712 | - | 3 | 2026-06-29 |
| SVA597 | - | 3 | 2026-06-23 |
| SVA335 | - | 3 | 2026-07-05 |
| SVA319 | Saudi Arabian Airlines | 3 | 2026-06-16 |
| SVA315 | Saudi Arabian Airlines | 3 | 2026-06-02 |
| SVA265 | Saudi Arabian Airlines | 3 | 2026-06-06 |
| SVA252 | Saudi Arabian Airlines | 3 | 2026-06-02 |
| SVA572 | - | 2 | 2026-06-18 |
| SVA568 | - | 2 | 2026-07-13 |
| SVA330 | Saudi Arabian Airlines | 2 | 2026-06-16 |
| SVA318 | - | 2 | 2026-07-05 |
| SVA317 | Saudi Arabian Airlines | 2 | 2026-05-19 |
| SVA273 | - | 2 | 2026-07-10 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | SVA202 | - | Jul 14, 14:30 UTC | Jul 14, 16:00 UTC | 1h 30m |
| 2026-07-14 | SVA201 | - | Jul 14, 09:30 UTC | Jul 14, 12:10 UTC | 2h 40m |
| 2026-07-13 | - | - | Jul 13, 19:30 UTC | Jul 13, 19:40 UTC | 10m |
| 2026-07-13 | SVA569 | - | Jul 13, 11:50 UTC | Jul 13, 12:40 UTC | 50m |
| 2026-07-13 | SVA568 | - | Jul 13, 08:55 UTC | Jul 13, 10:10 UTC | 1h 15m |
| 2026-07-10 | SVA334 | - | Jul 10, 19:50 UTC | Jul 10, 20:30 UTC | 40m |
| 2026-07-10 | SVA272 | - | Jul 10, 10:50 UTC | Jul 10, 18:20 UTC | 7h 30m |
| 2026-07-10 | SVA273 | - | Jul 10, 07:10 UTC | Jul 10, 08:40 UTC | 1h 30m |
| 2026-07-09 | SVA192 | - | Jul 9, 12:35 UTC | Jul 9, 13:50 UTC | 1h 15m |
| 2026-07-09 | SVA191 | - | Jul 9, 08:50 UTC | Jul 9, 10:40 UTC | 1h 50m |
| 2026-07-09 | SVA1105 | - | Jul 9, 03:25 UTC | Jul 9, 03:35 UTC | 10m |
| 2026-07-07 | SVA278 | - | Jul 7, 15:55 UTC | Jul 7, 17:45 UTC | 1h 50m |
| 2026-07-07 | SVA275 | - | Jul 7, 11:45 UTC | Jul 7, 13:45 UTC | 2h 0m |
| 2026-07-06 | SVA275 | - | Jul 6, 12:05 UTC | Jul 7, 12:00 UTC | 23h 55m |
| 2026-07-06 | SVA272 | - | Jul 6, 10:50 UTC | Jul 6, 12:10 UTC | 1h 20m |
| 2026-07-05 | SVA273 | - | Jul 5, 15:30 UTC | Jul 6, 08:45 UTC | 17h 15m |
| 2026-07-05 | SVA318 | - | Jul 5, 06:50 UTC | Jul 5, 12:30 UTC | 5h 40m |
| 2026-07-05 | SVA335 | - | Jul 5, 04:15 UTC | Jul 5, 04:35 UTC | 20m |
| 2026-07-03 | SVA1167 | - | Jul 3, 02:20 UTC | Jul 3, 02:35 UTC | 15m |
| 2026-07-02 | SVA268 | IST → JED | Jul 2, 17:00 UTC | Jul 2, 18:55 UTC | 1h 55m |
| 2026-07-02 | SVA267 | RUH → IST | Jul 2, 04:45 UTC | Jul 2, 14:30 UTC | 9h 45m |
| 2026-07-01 | SVA196 | - | Jul 1, 13:05 UTC | Jul 2, 01:40 UTC | 12h 35m |
| 2026-07-01 | SVA195 | - | Jul 1, 09:10 UTC | Jul 1, 10:55 UTC | 1h 45m |
| 2026-06-30 | SVA195 | - | Jun 30, 14:25 UTC | Jul 1, 10:55 UTC | 20h 30m |
| 2026-06-30 | SVA554 | - | Jun 30, 05:50 UTC | Jun 30, 13:00 UTC | 7h 10m |
| 2026-06-29 | SVA712 | - | Jun 29, 13:39 UTC | Jun 30, 02:45 UTC | 13h 6m |
| 2026-06-29 | SVA263 | - | Jun 29, 09:10 UTC | Jun 29, 11:10 UTC | 2h 0m |
| 2026-06-27 | SVA1169 | DMM → RUH | Jun 27, 21:04 UTC | Jun 27, 21:15 UTC | 10m |
| 2026-06-27 | SVA1163 | DMM → RUH | Jun 27, 16:20 UTC | Jun 27, 16:39 UTC | 20m |
| 2026-06-26 | SVA268 | IST → JED | Jun 26, 16:44 UTC | Jun 26, 18:29 UTC | 1h 45m |
| 2026-06-26 | SVA267 | RUH → IST | Jun 26, 04:50 UTC | Jun 26, 14:29 UTC | 9h 40m |
| 2026-06-25 | SVA712 | - | Jun 25, 11:50 UTC | Jun 26, 02:40 UTC | 14h 50m |
| 2026-06-25 | SVA568 | - | Jun 25, 08:45 UTC | Jun 25, 09:59 UTC | 1h 15m |
| 2026-06-23 | SVA1161 | - | Jun 23, 22:15 UTC | Jun 23, 22:25 UTC | 10m |
| 2026-06-23 | SVA1165 | DMM → RUH | Jun 23, 18:20 UTC | Jun 23, 18:34 UTC | 15m |
| 2026-06-23 | SVA597 | - | Jun 23, 09:40 UTC | Jun 23, 10:29 UTC | 50m |
| 2026-06-22 | SVA596 | - | Jun 22, 19:54 UTC | Jun 23, 08:09 UTC | 12h 15m |
| 2026-06-22 | SVA597 | - | Jun 22, 09:34 UTC | Jun 22, 18:30 UTC | 8h 55m |
| 2026-06-21 | SVA596 | - | Jun 21, 19:50 UTC | Jun 22, 08:15 UTC | 12h 25m |
| 2026-06-21 | SVA597 | - | Jun 21, 09:35 UTC | Jun 21, 18:25 UTC | 8h 50m |
| 2026-06-20 | SVA596 | - | Jun 20, 19:55 UTC | Jun 21, 07:59 UTC | 12h 5m |
| 2026-06-20 | SVA206 | - | Jun 20, 07:24 UTC | Jun 20, 17:59 UTC | 10h 35m |
| 2026-06-19 | SVA209 | - | Jun 19, 11:39 UTC | Jun 20, 04:04 UTC | 16h 25m |
| 2026-06-18 | SVA572 | - | Jun 18, 14:05 UTC | Jun 19, 09:55 UTC | 19h 49m |
| 2026-06-18 | SVA572 | - | Jun 18, 13:55 UTC | Jun 19, 09:55 UTC | 19h 59m |
| 2026-06-18 | SVA588 | - | Jun 18, 10:45 UTC | Jun 18, 11:20 UTC | 35m |
| 2026-06-16 | SVA330 | CAI → JED | Jun 16, 15:09 UTC | Jun 16, 15:35 UTC | 25m |
| 2026-06-16 | SVA319 | MED → CAI | Jun 16, 06:54 UTC | Jun 16, 12:39 UTC | 5h 45m |
| 2026-06-16 | SVA335 | JED → CAI | Jun 16, 04:15 UTC | Jun 16, 04:35 UTC | 20m |
| 2026-06-10 | SVA596 | MED → DXB | Jun 10, 06:55 UTC | Jun 10, 10:25 UTC | 3h 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 HZ-ASAK page for operator, model, and routing details .