sensors Mode-S transponder
71005B
ICAO 24-bit transponder address · allocated to Saudi Arabia
Currently assigned to HZ-AQI · AIRBUS A-330-300
- Hex
- 71005B
- Octal
- 34200133
- Decimal
- 7,405,659
- Country
- SA
- Tail
- HZ-AQI
- Type
- A333
- Flights observed
- 97
- Distinct callsigns
- 20
- Country
- SA
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 71005B 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 |
|---|---|---|---|
| SVA866 | - | 9 | 2026-06-27 |
| SVA893 | Saudi Arabian Airlines | 7 | 2026-06-27 |
| SVA892 | Saudi Arabian Airlines | 6 | 2026-06-27 |
| SVA796 | - | 6 | 2026-06-19 |
| SVA815 | - | 5 | 2026-07-15 |
| SVA793 | - | 5 | 2026-06-25 |
| SVA867 | Saudi Arabian Airlines | 4 | 2026-06-03 |
| SVA814 | - | 4 | 2026-07-15 |
| SVA792 | - | 4 | 2026-06-25 |
| SVA784 | - | 4 | 2026-07-07 |
| SVA775 | Saudi Arabian Airlines | 3 | 2026-07-13 |
| SVA774 | - | 3 | 2026-07-13 |
| SVA770 | - | 3 | 2026-07-05 |
| SVA754 | - | 3 | 2026-06-29 |
| SVA783 | Saudi Arabian Airlines | 2 | 2026-06-14 |
| SVA772 | - | 2 | 2026-07-11 |
| SVA5723 | - | 2 | 2026-05-13 |
| SVA389 | Saudi Arabian Airlines | 2 | 2026-06-01 |
| SVA3752 | Saudi Arabian Airlines | 2 | 2026-05-21 |
| SVA3574 | Saudi Arabian Airlines | 2 | 2026-05-31 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-16 | SVA551 | - | Jul 16, 17:10 UTC | Jul 16, 18:00 UTC | 50m |
| 2026-07-15 | SVA815 | - | Jul 15, 22:10 UTC | Jul 16, 15:25 UTC | 17h 15m |
| 2026-07-15 | SVA814 | - | Jul 15, 16:20 UTC | Jul 15, 20:20 UTC | 4h 0m |
| 2026-07-13 | SVA775 | COK → RUH | Jul 13, 15:15 UTC | Jul 13, 18:40 UTC | 3h 25m |
| 2026-07-13 | SVA774 | - | Jul 13, 01:55 UTC | Jul 13, 13:10 UTC | 11h 15m |
| 2026-07-12 | SVA323 | - | Jul 12, 23:25 UTC | Jul 12, 23:55 UTC | 30m |
| 2026-07-11 | SVA773 | - | Jul 11, 21:05 UTC | Jul 11, 23:15 UTC | 2h 10m |
| 2026-07-11 | SVA772 | - | Jul 11, 16:00 UTC | Jul 11, 19:10 UTC | 3h 10m |
| 2026-07-10 | SVA772 | - | Jul 10, 18:15 UTC | Jul 11, 16:45 UTC | 22h 30m |
| 2026-07-10 | SVA775 | COK → RUH | Jul 10, 15:00 UTC | Jul 10, 18:40 UTC | 3h 40m |
| 2026-07-10 | SVA774 | - | Jul 10, 08:55 UTC | Jul 10, 13:00 UTC | 4h 5m |
| 2026-07-08 | SVA815 | - | Jul 8, 22:15 UTC | Jul 9, 13:20 UTC | 15h 5m |
| 2026-07-08 | SVA814 | - | Jul 8, 06:05 UTC | Jul 8, 20:30 UTC | 14h 25m |
| 2026-07-07 | SVA784 | - | Jul 7, 15:45 UTC | Jul 8, 04:30 UTC | 12h 45m |
| 2026-07-06 | SVA815 | - | Jul 6, 22:05 UTC | Jul 7, 13:30 UTC | 15h 25m |
| 2026-07-06 | SVA814 | - | Jul 6, 06:55 UTC | Jul 6, 20:00 UTC | 13h 5m |
| 2026-07-05 | SVA770 | - | Jul 5, 08:50 UTC | Jul 6, 04:15 UTC | 19h 25m |
| 2026-07-05 | SVA770 | - | Jul 5, 06:50 UTC | Jul 6, 04:15 UTC | 21h 25m |
| 2026-07-05 | SVA770 | - | Jul 5, 00:35 UTC | Jul 5, 04:20 UTC | 3h 45m |
| 2026-07-04 | SVA815 | - | Jul 4, 01:05 UTC | Jul 5, 00:45 UTC | 23h 40m |
| 2026-07-03 | SVA815 | - | Jul 3, 22:05 UTC | Jul 4, 01:30 UTC | 3h 25m |
| 2026-07-03 | SVA814 | - | Jul 3, 16:00 UTC | Jul 3, 20:05 UTC | 4h 5m |
| 2026-07-01 | SVA304 | CAI → JED | Jul 1, 15:35 UTC | Jul 1, 15:45 UTC | 10m |
| 2026-07-01 | SVA305 | JED → CAI | Jul 1, 13:00 UTC | Jul 1, 13:20 UTC | 20m |
| 2026-06-29 | SVA754 | - | Jun 29, 00:14 UTC | Jun 29, 09:14 UTC | 9h 0m |
| 2026-06-28 | SVA754 | - | Jun 28, 01:04 UTC | Jun 29, 00:44 UTC | 23h 40m |
| 2026-06-27 | SVA893 | LKO → JED | Jun 27, 22:25 UTC | Jun 28, 01:04 UTC | 2h 40m |
| 2026-06-27 | SVA893 | LKO → JED | Jun 27, 21:15 UTC | Jun 27, 21:25 UTC | 10m |
| 2026-06-27 | SVA892 | JED → LKO | Jun 27, 06:15 UTC | Jun 27, 19:05 UTC | 12h 50m |
| 2026-06-27 | SVA866 | - | Jun 27, 00:20 UTC | Jun 27, 04:19 UTC | 4h 0m |
| 2026-06-25 | SVA386 | - | Jun 25, 23:09 UTC | Jun 25, 23:34 UTC | 25m |
| 2026-06-25 | SVA793 | - | Jun 25, 02:49 UTC | Jun 25, 21:25 UTC | 18h 35m |
| 2026-06-25 | SVA792 | - | Jun 25, 02:10 UTC | Jun 25, 21:25 UTC | 19h 15m |
| 2026-06-19 | SVA796 | - | Jun 19, 01:19 UTC | Jun 19, 07:34 UTC | 6h 15m |
| 2026-06-14 | SVA754 | JED → HYD | Jun 14, 18:30 UTC | Jun 15, 07:29 UTC | 12h 59m |
| 2026-06-14 | SVA783 | COK → JED | Jun 14, 06:00 UTC | Jun 14, 16:05 UTC | 10h 5m |
| 2026-06-14 | SVA784 | JED → COK | Jun 14, 00:05 UTC | Jun 14, 04:10 UTC | 4h 5m |
| 2026-06-12 | SVA775 | COK → RUH | Jun 12, 15:00 UTC | Jun 12, 18:55 UTC | 3h 55m |
| 2026-06-12 | SVA774 | RUH → COK | Jun 12, 11:25 UTC | Jun 12, 13:00 UTC | 1h 35m |
| 2026-06-11 | SVA793 | EAM → RUH | Jun 11, 02:40 UTC | Jun 11, 10:50 UTC | 8h 10m |
| 2026-06-09 | SVA709 | KHI → MED | Jun 9, 10:45 UTC | Jun 9, 10:55 UTC | 10m |
| 2026-06-07 | SVA755 | HYD → JED | Jun 7, 02:55 UTC | Jun 7, 07:40 UTC | 4h 45m |
| 2026-06-06 | SWA382 | PHX → RNO | Jun 6, 02:34 UTC | Jun 6, 04:53 UTC | 2h 19m |
| 2026-06-06 | SVA383 | JED → CAI | Jun 6, 01:50 UTC | Jun 6, 02:05 UTC | 15m |
| 2026-06-03 | SVA867 | BLR → JED | Jun 3, 07:15 UTC | Jun 3, 08:30 UTC | 1h 15m |
| 2026-06-03 | SVA866 | JED → BLR | Jun 3, 04:10 UTC | Jun 3, 05:35 UTC | 1h 25m |
| 2026-06-01 | SVA388 | CAI → JED | Jun 1, 21:15 UTC | Jun 1, 21:30 UTC | 15m |
| 2026-06-01 | SVA389 | JED → CAI | Jun 1, 03:00 UTC | Jun 1, 19:05 UTC | 16h 5m |
| 2026-05-31 | SVA3574 | JED → AUH | May 31, 15:05 UTC | Jun 1, 07:05 UTC | 16h 0m |
| 2026-05-31 | SVA3574 | JED → AUH | May 31, 00:40 UTC | May 31, 18:25 UTC | 17h 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-AQI page for operator, model, and routing details .