sensors Mode-S transponder
710413
ICAO 24-bit transponder address · allocated to Saudi Arabia
Currently assigned to HZ-AS73 · AIRBUS A-320
- Hex
- 710413
- Octal
- 34202023
- Decimal
- 7,406,611
- Country
- SA
- Tail
- HZ-AS73
- Type
- A320
- Flights observed
- 45
- Distinct callsigns
- 20
- Country
- SA
- Last broadcast
- 21h ago
Last known position
Country allocation
The ICAO 24-bit address 710413 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 |
|---|---|---|---|
| SVA570 | Saudi Arabian Airlines | 4 | 2026-05-25 |
| SVA540 | Saudi Arabian Airlines | 4 | 2026-07-05 |
| SVA638 | - | 3 | 2026-07-01 |
| SVA637 | - | 3 | 2026-07-01 |
| SVA634 | Saudi Arabian Airlines | 2 | 2026-06-26 |
| SVA633 | - | 2 | 2026-06-26 |
| SVA571 | Saudi Arabian Airlines | 2 | 2026-04-26 |
| SVA541 | Saudi Arabian Airlines | 2 | 2026-07-05 |
| SVA208 | - | 2 | 2026-04-17 |
| SVA207 | Saudi Arabian Airlines | 2 | 2026-04-17 |
| SVA1131 | Saudi Arabian Airlines | 2 | 2026-06-06 |
| SVA628 | Saudi Arabian Airlines | 1 | 2026-06-13 |
| SVA627 | Saudi Arabian Airlines | 1 | 2026-06-12 |
| SVA593 | - | 1 | 2026-07-05 |
| SVA592 | - | 1 | 2026-07-04 |
| SVA573 | Saudi Arabian Airlines | 1 | 2026-06-25 |
| SVA572 | - | 1 | 2026-06-25 |
| SVA521 | Saudi Arabian Airlines | 1 | 2026-05-30 |
| SVA411 | Saudi Arabian Airlines | 1 | 2026-04-28 |
| SVA410 | Saudi Arabian Airlines | 1 | 2026-04-28 |
Recent flights last 45
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | SVA1291 | - | Jul 13, 10:25 UTC | Jul 13, 10:35 UTC | 10m |
| 2026-07-09 | SVA1133 | - | Jul 9, 04:05 UTC | Jul 9, 04:15 UTC | 10m |
| 2026-07-06 | SVA1297 | - | Jul 6, 18:10 UTC | Jul 6, 18:20 UTC | 10m |
| 2026-07-06 | SVA1167 | - | Jul 6, 02:20 UTC | Jul 6, 02:30 UTC | 10m |
| 2026-07-05 | SVA541 | DOH → RUH | Jul 5, 12:05 UTC | Jul 5, 12:45 UTC | 40m |
| 2026-07-05 | SVA540 | RUH → DOH | Jul 5, 01:35 UTC | Jul 5, 10:50 UTC | 9h 15m |
| 2026-07-05 | SVA593 | - | Jul 5, 01:15 UTC | Jul 5, 01:30 UTC | 15m |
| 2026-07-04 | SVA592 | - | Jul 4, 21:00 UTC | Jul 4, 22:20 UTC | 1h 20m |
| 2026-07-01 | SVA638 | - | Jul 1, 19:30 UTC | Jul 1, 20:00 UTC | 30m |
| 2026-07-01 | SVA637 | - | Jul 1, 17:55 UTC | Jul 1, 18:20 UTC | 25m |
| 2026-06-26 | SVA638 | - | Jun 26, 19:30 UTC | Jun 26, 19:39 UTC | 10m |
| 2026-06-26 | SVA637 | RUH → AMM | Jun 26, 17:40 UTC | Jun 26, 17:54 UTC | 15m |
| 2026-06-26 | SVA634 | AMM → RUH | Jun 26, 12:39 UTC | Jun 26, 12:55 UTC | 15m |
| 2026-06-26 | SVA633 | - | Jun 26, 11:00 UTC | Jun 26, 11:09 UTC | 10m |
| 2026-06-25 | SVA573 | AUH → RUH | Jun 25, 11:19 UTC | Jun 25, 12:04 UTC | 45m |
| 2026-06-25 | SVA572 | - | Jun 25, 09:05 UTC | Jun 25, 09:59 UTC | 55m |
| 2026-06-22 | SVA638 | AMM → RUH | Jun 22, 19:24 UTC | Jun 22, 19:40 UTC | 15m |
| 2026-06-22 | SVA637 | RUH → AMM | Jun 22, 17:40 UTC | Jun 22, 17:55 UTC | 15m |
| 2026-06-22 | SVA634 | AMM → RUH | Jun 22, 12:49 UTC | Jun 22, 12:59 UTC | 10m |
| 2026-06-22 | SVA633 | RUH → AMM | Jun 22, 11:00 UTC | Jun 22, 11:09 UTC | 10m |
| 2026-06-13 | SVA628 | AMM → JED | Jun 13, 01:30 UTC | Jun 13, 01:45 UTC | 15m |
| 2026-06-12 | SVA627 | JED → AMM | Jun 12, 23:40 UTC | Jun 12, 23:55 UTC | 15m |
| 2026-06-06 | SVA1131 | DMM → RUH | Jun 6, 22:20 UTC | Jun 6, 22:30 UTC | 10m |
| 2026-06-05 | SVA1131 | DMM → RUH | Jun 5, 22:15 UTC | Jun 5, 22:25 UTC | 10m |
| 2026-06-02 | SVA541 | DOH → RUH | Jun 2, 12:10 UTC | Jun 2, 12:45 UTC | 35m |
| 2026-06-02 | SVA540 | RUH → DOH | Jun 2, 10:10 UTC | Jun 2, 10:50 UTC | 40m |
| 2026-05-30 | SVA521 | BAH → RUH | May 30, 15:05 UTC | May 30, 15:25 UTC | 20m |
| 2026-05-28 | SVA540 | RUH → DOH | May 28, 10:10 UTC | May 28, 10:50 UTC | 40m |
| 2026-05-27 | SVA540 | RUH → DOH | May 27, 13:35 UTC | May 28, 10:50 UTC | 21h 15m |
| 2026-05-25 | SVA570 | RUH → AUH | May 25, 10:05 UTC | May 25, 10:40 UTC | 35m |
| 2026-05-24 | SVA570 | RUH → AUH | May 24, 11:40 UTC | May 25, 10:40 UTC | 23h 0m |
| 2026-05-15 | SVA204 | FCO → JED | May 15, 08:00 UTC | May 15, 10:05 UTC | 2h 5m |
| 2026-05-15 | SVA203 | JED → FCO | May 15, 03:05 UTC | May 15, 05:40 UTC | 2h 35m |
| 2026-04-28 | SVA410 | HBE → JED | Apr 28, 17:45 UTC | Apr 29, 09:45 UTC | 16h 0m |
| 2026-04-28 | SVA411 | JED → HBE | Apr 28, 16:05 UTC | Apr 28, 16:30 UTC | 25m |
| 2026-04-26 | SVA571 | AUH → JED | Apr 26, 12:55 UTC | Apr 26, 13:45 UTC | 50m |
| 2026-04-26 | SVA570 | RUH → AUH | Apr 26, 10:10 UTC | Apr 26, 10:50 UTC | 40m |
| 2026-04-24 | SVA1145 | DMM → RUH | Apr 24, 14:15 UTC | Apr 24, 14:25 UTC | 10m |
| 2026-04-18 | SVA571 | AUH → JED | Apr 18, 12:55 UTC | Apr 18, 13:45 UTC | 50m |
| 2026-04-18 | SVA570 | RUH → AUH | Apr 18, 10:30 UTC | Apr 18, 11:15 UTC | 45m |
| 2026-04-17 | SVA208 | - | Apr 17, 15:20 UTC | Apr 17, 16:15 UTC | 55m |
| 2026-04-17 | SVA208 | - | Apr 17, 14:20 UTC | Apr 17, 15:15 UTC | 54m |
| 2026-04-17 | SVA207 | RUH → FCO | Apr 17, 11:20 UTC | Apr 17, 12:10 UTC | 50m |
| 2026-04-17 | SVA207 | RUH → FCO | Apr 17, 09:25 UTC | Apr 17, 11:15 UTC | 1h 50m |
| 2026-04-13 | SVA1143 | DMM → RUH | Apr 13, 10:15 UTC | Apr 13, 10:25 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-AS73 page for operator, model, and routing details .