sensors Mode-S transponder
71147C
ICAO 24-bit transponder address · allocated to Saudi Arabia
Currently assigned to HZ-ASAN · AIRBUS A-321neo
- Hex
- 71147C
- Octal
- 34212174
- Decimal
- 7,410,812
- Country
- SA
- Tail
- HZ-ASAN
- Type
- A21N
- Flights observed
- 114
- Distinct callsigns
- 20
- Country
- SA
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 71147C 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 |
|---|---|---|---|
| SVA259 | - | 9 | 2026-07-03 |
| SVA258 | - | 8 | 2026-07-03 |
| SVA261 | Saudi Arabian Airlines | 7 | 2026-06-26 |
| SVA265 | Saudi Arabian Airlines | 6 | 2026-06-02 |
| SVA260 | Saudi Arabian Airlines | 6 | 2026-06-26 |
| SVA263 | - | 5 | 2026-07-05 |
| SVA411 | Saudi Arabian Airlines | 4 | 2026-06-25 |
| SVA264 | Saudi Arabian Airlines | 4 | 2026-07-05 |
| SVA713 | - | 3 | 2026-07-09 |
| SVA568 | - | 3 | 2026-06-23 |
| SVA268 | - | 3 | 2026-07-08 |
| SVA207 | - | 3 | 2026-07-12 |
| SVA391 | - | 2 | 2026-07-02 |
| SVA319 | Saudi Arabian Airlines | 2 | 2026-06-22 |
| SVA278 | Saudi Arabian Airlines | 2 | 2026-06-09 |
| SVA275 | Saudi Arabian Airlines | 2 | 2026-06-09 |
| SVA209 | - | 2 | 2026-07-11 |
| SVA208 | Saudi Arabian Airlines | 2 | 2026-07-13 |
| SVA151 | Saudi Arabian Airlines | 2 | 2026-04-14 |
| SVA150 | Saudi Arabian Airlines | 2 | 2026-04-14 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | SVA208 | FCO → RUH | Jul 13, 14:50 UTC | Jul 13, 18:10 UTC | 3h 20m |
| 2026-07-12 | SVA207 | - | Jul 12, 20:35 UTC | Jul 13, 12:10 UTC | 15h 35m |
| 2026-07-12 | SVA206 | - | Jul 12, 08:01 UTC | Jul 12, 18:45 UTC | 10h 45m |
| 2026-07-11 | SVA209 | - | Jul 11, 09:05 UTC | Jul 12, 04:35 UTC | 19h 30m |
| 2026-07-11 | SVA209 | - | Jul 11, 08:50 UTC | Jul 12, 04:35 UTC | 19h 45m |
| 2026-07-11 | SVA331 | - | Jul 11, 06:45 UTC | Jul 11, 07:25 UTC | 40m |
| 2026-07-09 | SVA1296 | - | Jul 9, 20:00 UTC | Jul 9, 20:10 UTC | 10m |
| 2026-07-09 | SVA713 | - | Jul 9, 07:30 UTC | Jul 9, 18:40 UTC | 11h 10m |
| 2026-07-09 | SVA713 | - | Jul 9, 04:45 UTC | Jul 9, 05:55 UTC | 1h 10m |
| 2026-07-08 | SVA268 | - | Jul 8, 16:55 UTC | Jul 9, 01:40 UTC | 8h 45m |
| 2026-07-08 | SVA267 | RUH → IST | Jul 8, 04:45 UTC | Jul 8, 14:50 UTC | 10h 5m |
| 2026-07-07 | SVA208 | FCO → RUH | Jul 7, 14:35 UTC | Jul 8, 01:40 UTC | 11h 5m |
| 2026-07-07 | SVA207 | - | Jul 7, 11:00 UTC | Jul 7, 13:00 UTC | 2h 0m |
| 2026-07-07 | SVA207 | - | Jul 7, 09:45 UTC | Jul 7, 10:40 UTC | 55m |
| 2026-07-06 | SVA1133 | - | Jul 6, 04:15 UTC | Jul 6, 04:30 UTC | 15m |
| 2026-07-05 | SVA264 | IST → RUH | Jul 5, 13:50 UTC | Jul 5, 15:40 UTC | 1h 50m |
| 2026-07-05 | SVA263 | - | Jul 5, 09:15 UTC | Jul 5, 11:30 UTC | 2h 15m |
| 2026-07-04 | SVA263 | - | Jul 4, 11:20 UTC | Jul 5, 11:00 UTC | 23h 40m |
| 2026-07-03 | SVA279 | - | Jul 3, 18:35 UTC | Jul 4, 09:45 UTC | 15h 10m |
| 2026-07-03 | SVA258 | - | Jul 3, 10:35 UTC | Jul 3, 16:50 UTC | 6h 15m |
| 2026-07-03 | SVA259 | - | Jul 3, 03:05 UTC | Jul 3, 08:55 UTC | 5h 50m |
| 2026-07-02 | SVA380 | - | Jul 2, 18:20 UTC | Jul 3, 01:05 UTC | 6h 45m |
| 2026-07-02 | SVA258 | - | Jul 2, 10:55 UTC | Jul 2, 16:30 UTC | 5h 35m |
| 2026-07-02 | SVA259 | - | Jul 2, 02:55 UTC | Jul 2, 09:10 UTC | 6h 15m |
| 2026-07-02 | SVA391 | - | Jul 2, 00:50 UTC | Jul 2, 01:20 UTC | 30m |
| 2026-07-01 | SVA258 | - | Jul 1, 10:45 UTC | Jul 1, 16:45 UTC | 6h 0m |
| 2026-07-01 | SVA259 | - | Jul 1, 03:00 UTC | Jul 1, 09:05 UTC | 6h 5m |
| 2026-06-30 | SVA391 | - | Jun 30, 14:20 UTC | Jul 1, 01:20 UTC | 11h 0m |
| 2026-06-30 | SVA315 | RUH → CAI | Jun 30, 08:30 UTC | Jun 30, 12:35 UTC | 4h 5m |
| 2026-06-29 | SVA317 | MED → CAI | Jun 29, 18:25 UTC | Jun 30, 06:45 UTC | 12h 21m |
| 2026-06-29 | SVA381 | MED → CAI | Jun 29, 06:50 UTC | Jun 29, 16:15 UTC | 9h 25m |
| 2026-06-28 | SVA595 | DXB → JED | Jun 28, 19:25 UTC | Jun 29, 04:34 UTC | 9h 10m |
| 2026-06-28 | SVA594 | JED → DXB | Jun 28, 16:05 UTC | Jun 28, 17:19 UTC | 1h 15m |
| 2026-06-27 | SVA1131 | - | Jun 27, 22:25 UTC | Jun 27, 22:35 UTC | 10m |
| 2026-06-26 | SVA260 | IST → JED | Jun 26, 19:35 UTC | Jun 26, 21:24 UTC | 1h 50m |
| 2026-06-26 | SVA261 | JED → IST | Jun 26, 15:39 UTC | Jun 26, 17:40 UTC | 2h 0m |
| 2026-06-25 | SVA261 | JED → IST | Jun 25, 17:39 UTC | Jun 26, 17:00 UTC | 23h 20m |
| 2026-06-25 | SVA411 | JED → HBE | Jun 25, 15:50 UTC | Jun 25, 16:35 UTC | 45m |
| 2026-06-24 | SVA569 | DXB → JED | Jun 24, 11:59 UTC | Jun 24, 12:54 UTC | 55m |
| 2026-06-23 | SVA568 | - | Jun 23, 17:39 UTC | Jun 24, 10:10 UTC | 16h 30m |
| 2026-06-23 | SVA411 | JED → HBE | Jun 23, 15:40 UTC | Jun 23, 16:20 UTC | 40m |
| 2026-06-22 | SVA319 | MED → CAI | Jun 22, 06:54 UTC | Jun 22, 12:40 UTC | 5h 45m |
| 2026-06-22 | SVA335 | JED → CAI | Jun 22, 04:09 UTC | Jun 22, 04:24 UTC | 15m |
| 2026-06-19 | SVA410 | HBE → JED | Jun 19, 17:34 UTC | Jun 19, 18:05 UTC | 30m |
| 2026-06-19 | SVA411 | JED → HBE | Jun 19, 15:34 UTC | Jun 19, 16:14 UTC | 40m |
| 2026-06-18 | SVA411 | JED → HBE | Jun 18, 20:00 UTC | Jun 19, 16:14 UTC | 20h 14m |
| 2026-06-18 | SVA333 | RUH → HBE | Jun 18, 05:45 UTC | Jun 18, 18:35 UTC | 12h 50m |
| 2026-06-17 | SVA712 | - | Jun 17, 22:50 UTC | Jun 18, 02:45 UTC | 3h 55m |
| 2026-06-17 | SVA1127 | - | Jun 17, 01:30 UTC | Jun 17, 01:40 UTC | 10m |
| 2026-06-16 | SVA550 | JED → DXB | Jun 16, 14:35 UTC | Jun 16, 18:20 UTC | 3h 45m |
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-ASAN page for operator, model, and routing details .