sensors Mode-S transponder
710071
ICAO 24-bit transponder address · allocated to Saudi Arabia
Currently assigned to HZ-ASB · AIRBUS A-320
- Hex
- 710071
- Octal
- 34200161
- Decimal
- 7,405,681
- Country
- SA
- Tail
- HZ-ASB
- Type
- A320
- Flights observed
- 148
- Distinct callsigns
- 20
- Country
- SA
- Last broadcast
- 9h ago
Last known position
Country allocation
The ICAO 24-bit address 710071 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 |
|---|---|---|---|
| SVA153 | - | 17 | 2026-07-15 |
| SVA175 | - | 14 | 2026-07-09 |
| SVA207 | - | 13 | 2026-07-05 |
| SVA235 | - | 12 | 2026-07-12 |
| SVA201 | - | 9 | 2026-06-28 |
| SVA167 | - | 9 | 2026-07-13 |
| SVA174 | Saudi Arabian Airlines | 8 | 2026-07-09 |
| SVA234 | Saudi Arabian Airlines | 7 | 2026-07-13 |
| SVA209 | - | 7 | 2026-07-15 |
| SVA206 | - | 7 | 2026-07-16 |
| SVA151 | Saudi Arabian Airlines | 6 | 2026-06-03 |
| SVA179 | - | 5 | 2026-06-28 |
| SVA152 | Saudi Arabian Airlines | 4 | 2026-05-15 |
| SVA202 | Saudi Arabian Airlines | 3 | 2026-06-20 |
| SVA180 | Saudi Arabian Airlines | 3 | 2026-06-29 |
| SVA168 | Saudi Arabian Airlines | 3 | 2026-07-05 |
| SVA150 | Saudi Arabian Airlines | 3 | 2026-06-04 |
| SVA572 | Saudi Arabian Airlines | 2 | 2026-04-27 |
| SVA195 | - | 2 | 2026-06-23 |
| SVA628 | - | 1 | 2026-06-20 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-17 | SVA240 | - | Jul 17, 15:55 UTC | Jul 17, 17:35 UTC | 1h 40m |
| 2026-07-17 | SVA241 | - | Jul 17, 12:25 UTC | Jul 17, 14:10 UTC | 1h 45m |
| 2026-07-16 | SVA206 | - | Jul 16, 08:00 UTC | Jul 16, 10:40 UTC | 2h 40m |
| 2026-07-15 | SVA209 | VIE → FCO | Jul 15, 14:45 UTC | Jul 16, 04:40 UTC | 13h 55m |
| 2026-07-15 | SVA153 | - | Jul 15, 09:15 UTC | Jul 15, 12:45 UTC | 3h 30m |
| 2026-07-14 | SVA153 | - | Jul 14, 16:20 UTC | Jul 15, 12:45 UTC | 20h 24m |
| 2026-07-14 | SVA153 | FRA → VIE | Jul 14, 14:30 UTC | Jul 15, 12:45 UTC | 22h 14m |
| 2026-07-13 | SVA167 | - | Jul 13, 18:20 UTC | Jul 14, 12:35 UTC | 18h 15m |
| 2026-07-13 | SVA167 | - | Jul 13, 16:20 UTC | Jul 14, 12:35 UTC | 20h 15m |
| 2026-07-13 | SVA234 | ZRH → RUH | Jul 13, 14:35 UTC | Jul 14, 12:35 UTC | 22h 0m |
| 2026-07-12 | SVA235 | - | Jul 12, 18:20 UTC | Jul 13, 12:35 UTC | 18h 15m |
| 2026-07-12 | SVA235 | - | Jul 12, 16:20 UTC | Jul 13, 12:35 UTC | 20h 15m |
| 2026-07-12 | SVA235 | ZRH → ZRH | Jul 12, 14:30 UTC | Jul 13, 12:35 UTC | 22h 5m |
| 2026-07-12 | SVA235 | - | Jul 12, 08:40 UTC | Jul 12, 12:45 UTC | 4h 5m |
| 2026-07-09 | SVA174 | MUC → JED | Jul 9, 14:45 UTC | Jul 9, 17:50 UTC | 3h 5m |
| 2026-07-09 | SVA175 | - | Jul 9, 10:05 UTC | Jul 9, 13:00 UTC | 2h 55m |
| 2026-07-08 | SVA206 | - | Jul 8, 07:20 UTC | Jul 8, 09:00 UTC | 1h 40m |
| 2026-07-08 | SVA209 | - | Jul 8, 01:40 UTC | Jul 8, 05:00 UTC | 3h 20m |
| 2026-07-06 | SVA208 | FCO → RUH | Jul 6, 14:30 UTC | Jul 6, 17:10 UTC | 2h 40m |
| 2026-07-05 | SVA207 | - | Jul 5, 16:20 UTC | Jul 6, 12:15 UTC | 19h 55m |
| 2026-07-05 | SVA168 | FRA → JED | Jul 5, 14:35 UTC | Jul 6, 12:15 UTC | 21h 40m |
| 2026-07-05 | SVA167 | - | Jul 5, 09:30 UTC | Jul 5, 12:30 UTC | 3h 0m |
| 2026-07-04 | SVA167 | - | Jul 4, 16:20 UTC | Jul 5, 12:30 UTC | 20h 10m |
| 2026-07-04 | SVA167 | FRA → FRA | Jul 4, 14:35 UTC | Jul 5, 12:30 UTC | 21h 55m |
| 2026-07-04 | SVA167 | - | Jul 4, 09:20 UTC | Jul 4, 12:25 UTC | 3h 5m |
| 2026-07-01 | SVA272 | - | Jul 1, 10:55 UTC | Jul 1, 12:15 UTC | 1h 20m |
| 2026-07-01 | SVA273 | - | Jul 1, 07:20 UTC | Jul 1, 08:45 UTC | 1h 25m |
| 2026-06-29 | SVA180 | FRA → RUH | Jun 29, 14:34 UTC | Jun 29, 18:39 UTC | 4h 5m |
| 2026-06-28 | SVA179 | - | Jun 28, 16:19 UTC | Jun 29, 11:50 UTC | 19h 30m |
| 2026-06-28 | SVA179 | - | Jun 28, 14:30 UTC | Jun 29, 11:50 UTC | 21h 20m |
| 2026-06-28 | SVA201 | - | Jun 28, 09:39 UTC | Jun 28, 12:19 UTC | 2h 40m |
| 2026-06-27 | SVA174 | MUC → JED | Jun 27, 14:49 UTC | Jun 28, 12:19 UTC | 21h 30m |
| 2026-06-27 | SVA175 | - | Jun 27, 09:09 UTC | Jun 27, 12:34 UTC | 3h 25m |
| 2026-06-25 | SVA174 | MUC → JED | Jun 25, 14:39 UTC | Jun 25, 18:04 UTC | 3h 25m |
| 2026-06-25 | SVA175 | - | Jun 25, 09:29 UTC | Jun 25, 12:40 UTC | 3h 10m |
| 2026-06-24 | SVA175 | - | Jun 24, 14:20 UTC | Jun 25, 12:40 UTC | 22h 20m |
| 2026-06-24 | SVA175 | - | Jun 24, 12:20 UTC | Jun 25, 12:15 UTC | 23h 55m |
| 2026-06-23 | SVA195 | - | Jun 23, 14:35 UTC | Jun 24, 10:39 UTC | 20h 5m |
| 2026-06-23 | SVA201 | JED → FCO | Jun 23, 09:45 UTC | Jun 23, 12:20 UTC | 2h 35m |
| 2026-06-20 | SVA202 | FCO → JED | Jun 20, 14:24 UTC | Jun 20, 17:10 UTC | 2h 45m |
| 2026-06-20 | SVA201 | JED → FCO | Jun 20, 09:19 UTC | Jun 20, 11:54 UTC | 2h 35m |
| 2026-06-20 | SVA628 | - | Jun 20, 01:50 UTC | Jun 20, 02:04 UTC | 15m |
| 2026-06-19 | SVA627 | - | Jun 19, 23:34 UTC | Jun 19, 23:54 UTC | 20m |
| 2026-06-15 | SVA196 | - | Jun 15, 12:19 UTC | Jun 15, 14:20 UTC | 2h 0m |
| 2026-06-15 | SVA195 | - | Jun 15, 08:40 UTC | Jun 15, 10:24 UTC | 1h 45m |
| 2026-06-11 | SVA206 | FCO → RUH | Jun 11, 07:55 UTC | Jun 11, 10:40 UTC | 2h 45m |
| 2026-06-11 | SVA209 | RUH → FCO | Jun 11, 01:40 UTC | Jun 11, 05:00 UTC | 3h 20m |
| 2026-06-08 | SVA180 | FRA → RUH | Jun 8, 14:35 UTC | Jun 9, 09:20 UTC | 18h 45m |
| 2026-06-08 | SVA179 | RUH → FRA | Jun 8, 09:05 UTC | Jun 8, 12:35 UTC | 3h 30m |
| 2026-06-06 | SVA174 | MUC → JED | Jun 6, 14:50 UTC | Jun 6, 17:24 UTC | 2h 35m |
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-ASB page for operator, model, and routing details .