sensors Mode-S transponder
71018B
ICAO 24-bit transponder address · allocated to Saudi Arabia
Currently assigned to HZ-AQ22 · AIRBUS A-330-300
- Hex
- 71018B
- Octal
- 34200613
- Decimal
- 7,405,963
- Country
- SA
- Tail
- HZ-AQ22
- Type
- A333
- Flights observed
- 107
- Distinct callsigns
- 20
- Country
- SA
- Last broadcast
- 16d ago
Last known position
Country allocation
The ICAO 24-bit address 71018B 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 |
|---|---|---|---|
| SVA596 | Saudi Arabian Airlines | 8 | 2026-05-30 |
| SVA389 | - | 8 | 2026-06-30 |
| SVA321 | Saudi Arabian Airlines | 8 | 2026-06-20 |
| SVA264 | Saudi Arabian Airlines | 6 | 2026-06-13 |
| SVA238 | Saudi Arabian Airlines | 6 | 2026-06-19 |
| SVA417 | - | 5 | 2026-06-17 |
| SVA313 | Saudi Arabian Airlines | 5 | 2026-06-21 |
| SVA307 | - | 5 | 2026-07-02 |
| SVA239 | - | 5 | 2026-06-18 |
| SVA708 | - | 4 | 2026-06-17 |
| SVA5708 | - | 3 | 2026-06-06 |
| SVA320 | - | 3 | 2026-06-20 |
| SVA257 | - | 3 | 2026-06-26 |
| SVA256 | Saudi Arabian Airlines | 3 | 2026-06-27 |
| SVA764 | Saudi Arabian Airlines | 2 | 2026-04-17 |
| SVA588 | - | 2 | 2026-06-30 |
| SVA388 | Saudi Arabian Airlines | 2 | 2026-06-24 |
| SVA323 | Saudi Arabian Airlines | 2 | 2026-06-12 |
| SVA322 | Saudi Arabian Airlines | 2 | 2026-06-20 |
| SVA309 | - | 2 | 2026-06-25 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-02 | SVA9051 | - | Jul 2, 12:20 UTC | Jul 2, 17:30 UTC | 5h 10m |
| 2026-07-02 | SVA307 | - | Jul 2, 09:50 UTC | Jul 2, 10:10 UTC | 20m |
| 2026-07-01 | SVA307 | - | Jul 1, 14:30 UTC | Jul 2, 10:10 UTC | 19h 40m |
| 2026-06-30 | SVA588 | - | Jun 30, 20:55 UTC | Jul 1, 11:50 UTC | 14h 55m |
| 2026-06-30 | SVA389 | - | Jun 30, 12:25 UTC | Jun 30, 18:55 UTC | 6h 30m |
| 2026-06-30 | SVA307 | - | Jun 30, 09:30 UTC | Jun 30, 09:45 UTC | 15m |
| 2026-06-30 | SVA383 | JED → CAI | Jun 30, 01:45 UTC | Jun 30, 02:00 UTC | 15m |
| 2026-06-29 | SVA389 | - | Jun 29, 18:30 UTC | Jun 29, 18:39 UTC | 10m |
| 2026-06-27 | SVA256 | IST → JED | Jun 27, 12:50 UTC | Jun 27, 14:35 UTC | 1h 45m |
| 2026-06-26 | SVA257 | - | Jun 26, 17:54 UTC | Jun 27, 10:25 UTC | 16h 30m |
| 2026-06-26 | SVA303 | JED → CAI | Jun 26, 10:05 UTC | Jun 26, 15:54 UTC | 5h 50m |
| 2026-06-26 | SVA301 | JED → CAI | Jun 26, 01:39 UTC | Jun 26, 07:50 UTC | 6h 10m |
| 2026-06-25 | SVA309 | - | Jun 25, 23:14 UTC | Jun 25, 23:44 UTC | 30m |
| 2026-06-25 | SVA305 | JED → CAI | Jun 25, 13:05 UTC | Jun 25, 13:24 UTC | 20m |
| 2026-06-24 | SVA388 | CAI → JED | Jun 24, 20:40 UTC | Jun 24, 20:49 UTC | 10m |
| 2026-06-24 | SVA389 | JED → CAI | Jun 24, 12:44 UTC | Jun 24, 18:50 UTC | 6h 5m |
| 2026-06-24 | SVA307 | - | Jun 24, 09:39 UTC | Jun 24, 09:49 UTC | 10m |
| 2026-06-23 | SVA256 | IST → JED | Jun 23, 12:45 UTC | Jun 24, 02:20 UTC | 13h 35m |
| 2026-06-23 | SVA257 | - | Jun 23, 08:20 UTC | Jun 23, 10:24 UTC | 2h 5m |
| 2026-06-21 | SVA312 | CAI → RUH | Jun 21, 18:10 UTC | Jun 21, 18:25 UTC | 15m |
| 2026-06-21 | SVA313 | RUH → CAI | Jun 21, 15:49 UTC | Jun 21, 16:10 UTC | 20m |
| 2026-06-20 | SVA320 | - | Jun 20, 21:49 UTC | Jun 21, 06:29 UTC | 8h 40m |
| 2026-06-20 | SVA321 | RUH → CAI | Jun 20, 13:44 UTC | Jun 20, 20:00 UTC | 6h 15m |
| 2026-06-20 | SVA322 | CAI → RUH | Jun 20, 02:04 UTC | Jun 20, 11:09 UTC | 9h 5m |
| 2026-06-19 | SVA238 | GVA → RUH | Jun 19, 16:49 UTC | Jun 19, 23:59 UTC | 7h 10m |
| 2026-06-19 | SVA238 | GVA → RUH | Jun 19, 14:15 UTC | Jun 19, 16:44 UTC | 2h 30m |
| 2026-06-18 | SVA239 | - | Jun 18, 18:15 UTC | Jun 19, 11:45 UTC | 17h 29m |
| 2026-06-17 | SVA708 | - | Jun 17, 22:05 UTC | Jun 18, 16:00 UTC | 17h 55m |
| 2026-06-17 | SVA321 | RUH → CAI | Jun 17, 19:25 UTC | Jun 17, 20:00 UTC | 35m |
| 2026-06-17 | SVA417 | - | Jun 17, 10:45 UTC | Jun 17, 10:55 UTC | 10m |
| 2026-06-15 | SVA306 | CAI → JED | Jun 15, 12:15 UTC | Jun 15, 12:25 UTC | 10m |
| 2026-06-15 | SVA307 | JED → CAI | Jun 15, 09:35 UTC | Jun 15, 09:45 UTC | 10m |
| 2026-06-14 | SVA309 | JED → CAI | Jun 14, 23:25 UTC | Jun 14, 23:39 UTC | 15m |
| 2026-06-14 | SVA305 | JED → CAI | Jun 14, 13:00 UTC | Jun 14, 13:20 UTC | 20m |
| 2026-06-13 | SVA264 | IST → RUH | Jun 13, 14:50 UTC | Jun 14, 13:20 UTC | 22h 30m |
| 2026-06-13 | SVA264 | IST → RUH | Jun 13, 13:45 UTC | Jun 13, 15:35 UTC | 1h 50m |
| 2026-06-13 | SVA263 | - | Jun 13, 02:05 UTC | Jun 13, 11:15 UTC | 9h 9m |
| 2026-06-12 | SVA323 | RUH → CAI | Jun 12, 13:15 UTC | Jun 13, 00:00 UTC | 10h 45m |
| 2026-06-12 | SVA417 | RUH → CAI | Jun 12, 10:45 UTC | Jun 12, 10:55 UTC | 10m |
| 2026-06-11 | SVA388 | CAI → JED | Jun 11, 20:45 UTC | Jun 11, 20:55 UTC | 10m |
| 2026-06-11 | SVA389 | JED → CAI | Jun 11, 18:20 UTC | Jun 11, 19:00 UTC | 40m |
| 2026-06-10 | SVA389 | JED → CAI | Jun 10, 22:10 UTC | Jun 11, 19:00 UTC | 20h 50m |
| 2026-06-10 | SVA321 | RUH → CAI | Jun 10, 19:25 UTC | Jun 10, 20:00 UTC | 35m |
| 2026-06-10 | SVA418 | CAI → RUH | Jun 10, 13:20 UTC | Jun 10, 13:30 UTC | 10m |
| 2026-06-08 | SVA238 | GVA → RUH | Jun 8, 14:15 UTC | Jun 8, 17:50 UTC | 3h 35m |
| 2026-06-08 | SVA239 | RUH → GVA | Jun 8, 09:25 UTC | Jun 8, 12:05 UTC | 2h 40m |
| 2026-06-06 | SVA5708 | - | Jun 6, 18:45 UTC | Jun 7, 05:55 UTC | 11h 10m |
| 2026-06-06 | SVA5708 | - | Jun 6, 04:35 UTC | Jun 6, 15:59 UTC | 11h 25m |
| 2026-06-05 | SVA5708 | - | Jun 5, 17:00 UTC | Jun 6, 15:59 UTC | 23h 0m |
| 2026-06-05 | SVA238 | GVA → RUH | Jun 5, 14:10 UTC | Jun 6, 05:05 UTC | 14h 55m |
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-AQ22 page for operator, model, and routing details .