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