sensors Mode-S transponder
71018A
ICAO 24-bit transponder address · allocated to Saudi Arabia
Currently assigned to HZ-AQ23 · AIRBUS A-330-300
- Hex
- 71018A
- Octal
- 34200612
- Decimal
- 7,405,962
- Country
- SA
- Tail
- HZ-AQ23
- Type
- A333
- Flights observed
- 124
- Distinct callsigns
- 20
- Country
- SA
- Last broadcast
- 12h ago
Last known position
Country allocation
The ICAO 24-bit address 71018A 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 |
|---|---|---|---|
| SVA211 | - | 10 | 2026-06-27 |
| SVA588 | - | 7 | 2026-07-05 |
| SVA3779 | Saudi Arabian Airlines | 6 | 2026-04-27 |
| SVA311 | - | 6 | 2026-07-16 |
| SVA263 | - | 6 | 2026-07-11 |
| SVA210 | Saudi Arabian Airlines | 6 | 2026-06-27 |
| SVA708 | - | 5 | 2026-07-15 |
| SVA264 | Saudi Arabian Airlines | 5 | 2026-07-11 |
| SVA238 | - | 5 | 2026-07-17 |
| SVA237 | - | 5 | 2026-07-02 |
| SVA236 | Saudi Arabian Airlines | 4 | 2026-07-02 |
| SVA589 | Saudi Arabian Airlines | 3 | 2026-07-05 |
| SVA389 | Saudi Arabian Airlines | 3 | 2026-06-14 |
| SVA3776 | Saudi Arabian Airlines | 3 | 2026-04-26 |
| SVA321 | - | 3 | 2026-07-12 |
| SVA307 | - | 3 | 2026-07-04 |
| SVA305 | Saudi Arabian Airlines | 3 | 2026-06-17 |
| SVA596 | Saudi Arabian Airlines | 2 | 2026-05-09 |
| SVA435 | - | 2 | 2026-06-29 |
| SVA417 | Saudi Arabian Airlines | 2 | 2026-05-24 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-17 | SVA238 | - | Jul 17, 14:20 UTC | Jul 17, 18:05 UTC | 3h 45m |
| 2026-07-17 | SVA741 | BOM → RUH | Jul 17, 01:09 UTC | Jul 17, 04:04 UTC | 2h 55m |
| 2026-07-16 | SVA740 | - | Jul 16, 20:15 UTC | Jul 16, 23:44 UTC | 3h 30m |
| 2026-07-16 | SVA311 | - | Jul 16, 06:30 UTC | Jul 16, 07:00 UTC | 30m |
| 2026-07-15 | SVA311 | - | Jul 15, 10:35 UTC | Jul 16, 07:00 UTC | 20h 25m |
| 2026-07-15 | SVA709 | - | Jul 15, 09:40 UTC | Jul 16, 07:00 UTC | 21h 20m |
| 2026-07-15 | SVA708 | - | Jul 15, 04:10 UTC | Jul 15, 10:40 UTC | 6h 30m |
| 2026-07-13 | SVA312 | - | Jul 13, 18:05 UTC | Jul 13, 18:25 UTC | 20m |
| 2026-07-12 | SVA708 | - | Jul 12, 21:45 UTC | Jul 13, 16:00 UTC | 18h 15m |
| 2026-07-12 | SVA321 | - | Jul 12, 02:01 UTC | Jul 12, 19:50 UTC | 17h 50m |
| 2026-07-11 | SVA323 | - | Jul 11, 23:30 UTC | Jul 12, 00:05 UTC | 35m |
| 2026-07-11 | SVA264 | IST → RUH | Jul 11, 13:55 UTC | Jul 11, 15:45 UTC | 1h 50m |
| 2026-07-11 | SVA263 | - | Jul 11, 02:10 UTC | Jul 11, 11:05 UTC | 8h 55m |
| 2026-07-10 | SVA238 | - | Jul 10, 14:20 UTC | Jul 10, 23:50 UTC | 9h 31m |
| 2026-07-09 | SVA239 | - | Jul 9, 18:20 UTC | Jul 10, 12:25 UTC | 18h 5m |
| 2026-07-09 | SVA708 | - | Jul 9, 04:20 UTC | Jul 9, 16:15 UTC | 11h 55m |
| 2026-07-08 | SVA238 | - | Jul 8, 16:35 UTC | Jul 9, 16:15 UTC | 23h 40m |
| 2026-07-08 | SVA238 | - | Jul 8, 14:35 UTC | Jul 9, 10:55 UTC | 20h 20m |
| 2026-07-08 | SVA238 | - | Jul 8, 14:15 UTC | Jul 9, 10:55 UTC | 20h 40m |
| 2026-07-08 | SVA239 | - | Jul 8, 02:10 UTC | Jul 8, 12:40 UTC | 10h 30m |
| 2026-07-07 | SVA323 | - | Jul 7, 23:45 UTC | Jul 8, 00:00 UTC | 15m |
| 2026-07-06 | SVA775 | COK → RUH | Jul 6, 15:05 UTC | Jul 6, 19:00 UTC | 3h 55m |
| 2026-07-05 | SVA774 | - | Jul 5, 23:30 UTC | Jul 6, 13:10 UTC | 13h 40m |
| 2026-07-05 | SVA589 | DXB → JED | Jul 5, 13:50 UTC | Jul 5, 21:05 UTC | 7h 15m |
| 2026-07-05 | SVA588 | - | Jul 5, 10:40 UTC | Jul 5, 11:55 UTC | 1h 15m |
| 2026-07-04 | SVA307 | - | Jul 4, 10:40 UTC | Jul 4, 10:50 UTC | 10m |
| 2026-07-03 | SVA307 | - | Jul 3, 12:55 UTC | Jul 4, 10:50 UTC | 21h 55m |
| 2026-07-03 | SVA366 | TUN → JED | Jul 3, 11:10 UTC | Jul 3, 13:05 UTC | 1h 55m |
| 2026-07-02 | SVA236 | GVA → JED | Jul 2, 14:20 UTC | Jul 3, 08:20 UTC | 18h 0m |
| 2026-07-02 | SVA237 | - | Jul 2, 09:30 UTC | Jul 2, 12:10 UTC | 2h 40m |
| 2026-06-29 | SVA435 | - | Jun 29, 02:09 UTC | Jun 29, 02:20 UTC | 10m |
| 2026-06-27 | SVA210 | MXP → RUH | Jun 27, 14:35 UTC | Jun 27, 17:49 UTC | 3h 15m |
| 2026-06-27 | SVA211 | - | Jun 27, 08:44 UTC | Jun 27, 11:44 UTC | 3h 0m |
| 2026-06-26 | SVA211 | - | Jun 26, 14:35 UTC | Jun 27, 11:44 UTC | 21h 10m |
| 2026-06-26 | SVA211 | - | Jun 26, 13:59 UTC | Jun 27, 11:44 UTC | 21h 45m |
| 2026-06-26 | SVA588 | - | Jun 26, 10:44 UTC | Jun 26, 12:00 UTC | 1h 15m |
| 2026-06-25 | SVA588 | - | Jun 25, 14:39 UTC | Jun 26, 12:00 UTC | 21h 20m |
| 2026-06-25 | SVA264 | IST → RUH | Jun 25, 13:50 UTC | Jun 26, 12:00 UTC | 22h 10m |
| 2026-06-25 | SVA263 | - | Jun 25, 09:20 UTC | Jun 25, 11:19 UTC | 2h 0m |
| 2026-06-21 | SVA210 | MXP → RUH | Jun 21, 14:30 UTC | Jun 21, 17:15 UTC | 2h 45m |
| 2026-06-21 | SVA211 | - | Jun 21, 01:39 UTC | Jun 21, 11:30 UTC | 9h 50m |
| 2026-06-20 | SVA210 | MXP → RUH | Jun 20, 14:29 UTC | Jun 20, 23:45 UTC | 9h 15m |
| 2026-06-20 | SVA211 | - | Jun 20, 08:44 UTC | Jun 20, 11:40 UTC | 2h 55m |
| 2026-06-19 | SVA211 | - | Jun 19, 14:34 UTC | Jun 20, 11:40 UTC | 21h 5m |
| 2026-06-19 | SVA211 | - | Jun 19, 12:49 UTC | Jun 20, 11:40 UTC | 22h 50m |
| 2026-06-18 | SVA210 | MXP → RUH | Jun 18, 14:35 UTC | Jun 19, 10:24 UTC | 19h 49m |
| 2026-06-18 | SVA210 | MXP → RUH | Jun 18, 14:25 UTC | Jun 19, 10:24 UTC | 19h 59m |
| 2026-06-18 | SVA211 | - | Jun 18, 08:40 UTC | Jun 18, 11:45 UTC | 3h 5m |
| 2026-06-17 | SVA211 | - | Jun 17, 15:35 UTC | Jun 18, 11:45 UTC | 20h 10m |
| 2026-06-17 | SVA305 | JED → CAI | Jun 17, 13:05 UTC | Jun 17, 13:20 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-AQ23 page for operator, model, and routing details .