sensors Mode-S transponder
710412
ICAO 24-bit transponder address · allocated to Saudi Arabia
Currently assigned to HZ-AS72 · AIRBUS A-320
- Hex
- 710412
- Octal
- 34202022
- Decimal
- 7,406,610
- Country
- SA
- Tail
- HZ-AS72
- Type
- A320
- Flights observed
- 57
- Distinct callsigns
- 20
- Country
- SA
- Last broadcast
- 18h ago
Last known position
Country allocation
The ICAO 24-bit address 710412 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 |
|---|---|---|---|
| SVA572 | - | 5 | 2026-06-24 |
| SVA570 | Saudi Arabian Airlines | 4 | 2026-04-24 |
| SVA571 | Saudi Arabian Airlines | 3 | 2026-04-24 |
| SVA521 | - | 3 | 2026-06-27 |
| SVA1161 | - | 3 | 2026-07-15 |
| SVA1115 | Saudi Arabian Airlines | 3 | 2026-04-21 |
| SVA636 | - | 2 | 2026-06-15 |
| SVA634 | - | 2 | 2026-07-14 |
| SVA631 | Saudi Arabian Airlines | 2 | 2026-06-13 |
| SVA520 | - | 2 | 2026-06-25 |
| SVA1131 | - | 2 | 2026-07-04 |
| SVA635 | Saudi Arabian Airlines | 1 | 2026-06-15 |
| SVA633 | - | 1 | 2026-07-14 |
| SVA632 | Saudi Arabian Airlines | 1 | 2026-06-09 |
| SVA628 | Saudi Arabian Airlines | 1 | 2026-06-10 |
| SVA627 | Saudi Arabian Airlines | 1 | 2026-06-09 |
| SVA591 | - | 1 | 2026-07-13 |
| SVA580 | - | 1 | 2026-07-13 |
| SVA573 | Saudi Arabian Airlines | 1 | 2026-06-24 |
| SVA541 | Saudi Arabian Airlines | 1 | 2026-07-16 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-17 | SVA1295 | RUH → URY | Jul 17, 06:20 UTC | Jul 17, 06:29 UTC | 10m |
| 2026-07-16 | SVA541 | DOH → RUH | Jul 16, 12:09 UTC | Jul 16, 12:44 UTC | 35m |
| 2026-07-16 | SVA540 | - | Jul 16, 10:10 UTC | Jul 16, 10:59 UTC | 50m |
| 2026-07-15 | SVA1161 | - | Jul 15, 22:20 UTC | Jul 15, 22:30 UTC | 10m |
| 2026-07-15 | SVA196 | - | Jul 15, 12:15 UTC | Jul 15, 14:20 UTC | 2h 5m |
| 2026-07-14 | SVA195 | - | Jul 14, 19:30 UTC | Jul 15, 10:30 UTC | 14h 59m |
| 2026-07-14 | SVA634 | - | Jul 14, 12:40 UTC | Jul 14, 17:55 UTC | 5h 15m |
| 2026-07-14 | SVA633 | - | Jul 14, 10:40 UTC | Jul 14, 11:15 UTC | 35m |
| 2026-07-13 | SVA591 | - | Jul 13, 08:40 UTC | Jul 13, 09:30 UTC | 50m |
| 2026-07-13 | SVA580 | - | Jul 13, 05:45 UTC | Jul 13, 06:55 UTC | 1h 10m |
| 2026-07-12 | - | - | Jul 12, 03:25 UTC | Jul 12, 03:35 UTC | 10m |
| 2026-07-04 | SVA1131 | - | Jul 4, 22:35 UTC | Jul 4, 22:45 UTC | 10m |
| 2026-06-27 | SVA521 | - | Jun 27, 15:05 UTC | Jun 27, 15:24 UTC | 20m |
| 2026-06-25 | SVA521 | - | Jun 25, 14:55 UTC | Jun 25, 15:10 UTC | 15m |
| 2026-06-25 | SVA520 | - | Jun 25, 13:09 UTC | Jun 25, 13:24 UTC | 15m |
| 2026-06-24 | SVA573 | AUH → RUH | Jun 24, 11:39 UTC | Jun 24, 12:25 UTC | 45m |
| 2026-06-24 | SVA572 | - | Jun 24, 09:09 UTC | Jun 24, 10:10 UTC | 1h 0m |
| 2026-06-23 | SVA572 | - | Jun 23, 11:54 UTC | Jun 24, 10:10 UTC | 22h 15m |
| 2026-06-23 | SVA572 | - | Jun 23, 09:40 UTC | Jun 23, 10:39 UTC | 1h 0m |
| 2026-06-19 | SVA1160 | RUH → DMM | Jun 19, 16:59 UTC | Jun 19, 17:09 UTC | 10m |
| 2026-06-17 | SVA1161 | DMM → RUH | Jun 17, 22:20 UTC | Jun 17, 22:30 UTC | 10m |
| 2026-06-15 | SVA636 | - | Jun 15, 17:45 UTC | Jun 15, 17:54 UTC | 10m |
| 2026-06-15 | SVA635 | JED → AMM | Jun 15, 15:55 UTC | Jun 15, 16:04 UTC | 10m |
| 2026-06-13 | SVA631 | JED → AMM | Jun 13, 08:40 UTC | Jun 13, 09:00 UTC | 20m |
| 2026-06-13 | SVA1127 | DMM → JED | Jun 13, 01:20 UTC | Jun 13, 01:30 UTC | 10m |
| 2026-06-12 | SVA1128 | JED → DMM | Jun 12, 23:20 UTC | Jun 12, 23:45 UTC | 25m |
| 2026-06-11 | SVA1131 | DMM → RUH | Jun 11, 22:35 UTC | Jun 11, 22:45 UTC | 10m |
| 2026-06-10 | SVA628 | AMM → JED | Jun 10, 01:35 UTC | Jun 10, 01:50 UTC | 15m |
| 2026-06-09 | SVA627 | JED → AMM | Jun 9, 23:40 UTC | Jun 9, 23:55 UTC | 15m |
| 2026-06-09 | SVA636 | AMM → JED | Jun 9, 17:55 UTC | Jun 9, 18:10 UTC | 15m |
| 2026-06-09 | SVA632 | AMM → JED | Jun 9, 10:40 UTC | Jun 9, 10:55 UTC | 15m |
| 2026-06-09 | SVA631 | JED → AMM | Jun 9, 08:30 UTC | Jun 9, 08:50 UTC | 20m |
| 2026-06-07 | SVA410 | HBE → JED | Jun 7, 17:35 UTC | Jun 7, 18:05 UTC | 30m |
| 2026-06-07 | SVA411 | JED → HBE | Jun 7, 07:35 UTC | Jun 7, 16:15 UTC | 8h 40m |
| 2026-05-30 | SVA1165 | DMM → RUH | May 30, 18:15 UTC | May 30, 18:30 UTC | 15m |
| 2026-05-29 | SVA1169 | DMM → RUH | May 29, 20:30 UTC | May 29, 20:40 UTC | 10m |
| 2026-05-29 | SVA1163 | DMM → RUH | May 29, 16:25 UTC | May 29, 16:35 UTC | 10m |
| 2026-05-23 | SVA634 | AMM → RUH | May 23, 12:45 UTC | May 23, 12:55 UTC | 10m |
| 2026-05-21 | SVA521 | BAH → RUH | May 21, 15:00 UTC | May 21, 15:25 UTC | 25m |
| 2026-05-21 | SVA520 | RUH → BAH | May 21, 13:20 UTC | May 21, 13:35 UTC | 15m |
| 2026-05-18 | SVA572 | JED → AUH | May 18, 09:05 UTC | May 18, 12:25 UTC | 3h 20m |
| 2026-05-12 | SVA1161 | DMM → RUH | May 12, 22:31 UTC | May 12, 22:40 UTC | 10m |
| 2026-05-10 | SVA572 | JED → AUH | May 10, 10:10 UTC | May 10, 13:05 UTC | 2h 55m |
| 2026-04-24 | SVA571 | AUH → JED | Apr 24, 13:05 UTC | Apr 24, 22:45 UTC | 9h 40m |
| 2026-04-24 | SVA570 | RUH → AUH | Apr 24, 10:05 UTC | Apr 24, 11:05 UTC | 1h 0m |
| 2026-04-23 | SVA570 | RUH → AUH | Apr 23, 13:00 UTC | Apr 24, 11:05 UTC | 22h 5m |
| 2026-04-22 | SVA570 | RUH → AUH | Apr 22, 19:30 UTC | Apr 23, 10:45 UTC | 15h 15m |
| 2026-04-22 | SVA1124 | JED → DMM | Apr 22, 17:55 UTC | Apr 22, 18:10 UTC | 15m |
| 2026-04-21 | SVA1115 | DMM → JED | Apr 21, 13:20 UTC | Apr 21, 13:30 UTC | 10m |
| 2026-04-21 | - | - | Apr 21, 01:20 UTC | Apr 21, 01:30 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-AS72 page for operator, model, and routing details .