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