sensors Mode-S transponder
71005D
ICAO 24-bit transponder address · allocated to Saudi Arabia
Currently assigned to HZ-AQK · AIRBUS A-330-300
- Hex
- 71005D
- Octal
- 34200135
- Decimal
- 7,405,661
- Country
- SA
- Tail
- HZ-AQK
- Type
- A333
- Flights observed
- 110
- Distinct callsigns
- 20
- Country
- SA
- Last broadcast
- 3h ago
Last known position
Country allocation
The ICAO 24-bit address 71005D 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 | - | 20 | 2026-07-13 |
| SVA796 | Saudi Arabian Airlines | 9 | 2026-05-24 |
| SVA867 | - | 8 | 2026-07-13 |
| SVA793 | - | 7 | 2026-06-30 |
| SVA792 | - | 7 | 2026-06-30 |
| SVA722 | - | 6 | 2026-07-01 |
| SVA752 | Saudi Arabian Airlines | 5 | 2026-07-08 |
| SVA775 | Saudi Arabian Airlines | 4 | 2026-06-23 |
| SVA774 | - | 4 | 2026-06-29 |
| SVA9637 | Saudi Arabian Airlines | 2 | 2026-05-19 |
| SVA893 | Saudi Arabian Airlines | 2 | 2026-07-15 |
| SVA892 | Saudi Arabian Airlines | 2 | 2026-05-09 |
| SVA797 | Saudi Arabian Airlines | 2 | 2026-05-27 |
| SVA764 | Saudi Arabian Airlines | 2 | 2026-06-17 |
| SVA588 | - | 2 | 2026-07-06 |
| SVA383 | Saudi Arabian Airlines | 2 | 2026-06-04 |
| SVA302 | - | 2 | 2026-06-21 |
| SVA9656 | - | 1 | 2026-06-13 |
| SVA890 | - | 1 | 2026-07-17 |
| SVA815 | - | 1 | 2026-07-17 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-17 | SVA815 | - | Jul 17, 22:05 UTC | Jul 17, 23:20 UTC | 1h 15m |
| 2026-07-17 | SVA814 | - | Jul 17, 07:14 UTC | Jul 17, 19:55 UTC | 12h 40m |
| 2026-07-17 | SVA890 | - | Jul 17, 00:45 UTC | Jul 17, 04:35 UTC | 3h 50m |
| 2026-07-15 | SVA893 | LKO → JED | Jul 15, 22:20 UTC | Jul 16, 00:35 UTC | 2h 15m |
| 2026-07-15 | SVA754 | - | Jul 15, 00:30 UTC | Jul 15, 18:50 UTC | 18h 20m |
| 2026-07-13 | SVA867 | - | Jul 13, 06:25 UTC | Jul 13, 09:20 UTC | 2h 55m |
| 2026-07-13 | SVA866 | - | Jul 13, 03:10 UTC | Jul 13, 04:40 UTC | 1h 30m |
| 2026-07-12 | SVA867 | - | Jul 12, 06:05 UTC | Jul 13, 01:05 UTC | 19h 0m |
| 2026-07-12 | SVA866 | - | Jul 12, 00:15 UTC | Jul 12, 04:20 UTC | 4h 5m |
| 2026-07-08 | SVA752 | JED → HYD | Jul 8, 16:00 UTC | Jul 9, 00:25 UTC | 8h 25m |
| 2026-07-06 | SVA589 | DXB → JED | Jul 6, 13:55 UTC | Jul 6, 14:45 UTC | 50m |
| 2026-07-06 | SVA588 | - | Jul 6, 03:30 UTC | Jul 6, 12:05 UTC | 8h 35m |
| 2026-07-05 | SVA772 | - | Jul 5, 06:05 UTC | Jul 6, 00:50 UTC | 18h 45m |
| 2026-07-05 | SVA866 | - | Jul 5, 00:30 UTC | Jul 5, 04:20 UTC | 3h 50m |
| 2026-07-04 | SVA866 | - | Jul 4, 08:55 UTC | Jul 5, 04:20 UTC | 19h 25m |
| 2026-07-04 | SVA866 | - | Jul 4, 06:00 UTC | Jul 5, 04:20 UTC | 22h 20m |
| 2026-07-04 | SVA866 | - | Jul 4, 00:15 UTC | Jul 4, 04:05 UTC | 3h 50m |
| 2026-07-03 | SVA866 | - | Jul 3, 05:45 UTC | Jul 4, 04:05 UTC | 22h 20m |
| 2026-07-03 | SVA701 | KHI → JED | Jul 3, 01:20 UTC | Jul 4, 00:35 UTC | 23h 15m |
| 2026-07-03 | SVA700 | - | Jul 3, 00:20 UTC | Jul 3, 06:10 UTC | 5h 50m |
| 2026-07-01 | SVA722 | - | Jul 1, 00:45 UTC | Jul 1, 08:45 UTC | 8h 0m |
| 2026-06-30 | SVA722 | - | Jun 30, 09:45 UTC | Jul 1, 08:45 UTC | 23h 0m |
| 2026-06-30 | SVA722 | - | Jun 30, 08:00 UTC | Jul 1, 06:35 UTC | 22h 35m |
| 2026-06-30 | SVA793 | - | Jun 30, 03:20 UTC | Jul 1, 01:55 UTC | 22h 35m |
| 2026-06-30 | SVA792 | - | Jun 30, 02:10 UTC | Jul 1, 01:15 UTC | 23h 5m |
| 2026-06-29 | SVA792 | - | Jun 29, 15:19 UTC | Jun 30, 10:45 UTC | 19h 26m |
| 2026-06-29 | SVA792 | - | Jun 29, 15:04 UTC | Jun 30, 10:45 UTC | 19h 41m |
| 2026-06-29 | SVA774 | - | Jun 29, 09:20 UTC | Jun 29, 13:30 UTC | 4h 10m |
| 2026-06-23 | SVA775 | COK → RUH | Jun 23, 15:04 UTC | Jun 23, 18:50 UTC | 3h 45m |
| 2026-06-22 | SVA752 | JED → HYD | Jun 22, 15:40 UTC | Jun 23, 09:59 UTC | 18h 20m |
| 2026-06-22 | SVA752 | JED → HYD | Jun 22, 06:54 UTC | Jun 23, 01:00 UTC | 18h 5m |
| 2026-06-22 | SVA752 | JED → HYD | Jun 22, 04:24 UTC | Jun 23, 01:00 UTC | 20h 35m |
| 2026-06-22 | SVA752 | JED → HYD | Jun 22, 01:40 UTC | Jun 23, 01:00 UTC | 23h 20m |
| 2026-06-21 | SVA302 | - | Jun 21, 18:00 UTC | Jun 21, 18:10 UTC | 10m |
| 2026-06-21 | SVA867 | - | Jun 21, 06:04 UTC | Jun 21, 15:59 UTC | 9h 55m |
| 2026-06-21 | SVA866 | - | Jun 21, 00:19 UTC | Jun 21, 04:30 UTC | 4h 10m |
| 2026-06-17 | SVA763 | DEL → DMM | Jun 17, 21:30 UTC | Jun 17, 22:55 UTC | 1h 25m |
| 2026-06-17 | SVA764 | JED → COK | Jun 17, 15:30 UTC | Jun 17, 19:35 UTC | 4h 5m |
| 2026-06-16 | SVA764 | JED → COK | Jun 16, 20:40 UTC | Jun 17, 19:15 UTC | 22h 35m |
| 2026-06-16 | SVA792 | RUH → PEW | Jun 16, 02:45 UTC | Jun 16, 18:55 UTC | 16h 10m |
| 2026-06-13 | SVA9656 | - | Jun 13, 01:55 UTC | Jun 13, 03:20 UTC | 1h 25m |
| 2026-06-12 | SVA5547 | - | Jun 12, 21:10 UTC | Jun 13, 00:15 UTC | 3h 5m |
| 2026-06-10 | SVA5796 | - | Jun 10, 01:40 UTC | Jun 10, 07:15 UTC | 5h 35m |
| 2026-06-08 | SVA264 | IST → RUH | Jun 8, 13:45 UTC | Jun 8, 15:40 UTC | 1h 55m |
| 2026-06-08 | SVA263 | RUH → IST | Jun 8, 09:50 UTC | Jun 8, 11:45 UTC | 1h 55m |
| 2026-06-07 | SVA867 | BLR → JED | Jun 7, 06:05 UTC | Jun 7, 07:30 UTC | 1h 25m |
| 2026-06-07 | SVA866 | JED → BLR | Jun 7, 03:00 UTC | Jun 7, 04:25 UTC | 1h 25m |
| 2026-06-06 | SVA866 | JED → BLR | Jun 6, 08:05 UTC | Jun 7, 04:25 UTC | 20h 20m |
| 2026-06-06 | SVA866 | JED → BLR | Jun 6, 05:30 UTC | Jun 7, 04:25 UTC | 22h 55m |
| 2026-06-06 | SVA724 | RUH → ISB | Jun 6, 00:00 UTC | Jun 6, 08:25 UTC | 8h 25m |
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-AQK page for operator, model, and routing details .