sensors Mode-S transponder
710113
ICAO 24-bit transponder address · allocated to Saudi Arabia
Currently assigned to HZ-AS51 · AIRBUS A-320
- Hex
- 710113
- Octal
- 34200423
- Decimal
- 7,405,843
- Country
- SA
- Tail
- HZ-AS51
- Type
- A320
- Flights observed
- 39
- Distinct callsigns
- 20
- Country
- SA
- Last broadcast
- 9d ago
Last known position
Country allocation
The ICAO 24-bit address 710113 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 |
|---|---|---|---|
| SVA540 | Saudi Arabian Airlines | 5 | 2026-07-25 |
| SVA541 | Saudi Arabian Airlines | 3 | 2026-07-25 |
| SVA202 | Saudi Arabian Airlines | 3 | 2026-05-28 |
| SVA629 | Saudi Arabian Airlines | 2 | 2026-06-11 |
| SVA572 | Saudi Arabian Airlines | 2 | 2026-06-13 |
| SVA201 | Saudi Arabian Airlines | 2 | 2026-05-28 |
| SVA1107 | - | 2 | 2026-07-21 |
| SVA636 | - | 1 | 2026-06-18 |
| SVA634 | Saudi Arabian Airlines | 1 | 2026-06-09 |
| SVA630 | Saudi Arabian Airlines | 1 | 2026-06-06 |
| SVA590 | - | 1 | 2026-07-08 |
| SVA573 | Saudi Arabian Airlines | 1 | 2026-04-22 |
| SVA569 | - | 1 | 2026-07-09 |
| SVA568 | - | 1 | 2026-07-09 |
| SVA550 | - | 1 | 2026-07-08 |
| SVA527 | Saudi Arabian Airlines | 1 | 2026-05-30 |
| SVA526 | Saudi Arabian Airlines | 1 | 2026-05-30 |
| SVA521 | Saudi Arabian Airlines | 1 | 2026-06-01 |
| SVA411 | Saudi Arabian Airlines | 1 | 2026-07-13 |
| SVA410 | - | 1 | 2026-07-13 |
Recent flights last 39
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-25 | SVA541 | DOH → RUH | Jul 25, 12:00 UTC | Jul 25, 12:40 UTC | 40m |
| 2026-07-25 | SVA540 | RUH → DOH | Jul 25, 10:15 UTC | Jul 25, 10:45 UTC | 30m |
| 2026-07-24 | SVA541 | DOH → RUH | Jul 24, 12:05 UTC | Jul 25, 10:45 UTC | 22h 40m |
| 2026-07-24 | SVA540 | RUH → DOH | Jul 24, 10:25 UTC | Jul 24, 11:05 UTC | 40m |
| 2026-07-22 | SVA1038 | - | Jul 22, 14:30 UTC | Jul 22, 14:40 UTC | 10m |
| 2026-07-21 | SVA1107 | - | Jul 21, 07:55 UTC | Jul 21, 08:15 UTC | 20m |
| 2026-07-20 | SVA1107 | - | Jul 20, 11:50 UTC | Jul 21, 08:15 UTC | 20h 24m |
| 2026-07-18 | SVA1105 | DMM → JED | Jul 18, 03:50 UTC | Jul 18, 04:05 UTC | 15m |
| 2026-07-13 | SVA410 | - | Jul 13, 17:40 UTC | Jul 13, 18:25 UTC | 45m |
| 2026-07-13 | SVA411 | JED → HBE | Jul 13, 15:30 UTC | Jul 13, 16:10 UTC | 40m |
| 2026-07-09 | SVA569 | - | Jul 9, 12:00 UTC | Jul 9, 12:50 UTC | 50m |
| 2026-07-09 | SVA568 | - | Jul 9, 02:50 UTC | Jul 9, 10:30 UTC | 7h 40m |
| 2026-07-08 | SVA590 | - | Jul 8, 17:50 UTC | Jul 9, 00:10 UTC | 6h 20m |
| 2026-07-08 | SVA550 | - | Jul 8, 14:20 UTC | Jul 8, 15:30 UTC | 1h 10m |
| 2026-07-02 | SVA1296 | - | Jul 2, 19:40 UTC | Jul 2, 20:00 UTC | 20m |
| 2026-07-02 | SVA1297 | - | Jul 2, 17:30 UTC | Jul 2, 17:45 UTC | 15m |
| 2026-07-01 | SVA1290 | - | Jul 1, 12:10 UTC | Jul 1, 12:20 UTC | 10m |
| 2026-07-01 | SVA1291 | - | Jul 1, 10:40 UTC | Jul 1, 10:50 UTC | 10m |
| 2026-06-26 | SVA541 | DOH → RUH | Jun 26, 12:10 UTC | Jun 26, 12:50 UTC | 40m |
| 2026-06-26 | SVA540 | RUH → DOH | Jun 26, 10:10 UTC | Jun 26, 10:50 UTC | 40m |
| 2026-06-18 | SVA636 | - | Jun 18, 17:55 UTC | Jun 18, 18:10 UTC | 15m |
| 2026-06-13 | SVA572 | JED → AUH | Jun 13, 09:00 UTC | Jun 13, 09:30 UTC | 30m |
| 2026-06-11 | SVA629 | RUH → AMM | Jun 11, 09:00 UTC | Jun 11, 09:10 UTC | 10m |
| 2026-06-09 | SVA634 | AMM → RUH | Jun 9, 12:40 UTC | Jun 9, 12:50 UTC | 10m |
| 2026-06-06 | SVA630 | AMM → RUH | Jun 6, 10:34 UTC | Jun 6, 10:50 UTC | 15m |
| 2026-06-06 | SVA629 | RUH → AMM | Jun 6, 08:50 UTC | Jun 6, 09:09 UTC | 20m |
| 2026-06-01 | SVA521 | BAH → RUH | Jun 1, 15:00 UTC | Jun 1, 15:15 UTC | 15m |
| 2026-05-30 | SVA527 | BAH → JED | May 30, 17:25 UTC | May 30, 17:45 UTC | 20m |
| 2026-05-30 | SVA526 | JED → BAH | May 30, 15:35 UTC | May 30, 16:05 UTC | 30m |
| 2026-05-28 | SVA202 | FCO → JED | May 28, 14:50 UTC | May 29, 08:50 UTC | 18h 0m |
| 2026-05-28 | SVA202 | FCO → JED | May 28, 14:30 UTC | May 29, 08:50 UTC | 18h 20m |
| 2026-05-28 | SVA201 | JED → FCO | May 28, 09:35 UTC | May 28, 12:15 UTC | 2h 40m |
| 2026-05-19 | SVA540 | RUH → DOH | May 19, 10:10 UTC | May 19, 10:40 UTC | 30m |
| 2026-05-07 | SVA540 | RUH → DOH | May 7, 10:30 UTC | May 7, 11:05 UTC | 35m |
| 2026-05-05 | SVA202 | FCO → JED | May 5, 14:30 UTC | May 5, 16:10 UTC | 1h 40m |
| 2026-05-05 | SVA201 | JED → FCO | May 5, 10:15 UTC | May 5, 12:15 UTC | 2h 0m |
| 2026-04-22 | SVA573 | AUH → RUH | Apr 22, 12:45 UTC | Apr 22, 13:40 UTC | 55m |
| 2026-04-22 | SVA572 | JED → AUH | Apr 22, 09:55 UTC | Apr 22, 10:50 UTC | 55m |
| 2026-04-13 | SVA1133 | - | Apr 13, 04:10 UTC | Apr 13, 04:20 UTC | 10m |
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-AS51 page for operator, model, and routing details .