sensors Mode-S transponder
71004A
ICAO 24-bit transponder address · allocated to Saudi Arabia
Currently assigned to HZ-AQA · AIRBUS A-330-300
- Hex
- 71004A
- Octal
- 34200112
- Decimal
- 7,405,642
- Country
- SA
- Tail
- HZ-AQA
- Type
- A333
- Flights observed
- 101
- Distinct callsigns
- 20
- Country
- SA
- Last broadcast
- 11h ago
Last known position
Country allocation
The ICAO 24-bit address 71004A 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 |
|---|---|---|---|
| SVA366 | Saudi Arabian Airlines | 9 | 2026-07-24 |
| SVA365 | Saudi Arabian Airlines | 9 | 2026-07-24 |
| SVA763 | - | 8 | 2026-07-10 |
| SVA764 | Saudi Arabian Airlines | 7 | 2026-07-10 |
| SVA752 | Saudi Arabian Airlines | 7 | 2026-07-13 |
| SVA866 | - | 6 | 2026-06-30 |
| SVA784 | Saudi Arabian Airlines | 4 | 2026-06-17 |
| SVA775 | Saudi Arabian Airlines | 4 | 2026-06-27 |
| SVA890 | Saudi Arabian Airlines | 3 | 2026-06-14 |
| SVA774 | - | 3 | 2026-06-27 |
| SVA754 | - | 3 | 2026-07-04 |
| SVA722 | Saudi Arabian Airlines | 3 | 2026-05-14 |
| SVA5722 | - | 3 | 2026-06-23 |
| SVA307 | Saudi Arabian Airlines | 3 | 2026-07-23 |
| SVA892 | Saudi Arabian Airlines | 2 | 2026-06-08 |
| SVA867 | - | 2 | 2026-07-01 |
| SVA771 | Saudi Arabian Airlines | 2 | 2026-07-19 |
| SVA770 | Saudi Arabian Airlines | 2 | 2026-07-19 |
| SVA588 | Saudi Arabian Airlines | 2 | 2026-06-06 |
| SVA5723 | - | 2 | 2026-04-28 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-24 | SVA366 | TUN → JED | Jul 24, 11:10 UTC | Jul 24, 12:30 UTC | 1h 20m |
| 2026-07-24 | SVA365 | JED → TUN | Jul 24, 06:20 UTC | Jul 24, 08:40 UTC | 2h 20m |
| 2026-07-23 | SVA307 | JED → CAI | Jul 23, 09:45 UTC | Jul 23, 10:10 UTC | 25m |
| 2026-07-20 | SVA1678 | - | Jul 20, 20:00 UTC | Jul 20, 20:25 UTC | 25m |
| 2026-07-19 | SVA771 | MAA → JED | Jul 19, 05:35 UTC | Jul 19, 06:10 UTC | 35m |
| 2026-07-19 | SVA770 | JED → BOM | Jul 19, 00:35 UTC | Jul 19, 03:45 UTC | 3h 10m |
| 2026-07-18 | SVA307 | - | Jul 18, 09:50 UTC | Jul 18, 10:00 UTC | 10m |
| 2026-07-18 | SVA309 | - | Jul 18, 00:10 UTC | Jul 18, 00:25 UTC | 15m |
| 2026-07-13 | SVA752 | JED → HYD | Jul 13, 16:05 UTC | Jul 13, 23:15 UTC | 7h 10m |
| 2026-07-12 | SVA307 | - | Jul 12, 09:45 UTC | Jul 12, 10:01 UTC | 15m |
| 2026-07-10 | SVA763 | - | Jul 10, 21:30 UTC | Jul 10, 22:50 UTC | 1h 20m |
| 2026-07-10 | SVA764 | JED → COK | Jul 10, 15:35 UTC | Jul 10, 19:35 UTC | 4h 0m |
| 2026-07-10 | SVA771 | - | Jul 10, 05:50 UTC | Jul 10, 08:00 UTC | 2h 10m |
| 2026-07-09 | SVA770 | - | Jul 9, 10:55 UTC | Jul 10, 03:50 UTC | 16h 55m |
| 2026-07-08 | SVA365 | - | Jul 8, 12:50 UTC | Jul 9, 08:05 UTC | 19h 15m |
| 2026-07-08 | SVA366 | TUN → JED | Jul 8, 10:55 UTC | Jul 9, 08:05 UTC | 21h 10m |
| 2026-07-07 | SVA388 | - | Jul 7, 20:50 UTC | Jul 7, 21:00 UTC | 10m |
| 2026-07-07 | SVA366 | TUN → JED | Jul 7, 11:00 UTC | Jul 7, 18:50 UTC | 7h 50m |
| 2026-07-07 | SVA365 | - | Jul 7, 06:40 UTC | Jul 7, 08:20 UTC | 1h 40m |
| 2026-07-06 | SVA773 | - | Jul 6, 21:15 UTC | Jul 7, 06:35 UTC | 9h 20m |
| 2026-07-06 | SVA772 | - | Jul 6, 16:15 UTC | Jul 6, 19:30 UTC | 3h 15m |
| 2026-07-04 | SVA754 | - | Jul 4, 18:45 UTC | Jul 5, 09:10 UTC | 14h 25m |
| 2026-07-04 | SVA303 | JED → CAI | Jul 4, 10:00 UTC | Jul 4, 16:50 UTC | 6h 50m |
| 2026-07-03 | SVA763 | - | Jul 3, 21:25 UTC | Jul 4, 07:45 UTC | 10h 20m |
| 2026-07-03 | SVA764 | JED → COK | Jul 3, 15:25 UTC | Jul 3, 19:25 UTC | 4h 0m |
| 2026-07-01 | SVA386 | - | Jul 1, 23:15 UTC | Jul 1, 23:30 UTC | 15m |
| 2026-07-01 | SVA867 | - | Jul 1, 06:20 UTC | Jul 1, 20:55 UTC | 14h 35m |
| 2026-06-30 | SVA866 | - | Jun 30, 11:05 UTC | Jul 1, 04:45 UTC | 17h 40m |
| 2026-06-29 | SVA752 | JED → HYD | Jun 29, 15:39 UTC | Jun 30, 08:00 UTC | 16h 21m |
| 2026-06-27 | SVA775 | COK → RUH | Jun 27, 15:14 UTC | Jun 27, 18:45 UTC | 3h 30m |
| 2026-06-27 | SVA774 | - | Jun 27, 09:00 UTC | Jun 27, 13:09 UTC | 4h 10m |
| 2026-06-25 | SVA366 | TUN → JED | Jun 25, 10:55 UTC | Jun 25, 13:05 UTC | 2h 10m |
| 2026-06-25 | SVA365 | - | Jun 25, 06:25 UTC | Jun 25, 07:59 UTC | 1h 35m |
| 2026-06-23 | SVA5722 | - | Jun 23, 00:09 UTC | Jun 23, 08:20 UTC | 8h 10m |
| 2026-06-19 | SVA366 | TUN → JED | Jun 19, 11:04 UTC | Jun 19, 13:09 UTC | 2h 5m |
| 2026-06-19 | SVA365 | - | Jun 19, 06:14 UTC | Jun 19, 08:14 UTC | 2h 0m |
| 2026-06-17 | SVA752 | JED → HYD | Jun 17, 06:05 UTC | Jun 17, 23:00 UTC | 16h 55m |
| 2026-06-17 | SVA784 | JED → COK | Jun 17, 00:10 UTC | Jun 17, 04:15 UTC | 4h 5m |
| 2026-06-16 | SVA784 | JED → COK | Jun 16, 06:10 UTC | Jun 17, 04:15 UTC | 22h 6m |
| 2026-06-16 | SVA784 | JED → COK | Jun 16, 00:35 UTC | Jun 17, 00:30 UTC | 23h 56m |
| 2026-06-15 | SVA366 | TUN → JED | Jun 15, 10:55 UTC | Jun 16, 06:15 UTC | 19h 20m |
| 2026-06-15 | SVA365 | JED → TUN | Jun 15, 06:49 UTC | Jun 15, 08:45 UTC | 1h 55m |
| 2026-06-14 | SVA890 | JED → LKO | Jun 14, 04:35 UTC | Jun 14, 04:45 UTC | 10m |
| 2026-06-13 | SVA366 | TUN → JED | Jun 13, 11:15 UTC | Jun 14, 01:10 UTC | 13h 55m |
| 2026-06-12 | SVA5537 | - | Jun 12, 12:35 UTC | Jun 13, 08:15 UTC | 19h 39m |
| 2026-06-12 | SVA5537 | - | Jun 12, 11:10 UTC | Jun 13, 08:15 UTC | 21h 4m |
| 2026-06-12 | SVA365 | JED → TUN | Jun 12, 06:35 UTC | Jun 12, 08:20 UTC | 1h 45m |
| 2026-06-11 | SVA300 | CAI → JED | Jun 11, 10:10 UTC | Jun 11, 10:20 UTC | 10m |
| 2026-06-10 | SVA752 | JED → HYD | Jun 10, 15:35 UTC | Jun 11, 07:40 UTC | 16h 5m |
| 2026-06-08 | SVA893 | LKO → JED | Jun 8, 21:15 UTC | Jun 8, 21:50 UTC | 35m |
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-AQA page for operator, model, and routing details .