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