sensors Mode-S transponder
710132
ICAO 24-bit transponder address · allocated to Saudi Arabia
Currently assigned to HZ-AQ29 · AIRBUS A-330-300
- Hex
- 710132
- Octal
- 34200462
- Decimal
- 7,405,874
- Country
- SA
- Tail
- HZ-AQ29
- Type
- A333
- Flights observed
- 111
- Distinct callsigns
- 20
- Country
- SA
- Last broadcast
- 6h ago
Last known position
Country allocation
The ICAO 24-bit address 710132 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 |
|---|---|---|---|
| SVA237 | - | 7 | 2026-07-05 |
| SVA257 | - | 6 | 2026-07-04 |
| SVA211 | - | 6 | 2026-07-10 |
| SVA210 | - | 6 | 2026-07-10 |
| SVA313 | Saudi Arabian Airlines | 5 | 2026-06-23 |
| SVA256 | Saudi Arabian Airlines | 5 | 2026-06-20 |
| SVA597 | - | 4 | 2026-06-25 |
| SVA596 | Saudi Arabian Airlines | 4 | 2026-05-02 |
| SVA311 | Saudi Arabian Airlines | 4 | 2026-05-26 |
| SVA263 | Saudi Arabian Airlines | 4 | 2026-04-26 |
| SVA708 | Saudi Arabian Airlines | 3 | 2026-05-20 |
| SVA387 | - | 3 | 2026-07-02 |
| SVA3775 | Saudi Arabian Airlines | 3 | 2026-04-19 |
| SVA3774 | Saudi Arabian Airlines | 3 | 2026-04-19 |
| SVA321 | Saudi Arabian Airlines | 3 | 2026-05-26 |
| SVA417 | Saudi Arabian Airlines | 2 | 2026-05-26 |
| SVA389 | Saudi Arabian Airlines | 2 | 2026-05-22 |
| SVA386 | - | 2 | 2026-06-29 |
| SVA320 | - | 2 | 2026-07-01 |
| SVA312 | Saudi Arabian Airlines | 2 | 2026-05-27 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | SVA559 | - | Jul 14, 12:30 UTC | Jul 14, 13:25 UTC | 55m |
| 2026-07-13 | SVA212 | - | Jul 13, 14:35 UTC | Jul 14, 10:30 UTC | 19h 55m |
| 2026-07-13 | SVA213 | - | Jul 13, 08:15 UTC | Jul 13, 12:00 UTC | 3h 45m |
| 2026-07-10 | SVA210 | - | Jul 10, 14:25 UTC | Jul 10, 17:20 UTC | 2h 55m |
| 2026-07-10 | SVA211 | - | Jul 10, 08:05 UTC | Jul 10, 11:50 UTC | 3h 45m |
| 2026-07-08 | SVA302 | - | Jul 8, 18:15 UTC | Jul 8, 18:35 UTC | 20m |
| 2026-07-08 | SVA303 | - | Jul 8, 15:50 UTC | Jul 8, 16:10 UTC | 20m |
| 2026-07-05 | SVA236 | GVA → JED | Jul 5, 14:20 UTC | Jul 5, 17:00 UTC | 2h 40m |
| 2026-07-05 | SVA237 | - | Jul 5, 09:25 UTC | Jul 5, 12:30 UTC | 3h 5m |
| 2026-07-04 | SVA237 | - | Jul 4, 14:35 UTC | Jul 5, 12:30 UTC | 21h 55m |
| 2026-07-04 | SVA237 | - | Jul 4, 12:55 UTC | Jul 5, 12:30 UTC | 23h 35m |
| 2026-07-04 | SVA257 | - | Jul 4, 08:45 UTC | Jul 4, 11:05 UTC | 2h 20m |
| 2026-07-02 | SVA387 | - | Jul 2, 20:50 UTC | Jul 2, 21:10 UTC | 20m |
| 2026-07-02 | SVA304 | CAI → JED | Jul 2, 15:25 UTC | Jul 2, 15:35 UTC | 10m |
| 2026-07-01 | SVA320 | - | Jul 1, 22:10 UTC | Jul 2, 13:20 UTC | 15h 10m |
| 2026-07-01 | SVA418 | CAI → RUH | Jul 1, 13:20 UTC | Jul 1, 19:50 UTC | 6h 30m |
| 2026-06-30 | SVA210 | MXP → RUH | Jun 30, 16:35 UTC | Jul 1, 11:10 UTC | 18h 35m |
| 2026-06-30 | SVA210 | MXP → RUH | Jun 30, 14:35 UTC | Jul 1, 11:10 UTC | 20h 35m |
| 2026-06-30 | SVA211 | - | Jun 30, 08:35 UTC | Jun 30, 11:35 UTC | 3h 0m |
| 2026-06-29 | SVA386 | - | Jun 29, 23:14 UTC | Jun 29, 23:25 UTC | 10m |
| 2026-06-29 | SVA387 | - | Jun 29, 20:35 UTC | Jun 29, 20:49 UTC | 15m |
| 2026-06-29 | SVA301 | JED → CAI | Jun 29, 07:34 UTC | Jun 29, 07:55 UTC | 20m |
| 2026-06-29 | SVA308 | - | Jun 29, 01:50 UTC | Jun 29, 02:00 UTC | 10m |
| 2026-06-28 | SVA236 | GVA → JED | Jun 28, 14:14 UTC | Jun 28, 23:34 UTC | 9h 20m |
| 2026-06-28 | SVA237 | - | Jun 28, 08:25 UTC | Jun 28, 12:19 UTC | 3h 55m |
| 2026-06-25 | SVA3262 | - | Jun 25, 22:20 UTC | Jun 25, 22:45 UTC | 25m |
| 2026-06-25 | SVA597 | - | Jun 25, 09:34 UTC | Jun 25, 20:05 UTC | 10h 30m |
| 2026-06-24 | SVA238 | GVA → RUH | Jun 24, 14:15 UTC | Jun 25, 07:59 UTC | 17h 45m |
| 2026-06-24 | SVA239 | - | Jun 24, 08:09 UTC | Jun 24, 12:25 UTC | 4h 15m |
| 2026-06-23 | SVA313 | RUH → CAI | Jun 23, 19:39 UTC | Jun 23, 19:55 UTC | 15m |
| 2026-06-20 | SVA256 | IST → JED | Jun 20, 12:50 UTC | Jun 20, 14:44 UTC | 1h 55m |
| 2026-06-20 | SVA257 | - | Jun 20, 00:34 UTC | Jun 20, 10:15 UTC | 9h 40m |
| 2026-06-19 | SVA5515 | - | Jun 19, 20:40 UTC | Jun 19, 22:09 UTC | 1h 30m |
| 2026-06-18 | SVA305 | JED → CAI | Jun 18, 13:30 UTC | Jun 18, 13:45 UTC | 15m |
| 2026-06-11 | SVA256 | IST → JED | Jun 11, 12:35 UTC | Jun 11, 14:30 UTC | 1h 55m |
| 2026-06-11 | SVA257 | JED → IST | Jun 11, 01:40 UTC | Jun 11, 10:35 UTC | 8h 55m |
| 2026-06-10 | SVA309 | JED → CAI | Jun 10, 23:20 UTC | Jun 10, 23:55 UTC | 35m |
| 2026-06-10 | SVA305 | JED → CAI | Jun 10, 13:05 UTC | Jun 10, 13:25 UTC | 20m |
| 2026-06-09 | SVA258 | IST → MED | Jun 9, 11:25 UTC | Jun 9, 13:25 UTC | 2h 0m |
| 2026-06-09 | SVA259 | MED → IST | Jun 9, 07:25 UTC | Jun 9, 09:30 UTC | 2h 5m |
| 2026-06-07 | SVA5509 | - | Jun 7, 05:15 UTC | Jun 7, 10:45 UTC | 5h 30m |
| 2026-06-06 | SVA386 | CAI → JED | Jun 6, 23:09 UTC | Jun 6, 23:24 UTC | 15m |
| 2026-06-06 | SVA387 | JED → CAI | Jun 6, 20:39 UTC | Jun 6, 21:09 UTC | 30m |
| 2026-06-06 | SVA5501 | - | Jun 6, 00:25 UTC | Jun 6, 09:55 UTC | 9h 30m |
| 2026-06-04 | SVA9800 | - | Jun 4, 00:35 UTC | Jun 4, 11:10 UTC | 10h 35m |
| 2026-06-03 | - | - | Jun 3, 13:10 UTC | Jun 3, 13:20 UTC | 10m |
| 2026-06-02 | SVA9652 | - | Jun 2, 05:25 UTC | Jun 2, 07:05 UTC | 1h 40m |
| 2026-06-02 | SVA5541 | - | Jun 2, 00:35 UTC | Jun 2, 03:15 UTC | 2h 40m |
| 2026-05-27 | SVA312 | CAI → RUH | May 27, 18:30 UTC | May 27, 18:45 UTC | 15m |
| 2026-05-27 | SVA313 | RUH → CAI | May 27, 15:45 UTC | May 27, 16:05 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-AQ29 page for operator, model, and routing details .