sensors Mode-S transponder
710070
ICAO 24-bit transponder address · allocated to Saudi Arabia
Currently assigned to HZ-ASA · AIRBUS A-320
- Hex
- 710070
- Octal
- 34200160
- Decimal
- 7,405,680
- Country
- SA
- Tail
- HZ-ASA
- Type
- A320
- Flights observed
- 125
- Distinct callsigns
- 20
- Country
- SA
- Last broadcast
- 11h ago
Last known position
Country allocation
The ICAO 24-bit address 710070 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 |
|---|---|---|---|
| SVA207 | - | 24 | 2026-06-25 |
| SVA167 | - | 17 | 2026-06-28 |
| SVA201 | - | 15 | 2026-06-26 |
| SVA168 | Saudi Arabian Airlines | 11 | 2026-06-28 |
| SVA208 | Saudi Arabian Airlines | 6 | 2026-06-25 |
| SVA206 | - | 6 | 2026-07-04 |
| SVA202 | Saudi Arabian Airlines | 6 | 2026-06-21 |
| SVA235 | - | 5 | 2026-06-26 |
| SVA179 | - | 5 | 2026-07-02 |
| SVA234 | Saudi Arabian Airlines | 4 | 2026-06-26 |
| SVA209 | Saudi Arabian Airlines | 4 | 2026-05-26 |
| SVA540 | Saudi Arabian Airlines | 3 | 2026-05-21 |
| SVA204 | - | 3 | 2026-06-29 |
| SVA180 | Saudi Arabian Airlines | 3 | 2026-07-03 |
| SVA636 | - | 1 | 2026-06-29 |
| SVA573 | Saudi Arabian Airlines | 1 | 2026-05-13 |
| SVA561 | - | 1 | 2026-07-06 |
| SVA560 | - | 1 | 2026-07-06 |
| SVA554 | Saudi Arabian Airlines | 1 | 2026-06-17 |
| SVA521 | - | 1 | 2026-07-08 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-17 | SVA1117 | DMM → JED | Jul 17, 15:29 UTC | Jul 17, 15:40 UTC | 10m |
| 2026-07-17 | SVA1107 | - | Jul 17, 07:25 UTC | Jul 17, 07:35 UTC | 10m |
| 2026-07-08 | SVA521 | - | Jul 8, 14:55 UTC | Jul 8, 15:10 UTC | 15m |
| 2026-07-08 | SVA520 | - | Jul 8, 13:10 UTC | Jul 8, 13:30 UTC | 20m |
| 2026-07-06 | SVA561 | - | Jul 6, 17:25 UTC | Jul 6, 18:15 UTC | 50m |
| 2026-07-06 | SVA560 | - | Jul 6, 14:35 UTC | Jul 6, 15:45 UTC | 1h 10m |
| 2026-07-04 | SVA206 | - | Jul 4, 07:20 UTC | Jul 4, 10:35 UTC | 3h 15m |
| 2026-07-03 | SVA180 | FRA → RUH | Jul 3, 14:35 UTC | Jul 4, 04:50 UTC | 14h 15m |
| 2026-07-02 | SVA179 | - | Jul 2, 18:05 UTC | Jul 3, 12:50 UTC | 18h 45m |
| 2026-07-02 | SVA179 | DST → FRA | Jul 2, 17:45 UTC | Jul 3, 12:50 UTC | 19h 5m |
| 2026-07-02 | SVA206 | - | Jul 2, 08:10 UTC | Jul 2, 16:25 UTC | 8h 15m |
| 2026-07-01 | SVA180 | FRA → RUH | Jul 1, 14:55 UTC | Jul 2, 04:45 UTC | 13h 50m |
| 2026-07-01 | SVA179 | - | Jul 1, 08:05 UTC | Jul 1, 12:05 UTC | 4h 0m |
| 2026-06-29 | SVA636 | - | Jun 29, 17:49 UTC | Jun 29, 18:05 UTC | 15m |
| 2026-06-29 | SVA204 | - | Jun 29, 07:59 UTC | Jun 29, 16:19 UTC | 8h 20m |
| 2026-06-28 | SVA168 | FRA → JED | Jun 28, 14:39 UTC | Jun 29, 04:39 UTC | 14h 0m |
| 2026-06-28 | SVA167 | - | Jun 28, 08:39 UTC | Jun 28, 12:05 UTC | 3h 25m |
| 2026-06-27 | SVA167 | - | Jun 27, 16:04 UTC | Jun 28, 12:05 UTC | 20h 0m |
| 2026-06-27 | SVA167 | - | Jun 27, 14:20 UTC | Jun 28, 12:05 UTC | 21h 45m |
| 2026-06-26 | SVA201 | - | Jun 26, 18:04 UTC | Jun 27, 12:15 UTC | 18h 10m |
| 2026-06-26 | SVA201 | - | Jun 26, 16:05 UTC | Jun 27, 12:15 UTC | 20h 10m |
| 2026-06-26 | SVA234 | ZRH → RUH | Jun 26, 14:29 UTC | Jun 27, 12:15 UTC | 21h 45m |
| 2026-06-26 | SVA235 | - | Jun 26, 08:24 UTC | Jun 26, 12:19 UTC | 3h 55m |
| 2026-06-25 | SVA208 | FCO → RUH | Jun 25, 14:24 UTC | Jun 25, 17:44 UTC | 3h 20m |
| 2026-06-25 | SVA207 | - | Jun 25, 09:10 UTC | Jun 25, 12:19 UTC | 3h 10m |
| 2026-06-24 | SVA207 | - | Jun 24, 16:05 UTC | Jun 25, 12:19 UTC | 20h 15m |
| 2026-06-24 | SVA234 | ZRH → RUH | Jun 24, 14:15 UTC | Jun 25, 12:19 UTC | 22h 5m |
| 2026-06-24 | SVA235 | - | Jun 24, 08:39 UTC | Jun 24, 12:40 UTC | 4h 0m |
| 2026-06-21 | SVA202 | FCO → JED | Jun 21, 14:30 UTC | Jun 21, 16:39 UTC | 2h 10m |
| 2026-06-20 | SVA201 | JED → FCO | Jun 20, 18:04 UTC | Jun 21, 12:10 UTC | 18h 5m |
| 2026-06-20 | SVA201 | JED → FCO | Jun 20, 16:05 UTC | Jun 21, 12:10 UTC | 20h 5m |
| 2026-06-20 | SVA168 | FRA → JED | Jun 20, 14:35 UTC | Jun 21, 12:10 UTC | 21h 35m |
| 2026-06-20 | SVA167 | JED → FRA | Jun 20, 08:34 UTC | Jun 20, 12:09 UTC | 3h 35m |
| 2026-06-19 | SVA167 | JED → FRA | Jun 19, 16:04 UTC | Jun 20, 12:09 UTC | 20h 5m |
| 2026-06-19 | SVA167 | JED → FRA | Jun 19, 14:34 UTC | Jun 20, 11:59 UTC | 21h 25m |
| 2026-06-19 | SVA207 | - | Jun 19, 08:50 UTC | Jun 19, 12:04 UTC | 3h 15m |
| 2026-06-18 | SVA207 | - | Jun 18, 14:30 UTC | Jun 19, 12:04 UTC | 21h 34m |
| 2026-06-17 | SVA554 | RUH → DXB | Jun 17, 18:05 UTC | Jun 18, 12:40 UTC | 18h 35m |
| 2026-06-17 | SVA208 | FCO → RUH | Jun 17, 16:05 UTC | Jun 18, 12:40 UTC | 20h 35m |
| 2026-06-17 | SVA208 | FCO → RUH | Jun 17, 14:35 UTC | Jun 18, 12:40 UTC | 22h 5m |
| 2026-06-17 | SVA207 | - | Jun 17, 09:20 UTC | Jun 17, 12:20 UTC | 3h 0m |
| 2026-06-16 | SVA207 | - | Jun 16, 16:05 UTC | Jun 17, 12:20 UTC | 20h 16m |
| 2026-06-16 | SVA207 | - | Jun 16, 14:30 UTC | Jun 17, 12:20 UTC | 21h 51m |
| 2026-06-16 | SVA201 | JED → FCO | Jun 16, 10:00 UTC | Jun 16, 12:05 UTC | 2h 5m |
| 2026-06-13 | SVA202 | FCO → JED | Jun 13, 14:20 UTC | Jun 13, 16:40 UTC | 2h 20m |
| 2026-06-13 | SVA201 | JED → FCO | Jun 13, 09:35 UTC | Jun 13, 12:20 UTC | 2h 45m |
| 2026-06-10 | SVA208 | FCO → RUH | Jun 10, 14:30 UTC | Jun 10, 17:15 UTC | 2h 45m |
| 2026-06-10 | SVA207 | RUH → FCO | Jun 10, 09:10 UTC | Jun 10, 12:30 UTC | 3h 20m |
| 2026-06-09 | SVA207 | RUH → FCO | Jun 9, 16:50 UTC | Jun 10, 12:30 UTC | 19h 40m |
| 2026-06-09 | SVA207 | RUH → FCO | Jun 9, 14:25 UTC | Jun 10, 12:30 UTC | 22h 5m |
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-ASA page for operator, model, and routing details .