sensors Mode-S transponder
710122
ICAO 24-bit transponder address · allocated to Saudi Arabia
Currently assigned to HZ-AQ25 · AIRBUS A-330-300
- Hex
- 710122
- Octal
- 34200442
- Decimal
- 7,405,858
- Country
- SA
- Tail
- HZ-AQ25
- Type
- A333
- Flights observed
- 125
- Distinct callsigns
- 20
- Country
- SA
- Last broadcast
- 2h ago
Last known position
Country allocation
The ICAO 24-bit address 710122 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 |
|---|---|---|---|
| SVA708 | - | 10 | 2026-07-05 |
| SVA257 | - | 7 | 2026-07-12 |
| SVA211 | - | 7 | 2026-06-25 |
| SVA321 | - | 6 | 2026-07-02 |
| SVA588 | - | 5 | 2026-07-14 |
| SVA263 | - | 5 | 2026-06-20 |
| SVA256 | Saudi Arabian Airlines | 5 | 2026-07-13 |
| SVA210 | Saudi Arabian Airlines | 5 | 2026-06-26 |
| SVA700 | Saudi Arabian Airlines | 4 | 2026-04-30 |
| SVA5500 | - | 4 | 2026-04-25 |
| SVA264 | Saudi Arabian Airlines | 4 | 2026-06-20 |
| SVA417 | - | 3 | 2026-07-02 |
| SVA320 | Saudi Arabian Airlines | 3 | 2026-06-12 |
| SVA307 | - | 3 | 2026-07-08 |
| SVA259 | - | 3 | 2026-06-19 |
| SVA258 | - | 3 | 2026-06-19 |
| SVA9801 | - | 2 | 2026-04-24 |
| SVA9608 | - | 2 | 2026-06-05 |
| SVA784 | Saudi Arabian Airlines | 2 | 2026-04-26 |
| SVA774 | Saudi Arabian Airlines | 2 | 2026-06-06 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | SVA589 | DXB → JED | Jul 14, 13:50 UTC | Jul 14, 14:45 UTC | 55m |
| 2026-07-14 | SVA588 | - | Jul 14, 01:55 UTC | Jul 14, 12:00 UTC | 10h 5m |
| 2026-07-13 | SVA256 | IST → JED | Jul 13, 12:50 UTC | Jul 14, 00:05 UTC | 11h 15m |
| 2026-07-12 | SVA257 | - | Jul 12, 17:50 UTC | Jul 13, 10:20 UTC | 16h 30m |
| 2026-07-12 | SVA704 | JED → KHI | Jul 12, 10:20 UTC | Jul 13, 08:30 UTC | 22h 10m |
| 2026-07-12 | SVA301 | - | Jul 12, 07:50 UTC | Jul 12, 08:15 UTC | 25m |
| 2026-07-11 | SVA256 | IST → JED | Jul 11, 12:55 UTC | Jul 11, 14:55 UTC | 2h 0m |
| 2026-07-10 | SVA257 | - | Jul 10, 18:05 UTC | Jul 11, 10:15 UTC | 16h 11m |
| 2026-07-09 | SVA303 | - | Jul 9, 20:45 UTC | Jul 10, 16:05 UTC | 19h 20m |
| 2026-07-09 | SVA389 | - | Jul 9, 12:15 UTC | Jul 9, 18:45 UTC | 6h 30m |
| 2026-07-08 | SVA307 | - | Jul 8, 23:25 UTC | Jul 9, 09:55 UTC | 10h 30m |
| 2026-07-08 | SVA387 | - | Jul 8, 20:40 UTC | Jul 8, 21:00 UTC | 20m |
| 2026-07-08 | SVA304 | CAI → JED | Jul 8, 15:35 UTC | Jul 8, 15:45 UTC | 10m |
| 2026-07-08 | SVA305 | JED → CAI | Jul 8, 13:10 UTC | Jul 8, 13:20 UTC | 10m |
| 2026-07-06 | SVA704 | JED → KHI | Jul 6, 12:20 UTC | Jul 7, 00:00 UTC | 11h 40m |
| 2026-07-05 | SVA388 | - | Jul 5, 20:50 UTC | Jul 6, 09:55 UTC | 13h 5m |
| 2026-07-05 | SVA708 | - | Jul 5, 04:15 UTC | Jul 5, 18:35 UTC | 14h 20m |
| 2026-07-04 | SVA708 | - | Jul 4, 19:15 UTC | Jul 5, 18:30 UTC | 23h 15m |
| 2026-07-04 | SVA708 | - | Jul 4, 04:20 UTC | Jul 4, 16:00 UTC | 11h 40m |
| 2026-07-03 | SVA708 | - | Jul 3, 18:35 UTC | Jul 4, 16:00 UTC | 21h 25m |
| 2026-07-03 | SVA708 | - | Jul 3, 18:15 UTC | Jul 4, 16:00 UTC | 21h 45m |
| 2026-07-02 | SVA708 | - | Jul 2, 22:05 UTC | Jul 3, 16:05 UTC | 18h 0m |
| 2026-07-02 | SVA321 | - | Jul 2, 13:20 UTC | Jul 2, 19:55 UTC | 6h 35m |
| 2026-07-02 | SVA417 | - | Jul 2, 10:40 UTC | Jul 2, 11:00 UTC | 20m |
| 2026-07-01 | SVA708 | - | Jul 1, 04:30 UTC | Jul 1, 10:55 UTC | 6h 25m |
| 2026-06-29 | SVA212 | - | Jun 29, 14:29 UTC | Jun 29, 18:10 UTC | 3h 40m |
| 2026-06-29 | SVA213 | - | Jun 29, 08:04 UTC | Jun 29, 11:50 UTC | 3h 45m |
| 2026-06-27 | SVA236 | GVA → JED | Jun 27, 14:35 UTC | Jun 27, 18:04 UTC | 3h 30m |
| 2026-06-27 | SVA237 | - | Jun 27, 02:20 UTC | Jun 27, 12:15 UTC | 9h 55m |
| 2026-06-26 | SVA210 | MXP → RUH | Jun 26, 14:25 UTC | Jun 27, 00:00 UTC | 9h 35m |
| 2026-06-25 | SVA211 | - | Jun 25, 16:35 UTC | Jun 26, 11:30 UTC | 18h 55m |
| 2026-06-25 | SVA210 | MXP → RUH | Jun 25, 14:55 UTC | Jun 26, 11:30 UTC | 20h 35m |
| 2026-06-25 | SVA211 | - | Jun 25, 09:14 UTC | Jun 25, 11:39 UTC | 2h 25m |
| 2026-06-24 | SVA309 | - | Jun 24, 18:25 UTC | Jun 24, 23:40 UTC | 5h 15m |
| 2026-06-24 | SVA303 | JED → CAI | Jun 24, 15:39 UTC | Jun 24, 15:54 UTC | 15m |
| 2026-06-23 | SVA389 | JED → CAI | Jun 23, 18:10 UTC | Jun 23, 18:29 UTC | 20m |
| 2026-06-23 | SVA307 | JED → CAI | Jun 23, 09:54 UTC | Jun 23, 10:04 UTC | 10m |
| 2026-06-20 | SVA264 | IST → RUH | Jun 20, 14:05 UTC | Jun 20, 16:00 UTC | 1h 55m |
| 2026-06-20 | SVA263 | - | Jun 20, 10:29 UTC | Jun 20, 12:24 UTC | 1h 55m |
| 2026-06-19 | SVA263 | - | Jun 19, 12:34 UTC | Jun 20, 12:24 UTC | 23h 50m |
| 2026-06-19 | SVA258 | - | Jun 19, 11:45 UTC | Jun 20, 10:29 UTC | 22h 45m |
| 2026-06-19 | SVA259 | - | Jun 19, 07:25 UTC | Jun 19, 09:19 UTC | 1h 55m |
| 2026-06-18 | SVA382 | - | Jun 18, 04:00 UTC | Jun 18, 09:50 UTC | 5h 50m |
| 2026-06-18 | SVA383 | JED → CAI | Jun 18, 01:35 UTC | Jun 18, 02:10 UTC | 35m |
| 2026-06-14 | SVA307 | JED → CAI | Jun 14, 09:35 UTC | Jun 14, 09:45 UTC | 10m |
| 2026-06-13 | SVA309 | JED → CAI | Jun 13, 23:15 UTC | Jun 13, 23:25 UTC | 10m |
| 2026-06-12 | SVA320 | CAI → RUH | Jun 12, 21:45 UTC | Jun 12, 22:15 UTC | 30m |
| 2026-06-12 | SVA321 | RUH → CAI | Jun 12, 19:20 UTC | Jun 12, 19:40 UTC | 20m |
| 2026-06-11 | SVA5708 | - | Jun 11, 04:20 UTC | Jun 11, 11:00 UTC | 6h 40m |
| 2026-06-09 | SVA311 | RUH → CAI | Jun 9, 06:30 UTC | Jun 9, 06:50 UTC | 20m |
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-AQ25 page for operator, model, and routing details .