sensors Mode-S transponder
710124
ICAO 24-bit transponder address · allocated to Saudi Arabia
Currently assigned to HZ-AR13 · BOEING 787-9 Dreamliner
- Hex
- 710124
- Octal
- 34200444
- Decimal
- 7,405,860
- Country
- SA
- Tail
- HZ-AR13
- Type
- B789
- Flights observed
- 180
- Distinct callsigns
- 20
- Country
- SA
- Last broadcast
- Jul 26, 20:00 UTC
Last known position
Country allocation
The ICAO 24-bit address 710124 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 |
|---|---|---|---|
| SVA117 | Saudi Arabian Airlines | 13 | 2026-07-25 |
| SVA840 | Saudi Arabian Airlines | 12 | 2026-05-24 |
| SVA885 | - | 10 | 2026-07-16 |
| SVA870 | - | 8 | 2026-07-03 |
| SVA375 | - | 8 | 2026-07-17 |
| SVA061 | Saudi Arabian Airlines | 8 | 2026-07-23 |
| SVA124 | Saudi Arabian Airlines | 7 | 2026-07-26 |
| SVA123 | Saudi Arabian Airlines | 7 | 2026-07-25 |
| SVA889 | Saudi Arabian Airlines | 6 | 2026-06-07 |
| SVA841 | Saudi Arabian Airlines | 6 | 2026-05-25 |
| SVA373 | - | 6 | 2026-07-08 |
| SVA215 | Saudi Arabian Airlines | 6 | 2026-05-31 |
| SVA119 | Saudi Arabian Airlines | 6 | 2026-06-03 |
| SVA118 | - | 6 | 2026-07-14 |
| SVA884 | - | 5 | 2026-07-15 |
| SVA846 | - | 4 | 2026-06-15 |
| SVA214 | Saudi Arabian Airlines | 4 | 2026-05-23 |
| SVA127 | - | 4 | 2026-07-02 |
| SVA062 | Saudi Arabian Airlines | 4 | 2026-07-24 |
| SVA883 | Saudi Arabian Airlines | 3 | 2026-07-22 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | SVA124 | MAN → JED | Jul 26, 15:40 UTC | Jul 26, 20:00 UTC | 4h 20m |
| 2026-07-25 | SVA123 | GVA → MAN | Jul 25, 22:00 UTC | Jul 26, 11:55 UTC | 13h 56m |
| 2026-07-25 | SVA117 | RUH → LHR | Jul 25, 01:05 UTC | Jul 25, 19:05 UTC | 18h 0m |
| 2026-07-24 | SVA117 | RUH → LHR | Jul 24, 23:05 UTC | Jul 25, 19:05 UTC | 20h 0m |
| 2026-07-24 | SVA117 | RUH → LHR | Jul 24, 21:30 UTC | Jul 25, 19:05 UTC | 21h 35m |
| 2026-07-24 | SVA062 | YYZ → JED | Jul 24, 04:20 UTC | Jul 24, 19:10 UTC | 14h 50m |
| 2026-07-23 | SVA062 | YYZ → JED | Jul 23, 23:15 UTC | Jul 24, 19:10 UTC | 19h 55m |
| 2026-07-23 | SVA061 | JED → YYZ | Jul 23, 09:05 UTC | Jul 23, 19:30 UTC | 10h 25m |
| 2026-07-22 | SVA883 | CAN → JED | Jul 22, 17:05 UTC | Jul 23, 08:30 UTC | 15h 25m |
| 2026-07-22 | SVA883 | CAN → JED | Jul 22, 03:55 UTC | Jul 22, 22:00 UTC | 18h 5m |
| 2026-07-22 | SVA883 | CAN → JED | Jul 22, 01:50 UTC | Jul 22, 22:00 UTC | 20h 10m |
| 2026-07-21 | SVA882 | JED → CAN | Jul 21, 23:55 UTC | Jul 22, 22:00 UTC | 22h 5m |
| 2026-07-18 | SVA374 | CMN → RUH | Jul 18, 20:55 UTC | Jul 19, 01:05 UTC | 4h 10m |
| 2026-07-17 | SVA375 | - | Jul 17, 23:25 UTC | Jul 18, 17:05 UTC | 17h 41m |
| 2026-07-17 | SVA375 | - | Jul 17, 21:05 UTC | Jul 18, 17:05 UTC | 20h 1m |
| 2026-07-17 | SVA375 | - | Jul 17, 19:40 UTC | Jul 18, 17:05 UTC | 21h 26m |
| 2026-07-17 | SVA375 | - | Jul 17, 12:40 UTC | Jul 17, 17:30 UTC | 4h 50m |
| 2026-07-16 | SVA375 | - | Jul 16, 15:05 UTC | Jul 17, 15:00 UTC | 23h 55m |
| 2026-07-16 | SVA885 | - | Jul 16, 13:05 UTC | Jul 17, 13:00 UTC | 23h 55m |
| 2026-07-16 | SVA885 | - | Jul 16, 09:55 UTC | Jul 16, 15:14 UTC | 5h 20m |
| 2026-07-16 | SVA885 | - | Jul 16, 07:50 UTC | Jul 16, 08:05 UTC | 15m |
| 2026-07-15 | SVA884 | - | Jul 15, 21:15 UTC | Jul 16, 03:15 UTC | 6h 0m |
| 2026-07-15 | SVA884 | - | Jul 15, 01:15 UTC | Jul 16, 00:10 UTC | 22h 55m |
| 2026-07-14 | SVA118 | - | Jul 14, 23:05 UTC | Jul 15, 22:25 UTC | 23h 20m |
| 2026-07-14 | SVA118 | - | Jul 14, 21:50 UTC | Jul 15, 01:45 UTC | 3h 54m |
| 2026-07-14 | SVA117 | - | Jul 14, 14:35 UTC | Jul 14, 19:35 UTC | 5h 0m |
| 2026-07-13 | SVA118 | - | Jul 13, 21:30 UTC | Jul 14, 01:55 UTC | 4h 25m |
| 2026-07-13 | SVA117 | - | Jul 13, 14:25 UTC | Jul 13, 19:10 UTC | 4h 45m |
| 2026-07-10 | SVA062 | - | Jul 10, 00:00 UTC | Jul 10, 10:00 UTC | 10h 0m |
| 2026-07-09 | SVA061 | - | Jul 9, 07:45 UTC | Jul 9, 19:10 UTC | 11h 25m |
| 2026-07-08 | SVA061 | - | Jul 8, 17:05 UTC | Jul 9, 17:00 UTC | 23h 55m |
| 2026-07-08 | SVA061 | - | Jul 8, 15:05 UTC | Jul 9, 13:05 UTC | 22h 0m |
| 2026-07-08 | SVA061 | - | Jul 8, 14:20 UTC | Jul 9, 13:00 UTC | 22h 40m |
| 2026-07-08 | SVA373 | - | Jul 8, 08:10 UTC | Jul 8, 11:55 UTC | 3h 45m |
| 2026-07-05 | SVA228 | BCN → JED | Jul 5, 15:05 UTC | Jul 5, 17:45 UTC | 2h 40m |
| 2026-07-04 | SVA871 | - | Jul 4, 17:25 UTC | Jul 5, 12:45 UTC | 19h 20m |
| 2026-07-04 | SVA871 | - | Jul 4, 15:40 UTC | Jul 5, 12:45 UTC | 21h 5m |
| 2026-07-03 | SVA870 | - | Jul 3, 17:05 UTC | Jul 4, 12:10 UTC | 19h 5m |
| 2026-07-03 | SVA870 | - | Jul 3, 15:05 UTC | Jul 4, 12:10 UTC | 21h 5m |
| 2026-07-03 | SVA870 | - | Jul 3, 14:30 UTC | Jul 4, 12:10 UTC | 21h 40m |
| 2026-07-02 | SVA127 | - | Jul 2, 18:25 UTC | Jul 3, 11:20 UTC | 16h 55m |
| 2026-07-02 | SVA379 | - | Jul 2, 11:45 UTC | Jul 2, 16:25 UTC | 4h 40m |
| 2026-06-30 | SVA220 | - | Jun 30, 15:00 UTC | Jun 30, 18:55 UTC | 3h 55m |
| 2026-06-30 | SVA227 | - | Jun 30, 07:10 UTC | Jun 30, 10:50 UTC | 3h 40m |
| 2026-06-23 | SVA3655 | - | Jun 23, 03:49 UTC | Jun 23, 09:40 UTC | 5h 50m |
| 2026-06-22 | SVA3654 | RUH → CCJ | Jun 22, 07:25 UTC | Jun 23, 01:25 UTC | 18h 0m |
| 2026-06-21 | SVA3838 | - | Jun 21, 21:34 UTC | Jun 22, 04:49 UTC | 7h 15m |
| 2026-06-17 | SVA885 | - | Jun 17, 23:25 UTC | Jun 18, 17:15 UTC | 17h 50m |
| 2026-06-17 | SVA884 | - | Jun 17, 21:30 UTC | Jun 18, 17:15 UTC | 19h 45m |
| 2026-06-16 | SVA847 | BKK → RUH | Jun 16, 08:44 UTC | Jun 16, 12:55 UTC | 4h 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-AR13 page for operator, model, and routing details .