sensors Mode-S transponder
71011F
ICAO 24-bit transponder address · allocated to Saudi Arabia
Currently assigned to HZ-AS57 · AIRBUS A-320
- Hex
- 71011F
- Octal
- 34200437
- Decimal
- 7,405,855
- Country
- SA
- Tail
- HZ-AS57
- Type
- A320
- Flights observed
- 33
- Distinct callsigns
- 20
- Country
- SA
- Last broadcast
- 7d ago
Last known position
Country allocation
The ICAO 24-bit address 71011F 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 |
|---|---|---|---|
| SVA260 | Saudi Arabian Airlines | 4 | 2026-04-25 |
| SVA569 | - | 3 | 2026-07-08 |
| SVA568 | - | 3 | 2026-07-08 |
| SVA521 | - | 2 | 2026-07-04 |
| SVA520 | - | 2 | 2026-07-04 |
| SVA1125 | Saudi Arabian Airlines | 2 | 2026-05-27 |
| SVA1105 | Saudi Arabian Airlines | 2 | 2026-06-02 |
| SVA638 | Saudi Arabian Airlines | 1 | 2026-06-23 |
| SVA637 | Saudi Arabian Airlines | 1 | 2026-06-23 |
| SVA634 | Saudi Arabian Airlines | 1 | 2026-06-23 |
| SVA633 | Saudi Arabian Airlines | 1 | 2026-06-23 |
| SVA590 | - | 1 | 2026-07-07 |
| SVA572 | Saudi Arabian Airlines | 1 | 2026-05-08 |
| SVA560 | - | 1 | 2026-06-25 |
| SVA546 | Saudi Arabian Airlines | 1 | 2026-05-14 |
| SVA278 | - | 1 | 2026-04-21 |
| SVA275 | Saudi Arabian Airlines | 1 | 2026-04-21 |
| SVA261 | Saudi Arabian Airlines | 1 | 2026-04-25 |
| SVA209 | - | 1 | 2026-06-25 |
| SVA206 | - | 1 | 2026-06-26 |
Recent flights last 33
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-11 | - | - | Jul 11, 04:10 UTC | Jul 11, 04:25 UTC | 15m |
| 2026-07-08 | SVA569 | - | Jul 8, 11:50 UTC | Jul 8, 17:45 UTC | 5h 55m |
| 2026-07-08 | SVA568 | - | Jul 8, 03:10 UTC | Jul 8, 10:10 UTC | 7h 0m |
| 2026-07-07 | SVA590 | - | Jul 7, 23:05 UTC | Jul 8, 00:30 UTC | 1h 25m |
| 2026-07-04 | SVA521 | - | Jul 4, 15:00 UTC | Jul 4, 15:15 UTC | 15m |
| 2026-07-04 | SVA520 | - | Jul 4, 13:10 UTC | Jul 4, 13:25 UTC | 15m |
| 2026-06-26 | SVA568 | - | Jun 26, 09:50 UTC | Jun 27, 09:44 UTC | 23h 55m |
| 2026-06-26 | SVA206 | - | Jun 26, 07:10 UTC | Jun 26, 09:59 UTC | 2h 50m |
| 2026-06-25 | SVA209 | - | Jun 25, 16:45 UTC | Jun 26, 04:45 UTC | 12h 0m |
| 2026-06-25 | SVA560 | - | Jun 25, 13:59 UTC | Jun 25, 15:10 UTC | 1h 10m |
| 2026-06-24 | SVA521 | - | Jun 24, 15:00 UTC | Jun 24, 15:14 UTC | 15m |
| 2026-06-24 | SVA520 | - | Jun 24, 13:10 UTC | Jun 24, 13:24 UTC | 15m |
| 2026-06-23 | SVA638 | AMM → RUH | Jun 23, 19:29 UTC | Jun 23, 19:39 UTC | 10m |
| 2026-06-23 | SVA637 | RUH → AMM | Jun 23, 17:34 UTC | Jun 23, 17:54 UTC | 20m |
| 2026-06-23 | SVA634 | AMM → RUH | Jun 23, 12:49 UTC | Jun 23, 13:00 UTC | 10m |
| 2026-06-23 | SVA633 | RUH → AMM | Jun 23, 11:04 UTC | Jun 23, 11:24 UTC | 20m |
| 2026-06-18 | SVA1131 | - | Jun 18, 22:15 UTC | Jun 18, 22:35 UTC | 20m |
| 2026-06-02 | SVA1105 | DMM → JED | Jun 2, 03:25 UTC | Jun 2, 03:35 UTC | 10m |
| 2026-05-27 | SVA1125 | DMM → JED | May 27, 17:20 UTC | May 28, 13:40 UTC | 20h 20m |
| 2026-05-14 | SVA546 | JED → DOH | May 14, 11:15 UTC | May 14, 11:50 UTC | 35m |
| 2026-05-08 | SVA572 | JED → AUH | May 8, 10:04 UTC | May 8, 10:19 UTC | 15m |
| 2026-04-27 | SVA569 | DXB → JED | Apr 27, 11:45 UTC | Apr 27, 19:35 UTC | 7h 50m |
| 2026-04-27 | SVA568 | JED → DXB | Apr 27, 07:55 UTC | Apr 27, 09:00 UTC | 1h 5m |
| 2026-04-26 | SVA569 | DXB → JED | Apr 26, 11:55 UTC | Apr 27, 09:00 UTC | 21h 5m |
| 2026-04-25 | SVA260 | IST → JED | Apr 25, 19:35 UTC | Apr 26, 09:10 UTC | 13h 35m |
| 2026-04-25 | SVA261 | JED → IST | Apr 25, 07:40 UTC | Apr 25, 17:35 UTC | 9h 55m |
| 2026-04-24 | SVA260 | IST → JED | Apr 24, 20:10 UTC | Apr 25, 17:35 UTC | 21h 25m |
| 2026-04-24 | SVA260 | IST → JED | Apr 24, 16:00 UTC | Apr 25, 07:40 UTC | 15h 40m |
| 2026-04-24 | SVA260 | IST → JED | Apr 24, 03:15 UTC | Apr 24, 21:40 UTC | 18h 25m |
| 2026-04-23 | SVA1125 | DMM → JED | Apr 23, 17:25 UTC | Apr 24, 01:25 UTC | 7h 59m |
| 2026-04-21 | SVA278 | - | Apr 21, 15:45 UTC | Apr 21, 17:15 UTC | 1h 30m |
| 2026-04-21 | SVA275 | JED → IST | Apr 21, 12:05 UTC | Apr 21, 13:50 UTC | 1h 45m |
| 2026-04-17 | SVA1105 | DMM → JED | Apr 17, 03:30 UTC | Apr 17, 03:40 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-AS57 page for operator, model, and routing details .