sensors Mode-S transponder
71040C
ICAO 24-bit transponder address · allocated to Saudi Arabia
Currently assigned to HZ-AS64 · AIRBUS A-320
- Hex
- 71040C
- Octal
- 34202014
- Decimal
- 7,406,604
- Country
- SA
- Tail
- HZ-AS64
- Type
- A320
- Flights observed
- 37
- Distinct callsigns
- 20
- Country
- SA
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 71040C 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 |
|---|---|---|---|
| SVA634 | - | 3 | 2026-07-08 |
| SVA633 | - | 2 | 2026-07-08 |
| SVA596 | - | 2 | 2026-07-03 |
| SVA572 | - | 2 | 2026-07-06 |
| SVA209 | Saudi Arabian Airlines | 2 | 2026-05-29 |
| SVA206 | Saudi Arabian Airlines | 2 | 2026-05-29 |
| SVA1133 | Saudi Arabian Airlines | 2 | 2026-05-20 |
| SVA638 | Saudi Arabian Airlines | 1 | 2026-06-05 |
| SVA637 | Saudi Arabian Airlines | 1 | 2026-06-05 |
| SVA636 | Saudi Arabian Airlines | 1 | 2026-06-11 |
| SVA635 | Saudi Arabian Airlines | 1 | 2026-06-11 |
| SVA632 | Saudi Arabian Airlines | 1 | 2026-06-11 |
| SVA631 | Saudi Arabian Airlines | 1 | 2026-06-11 |
| SVA597 | - | 1 | 2026-07-03 |
| SVA573 | - | 1 | 2026-07-06 |
| SVA561 | - | 1 | 2026-07-09 |
| SVA560 | - | 1 | 2026-07-08 |
| SVA332 | Saudi Arabian Airlines | 1 | 2026-04-16 |
| SVA261 | Saudi Arabian Airlines | 1 | 2026-04-23 |
| SVA260 | Saudi Arabian Airlines | 1 | 2026-04-23 |
Recent flights last 37
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-17 | SVA1127 | - | Jul 17, 01:35 UTC | Jul 17, 01:49 UTC | 15m |
| 2026-07-09 | SVA561 | - | Jul 9, 16:45 UTC | Jul 9, 17:40 UTC | 55m |
| 2026-07-08 | SVA560 | - | Jul 8, 19:25 UTC | Jul 9, 14:55 UTC | 19h 30m |
| 2026-07-08 | SVA634 | - | Jul 8, 12:40 UTC | Jul 8, 18:05 UTC | 5h 25m |
| 2026-07-08 | SVA633 | - | Jul 8, 10:50 UTC | Jul 8, 11:25 UTC | 35m |
| 2026-07-07 | SVA1294 | - | Jul 7, 08:00 UTC | Jul 7, 08:10 UTC | 10m |
| 2026-07-07 | SVA1295 | - | Jul 7, 06:30 UTC | Jul 7, 06:45 UTC | 15m |
| 2026-07-06 | SVA1161 | - | Jul 6, 22:25 UTC | Jul 6, 22:35 UTC | 10m |
| 2026-07-06 | SVA573 | - | Jul 6, 11:45 UTC | Jul 6, 12:15 UTC | 30m |
| 2026-07-06 | SVA572 | - | Jul 6, 09:05 UTC | Jul 6, 10:05 UTC | 1h 0m |
| 2026-07-03 | SVA597 | - | Jul 3, 09:45 UTC | Jul 3, 10:40 UTC | 55m |
| 2026-07-03 | SVA596 | - | Jul 3, 06:50 UTC | Jul 3, 08:05 UTC | 1h 15m |
| 2026-07-02 | SVA596 | - | Jul 2, 11:40 UTC | Jul 3, 08:05 UTC | 20h 25m |
| 2026-07-02 | SVA572 | - | Jul 2, 08:55 UTC | Jul 2, 10:00 UTC | 1h 5m |
| 2026-06-27 | SVA1109 | - | Jun 27, 09:34 UTC | Jun 27, 09:44 UTC | 10m |
| 2026-06-11 | SVA636 | AMM → JED | Jun 11, 17:50 UTC | Jun 11, 18:05 UTC | 15m |
| 2026-06-11 | SVA635 | JED → AMM | Jun 11, 16:05 UTC | Jun 11, 16:20 UTC | 15m |
| 2026-06-11 | SVA632 | AMM → JED | Jun 11, 10:45 UTC | Jun 11, 11:00 UTC | 15m |
| 2026-06-11 | SVA631 | JED → AMM | Jun 11, 08:50 UTC | Jun 11, 09:00 UTC | 10m |
| 2026-06-06 | SVA1125 | DMM → JED | Jun 6, 17:29 UTC | Jun 7, 13:40 UTC | 20h 10m |
| 2026-06-05 | SVA638 | AMM → RUH | Jun 5, 19:30 UTC | Jun 5, 19:40 UTC | 10m |
| 2026-06-05 | SVA637 | RUH → AMM | Jun 5, 17:50 UTC | Jun 5, 18:00 UTC | 10m |
| 2026-06-05 | SVA634 | AMM → RUH | Jun 5, 12:40 UTC | Jun 5, 12:50 UTC | 10m |
| 2026-05-30 | SVA1139 | DMM → RUH | May 30, 06:05 UTC | May 30, 06:20 UTC | 15m |
| 2026-05-29 | SVA206 | FCO → RUH | May 29, 08:00 UTC | May 29, 10:20 UTC | 2h 20m |
| 2026-05-29 | SVA209 | RUH → FCO | May 29, 01:40 UTC | May 29, 04:35 UTC | 2h 55m |
| 2026-05-25 | SVA634 | AMM → RUH | May 25, 12:55 UTC | May 25, 13:05 UTC | 10m |
| 2026-05-25 | SVA633 | RUH → AMM | May 25, 11:20 UTC | May 25, 11:35 UTC | 15m |
| 2026-05-20 | SVA1133 | DMM → RUH | May 20, 04:05 UTC | May 20, 04:20 UTC | 15m |
| 2026-05-17 | SVA1133 | DMM → RUH | May 17, 04:15 UTC | May 17, 04:30 UTC | 15m |
| 2026-05-08 | SVA206 | FCO → RUH | May 8, 08:09 UTC | May 8, 10:44 UTC | 2h 35m |
| 2026-05-08 | SVA209 | RUH → FCO | May 8, 01:45 UTC | May 8, 05:00 UTC | 3h 15m |
| 2026-04-23 | SVA260 | IST → JED | Apr 23, 19:55 UTC | Apr 23, 21:15 UTC | 1h 20m |
| 2026-04-23 | SVA261 | JED → IST | Apr 23, 15:55 UTC | Apr 23, 17:35 UTC | 1h 40m |
| 2026-04-16 | SVA332 | HBE → JED | Apr 16, 07:15 UTC | Apr 16, 09:05 UTC | 1h 50m |
| 2026-04-15 | SVA1105 | DMM → JED | Apr 15, 03:25 UTC | Apr 15, 03:35 UTC | 10m |
| 2026-04-14 | SVA1129 | - | Apr 14, 19:10 UTC | Apr 14, 19:25 UTC | 15m |
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-AS64 page for operator, model, and routing details .