sensors Mode-S transponder
71004E
ICAO 24-bit transponder address · allocated to Saudi Arabia
Currently assigned to HZ-AQE · AIRBUS A-330-300
- Hex
- 71004E
- Octal
- 34200116
- Decimal
- 7,405,646
- Country
- SA
- Tail
- HZ-AQE
- Type
- A333
- Flights observed
- 90
- Distinct callsigns
- 20
- Country
- SA
- Last broadcast
- 3h ago
Last known position
Country allocation
The ICAO 24-bit address 71004E 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 |
|---|---|---|---|
| SVA365 | - | 15 | 2026-07-12 |
| SVA890 | - | 12 | 2026-06-27 |
| SVA366 | Saudi Arabian Airlines | 10 | 2026-07-12 |
| SVA891 | - | 6 | 2026-06-28 |
| SVA866 | Saudi Arabian Airlines | 4 | 2026-06-15 |
| SVA784 | - | 4 | 2026-07-06 |
| SVA754 | Saudi Arabian Airlines | 4 | 2026-06-08 |
| SVA752 | Saudi Arabian Airlines | 4 | 2026-06-24 |
| SVA722 | Saudi Arabian Airlines | 4 | 2026-06-22 |
| SVA774 | Saudi Arabian Airlines | 3 | 2026-04-13 |
| SVA775 | - | 2 | 2026-04-13 |
| SVA5722 | - | 2 | 2026-06-14 |
| SVA387 | - | 2 | 2026-07-13 |
| SVA386 | - | 2 | 2026-07-13 |
| SVA867 | Saudi Arabian Airlines | 1 | 2026-06-13 |
| SVA783 | - | 1 | 2026-07-06 |
| SVA764 | Saudi Arabian Airlines | 1 | 2026-05-27 |
| SVA763 | Saudi Arabian Airlines | 1 | 2026-05-27 |
| SVA589 | Saudi Arabian Airlines | 1 | 2026-07-07 |
| SVA588 | - | 1 | 2026-07-07 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | SVA303 | - | Jul 14, 15:40 UTC | Jul 14, 16:00 UTC | 20m |
| 2026-07-13 | SVA386 | - | Jul 13, 23:05 UTC | Jul 14, 07:45 UTC | 8h 40m |
| 2026-07-13 | SVA387 | - | Jul 13, 06:01 UTC | Jul 13, 21:10 UTC | 15h 10m |
| 2026-07-12 | SVA366 | TUN → JED | Jul 12, 11:01 UTC | Jul 13, 04:20 UTC | 17h 20m |
| 2026-07-12 | SVA365 | - | Jul 12, 05:35 UTC | Jul 12, 08:15 UTC | 2h 40m |
| 2026-07-07 | SVA589 | DXB → JED | Jul 7, 13:55 UTC | Jul 8, 09:55 UTC | 20h 0m |
| 2026-07-07 | SVA588 | - | Jul 7, 10:50 UTC | Jul 7, 12:00 UTC | 1h 10m |
| 2026-07-06 | SVA783 | - | Jul 6, 06:05 UTC | Jul 6, 18:50 UTC | 12h 45m |
| 2026-07-06 | SVA784 | - | Jul 6, 00:20 UTC | Jul 6, 04:20 UTC | 4h 0m |
| 2026-07-04 | SVA388 | - | Jul 4, 20:45 UTC | Jul 4, 20:55 UTC | 10m |
| 2026-07-04 | SVA389 | - | Jul 4, 18:20 UTC | Jul 4, 18:40 UTC | 20m |
| 2026-06-29 | SVA305 | JED → CAI | Jun 29, 12:55 UTC | Jun 29, 13:09 UTC | 15m |
| 2026-06-28 | SVA891 | - | Jun 28, 07:50 UTC | Jun 28, 09:55 UTC | 2h 5m |
| 2026-06-27 | SVA890 | - | Jun 27, 10:54 UTC | Jun 28, 04:44 UTC | 17h 50m |
| 2026-06-27 | SVA365 | - | Jun 27, 05:55 UTC | Jun 27, 08:05 UTC | 2h 10m |
| 2026-06-26 | SVA365 | - | Jun 26, 11:34 UTC | Jun 27, 08:05 UTC | 20h 30m |
| 2026-06-26 | SVA365 | - | Jun 26, 11:00 UTC | Jun 27, 08:05 UTC | 21h 5m |
| 2026-06-26 | SVA365 | - | Jun 26, 06:35 UTC | Jun 26, 08:20 UTC | 1h 45m |
| 2026-06-24 | SVA752 | JED → HYD | Jun 24, 06:04 UTC | Jun 25, 00:49 UTC | 18h 45m |
| 2026-06-24 | SVA784 | - | Jun 24, 00:09 UTC | Jun 24, 04:10 UTC | 4h 0m |
| 2026-06-22 | SVA722 | JED → ISB | Jun 22, 00:24 UTC | Jun 22, 08:15 UTC | 7h 50m |
| 2026-06-21 | SVA722 | JED → ISB | Jun 21, 05:59 UTC | Jun 22, 03:14 UTC | 21h 15m |
| 2026-06-21 | SVA784 | JED → COK | Jun 21, 00:04 UTC | Jun 21, 04:04 UTC | 4h 0m |
| 2026-06-20 | SVA784 | JED → COK | Jun 20, 06:10 UTC | Jun 21, 04:04 UTC | 21h 55m |
| 2026-06-20 | SVA5752 | - | Jun 20, 00:39 UTC | Jun 20, 06:10 UTC | 5h 30m |
| 2026-06-19 | SVA891 | - | Jun 19, 07:49 UTC | Jun 20, 06:10 UTC | 22h 20m |
| 2026-06-19 | SVA890 | - | Jun 19, 00:40 UTC | Jun 19, 04:29 UTC | 3h 50m |
| 2026-06-15 | SVA752 | JED → HYD | Jun 15, 06:15 UTC | Jun 16, 00:55 UTC | 18h 40m |
| 2026-06-15 | SVA866 | JED → BLR | Jun 15, 02:30 UTC | Jun 15, 04:10 UTC | 1h 40m |
| 2026-06-14 | SVA866 | JED → BLR | Jun 14, 06:15 UTC | Jun 15, 04:10 UTC | 21h 54m |
| 2026-06-14 | SVA5722 | - | Jun 14, 00:30 UTC | Jun 14, 06:15 UTC | 5h 45m |
| 2026-06-13 | SVA867 | BLR → JED | Jun 13, 06:05 UTC | Jun 13, 16:00 UTC | 9h 55m |
| 2026-06-13 | SVA866 | JED → BLR | Jun 13, 00:10 UTC | Jun 13, 04:10 UTC | 4h 0m |
| 2026-06-12 | SVA866 | JED → BLR | Jun 12, 08:00 UTC | Jun 13, 04:10 UTC | 20h 10m |
| 2026-06-12 | SVA890 | JED → LKO | Jun 12, 03:00 UTC | Jun 12, 03:55 UTC | 55m |
| 2026-06-08 | SVA754 | JED → HYD | Jun 8, 00:10 UTC | Jun 8, 07:30 UTC | 7h 20m |
| 2026-06-05 | SVA752 | JED → HYD | Jun 5, 07:25 UTC | Jun 5, 22:30 UTC | 15h 5m |
| 2026-06-04 | SVA5722 | - | Jun 4, 00:30 UTC | Jun 4, 06:30 UTC | 6h 0m |
| 2026-06-02 | SVA387 | JED → CAI | Jun 2, 20:50 UTC | Jun 2, 21:10 UTC | 20m |
| 2026-06-01 | SVA891 | LKO → JED | Jun 1, 08:00 UTC | Jun 1, 08:55 UTC | 55m |
| 2026-06-01 | SVA891 | LKO → JED | Jun 1, 06:45 UTC | Jun 1, 07:00 UTC | 15m |
| 2026-05-31 | SVA890 | JED → LKO | May 31, 10:05 UTC | Jun 1, 03:40 UTC | 17h 35m |
| 2026-05-31 | SVA3524 | - | May 31, 08:35 UTC | May 31, 08:50 UTC | 15m |
| 2026-05-30 | SVA3558 | JED → DOH | May 30, 12:20 UTC | May 30, 17:50 UTC | 5h 30m |
| 2026-05-29 | SVA1129 | DMM → JED | May 29, 19:20 UTC | May 30, 10:05 UTC | 14h 45m |
| 2026-05-29 | SVA301 | JED → CAI | May 29, 07:35 UTC | May 29, 07:45 UTC | 10m |
| 2026-05-27 | SVA763 | DEL → DMM | May 27, 21:30 UTC | May 27, 22:55 UTC | 1h 25m |
| 2026-05-27 | SVA764 | JED → COK | May 27, 15:35 UTC | May 27, 19:35 UTC | 4h 0m |
| 2026-05-26 | SVA366 | TUN → JED | May 26, 10:54 UTC | May 26, 12:30 UTC | 1h 35m |
| 2026-05-25 | SVA752 | JED → HYD | May 25, 17:10 UTC | May 26, 08:19 UTC | 15h 10m |
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-AQE page for operator, model, and routing details .