sensors Mode-S transponder
711537
ICAO 24-bit transponder address · allocated to Saudi Arabia
Currently assigned to HZ-ASAH · AIRBUS A-321neo
- Hex
- 711537
- Octal
- 34212467
- Decimal
- 7,410,999
- Country
- SA
- Tail
- HZ-ASAH
- Type
- A21N
- Flights observed
- 124
- Distinct callsigns
- 20
- Country
- SA
- Last broadcast
- 6h ago
Last known position
Country allocation
The ICAO 24-bit address 711537 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 |
|---|---|---|---|
| SVA712 | - | 13 | 2026-06-27 |
| SVA267 | Saudi Arabian Airlines | 9 | 2026-07-11 |
| SVA264 | Saudi Arabian Airlines | 7 | 2026-07-12 |
| SVA263 | - | 6 | 2026-07-11 |
| SVA261 | Saudi Arabian Airlines | 6 | 2026-05-17 |
| SVA259 | Saudi Arabian Airlines | 5 | 2026-05-07 |
| SVA258 | Saudi Arabian Airlines | 5 | 2026-05-08 |
| SVA208 | Saudi Arabian Airlines | 5 | 2026-07-01 |
| SVA713 | - | 4 | 2026-06-24 |
| SVA554 | Saudi Arabian Airlines | 4 | 2026-06-28 |
| SVA268 | - | 4 | 2026-07-10 |
| SVA207 | - | 4 | 2026-06-30 |
| SVA278 | Saudi Arabian Airlines | 3 | 2026-04-26 |
| SVA265 | Saudi Arabian Airlines | 3 | 2026-05-16 |
| SVA260 | - | 3 | 2026-07-02 |
| SVA596 | - | 2 | 2026-06-15 |
| SVA588 | - | 2 | 2026-06-20 |
| SVA555 | Saudi Arabian Airlines | 2 | 2026-06-28 |
| SVA380 | Saudi Arabian Airlines | 2 | 2026-05-08 |
| SVA318 | Saudi Arabian Airlines | 2 | 2026-05-18 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | SVA334 | - | Jul 13, 19:55 UTC | Jul 13, 20:30 UTC | 35m |
| 2026-07-13 | SVA272 | - | Jul 13, 10:55 UTC | Jul 13, 18:40 UTC | 7h 45m |
| 2026-07-13 | SVA273 | - | Jul 13, 07:10 UTC | Jul 13, 08:40 UTC | 1h 30m |
| 2026-07-12 | SVA264 | IST → RUH | Jul 12, 13:45 UTC | Jul 12, 15:40 UTC | 1h 55m |
| 2026-07-11 | SVA263 | - | Jul 11, 17:05 UTC | Jul 12, 11:05 UTC | 18h 0m |
| 2026-07-11 | SVA267 | RUH → IST | Jul 11, 04:55 UTC | Jul 11, 14:15 UTC | 9h 20m |
| 2026-07-10 | SVA268 | - | Jul 10, 16:55 UTC | Jul 11, 01:40 UTC | 8h 45m |
| 2026-07-10 | SVA267 | RUH → IST | Jul 10, 05:45 UTC | Jul 10, 14:25 UTC | 8h 40m |
| 2026-07-09 | SVA268 | - | Jul 9, 16:45 UTC | Jul 10, 01:30 UTC | 8h 45m |
| 2026-07-08 | SVA267 | RUH → IST | Jul 8, 19:50 UTC | Jul 9, 14:35 UTC | 18h 45m |
| 2026-07-08 | SVA272 | - | Jul 8, 11:15 UTC | Jul 8, 18:30 UTC | 7h 15m |
| 2026-07-08 | SVA273 | - | Jul 8, 08:05 UTC | Jul 8, 09:35 UTC | 1h 30m |
| 2026-07-02 | SVA260 | - | Jul 2, 19:40 UTC | Jul 2, 21:35 UTC | 1h 55m |
| 2026-07-02 | SVA266 | - | Jul 2, 09:10 UTC | Jul 2, 17:45 UTC | 8h 35m |
| 2026-07-01 | SVA208 | FCO → RUH | Jul 1, 14:30 UTC | Jul 2, 07:30 UTC | 17h 0m |
| 2026-06-30 | SVA207 | - | Jun 30, 20:00 UTC | Jul 1, 12:30 UTC | 16h 30m |
| 2026-06-30 | SVA333 | RUH → HBE | Jun 30, 17:40 UTC | Jun 30, 18:30 UTC | 50m |
| 2026-06-30 | SVA1167 | - | Jun 30, 02:15 UTC | Jun 30, 02:25 UTC | 10m |
| 2026-06-28 | SVA555 | DXB → RUH | Jun 28, 14:25 UTC | Jun 28, 15:20 UTC | 55m |
| 2026-06-28 | SVA554 | RUH → DXB | Jun 28, 04:59 UTC | Jun 28, 12:55 UTC | 7h 55m |
| 2026-06-27 | SVA712 | - | Jun 27, 16:59 UTC | Jun 28, 01:29 UTC | 8h 30m |
| 2026-06-26 | SVA264 | IST → RUH | Jun 26, 13:34 UTC | Jun 26, 15:25 UTC | 1h 50m |
| 2026-06-26 | SVA263 | - | Jun 26, 09:24 UTC | Jun 26, 11:05 UTC | 1h 40m |
| 2026-06-24 | SVA713 | - | Jun 24, 04:44 UTC | Jun 24, 08:24 UTC | 3h 40m |
| 2026-06-23 | SVA712 | - | Jun 23, 14:29 UTC | Jun 24, 02:49 UTC | 12h 20m |
| 2026-06-23 | SVA554 | RUH → DXB | Jun 23, 11:40 UTC | Jun 23, 12:49 UTC | 1h 10m |
| 2026-06-22 | SVA554 | RUH → DXB | Jun 22, 13:49 UTC | Jun 23, 12:49 UTC | 23h 0m |
| 2026-06-22 | SVA196 | - | Jun 22, 12:44 UTC | Jun 23, 11:45 UTC | 23h 0m |
| 2026-06-22 | SVA195 | - | Jun 22, 08:35 UTC | Jun 22, 10:19 UTC | 1h 45m |
| 2026-06-21 | SVA521 | BAH → RUH | Jun 21, 15:05 UTC | Jun 21, 15:19 UTC | 15m |
| 2026-06-21 | SVA520 | - | Jun 21, 13:15 UTC | Jun 21, 13:29 UTC | 15m |
| 2026-06-20 | SVA588 | - | Jun 20, 10:34 UTC | Jun 20, 11:54 UTC | 1h 20m |
| 2026-06-18 | SVA1117 | DMM → JED | Jun 18, 15:35 UTC | Jun 18, 15:50 UTC | 15m |
| 2026-06-18 | SVA1105 | DMM → JED | Jun 18, 03:25 UTC | Jun 18, 03:45 UTC | 20m |
| 2026-06-16 | SVA588 | - | Jun 16, 10:45 UTC | Jun 16, 14:45 UTC | 4h 0m |
| 2026-06-15 | SVA1165 | DMM → RUH | Jun 15, 18:40 UTC | Jun 15, 18:50 UTC | 10m |
| 2026-06-15 | SVA596 | - | Jun 15, 06:49 UTC | Jun 15, 07:10 UTC | 20m |
| 2026-06-14 | SVA596 | - | Jun 14, 09:30 UTC | Jun 15, 07:10 UTC | 21h 39m |
| 2026-06-12 | SVA555 | DXB → RUH | Jun 12, 11:50 UTC | Jun 13, 07:20 UTC | 19h 29m |
| 2026-06-12 | SVA554 | RUH → DXB | Jun 12, 11:40 UTC | Jun 13, 07:20 UTC | 19h 39m |
| 2026-06-12 | SVA713 | CCJ → RUH | Jun 12, 04:50 UTC | Jun 12, 15:30 UTC | 10h 40m |
| 2026-06-11 | SVA712 | MED → KHI | Jun 11, 08:30 UTC | Jun 12, 02:40 UTC | 18h 11m |
| 2026-06-11 | SVA712 | MED → KHI | Jun 11, 05:55 UTC | Jun 12, 02:40 UTC | 20h 46m |
| 2026-06-11 | SVA712 | MED → KHI | Jun 11, 04:55 UTC | Jun 12, 02:40 UTC | 21h 46m |
| 2026-06-10 | SVA712 | MED → KHI | Jun 10, 05:50 UTC | Jun 11, 01:35 UTC | 19h 45m |
| 2026-06-10 | SVA712 | MED → KHI | Jun 10, 04:45 UTC | Jun 11, 01:35 UTC | 20h 50m |
| 2026-06-09 | SVA712 | MED → KHI | Jun 9, 22:45 UTC | Jun 10, 01:25 UTC | 2h 40m |
| 2026-06-08 | SVA597 | DXB → MED | Jun 8, 10:25 UTC | Jun 8, 10:40 UTC | 15m |
| 2026-06-06 | SVA713 | CCJ → RUH | Jun 6, 04:55 UTC | Jun 6, 08:35 UTC | 3h 40m |
| 2026-06-05 | SVA268 | IST → JED | Jun 5, 16:35 UTC | Jun 6, 01:40 UTC | 9h 5m |
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-ASAH page for operator, model, and routing details .