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
- 154
- Distinct callsigns
- 20
- Country
- SA
- Last broadcast
- 12h ago
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 |
|---|---|---|---|
| SVA840 | Saudi Arabian Airlines | 12 | 2026-05-24 |
| SVA117 | - | 9 | 2026-07-13 |
| SVA870 | - | 8 | 2026-07-03 |
| SVA885 | - | 7 | 2026-06-17 |
| SVA061 | - | 7 | 2026-07-09 |
| 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 |
| SVA124 | Saudi Arabian Airlines | 6 | 2026-05-16 |
| SVA123 | Saudi Arabian Airlines | 6 | 2026-05-15 |
| SVA119 | Saudi Arabian Airlines | 6 | 2026-06-03 |
| SVA846 | - | 4 | 2026-06-15 |
| SVA214 | Saudi Arabian Airlines | 4 | 2026-05-23 |
| SVA127 | - | 4 | 2026-07-02 |
| SVA118 | - | 4 | 2026-07-13 |
| SVA884 | - | 3 | 2026-06-17 |
| SVA871 | - | 3 | 2026-07-04 |
| SVA847 | Saudi Arabian Airlines | 3 | 2026-06-16 |
| SVA379 | - | 3 | 2026-07-02 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 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 |
| 2026-06-15 | SVA846 | - | Jun 15, 23:39 UTC | Jun 16, 06:30 UTC | 6h 50m |
| 2026-06-14 | SVA118 | - | Jun 14, 21:40 UTC | Jun 15, 00:49 UTC | 3h 10m |
| 2026-06-14 | SVA117 | RUH → LHR | Jun 14, 01:15 UTC | Jun 14, 19:50 UTC | 18h 36m |
| 2026-06-13 | SVA117 | RUH → LHR | Jun 13, 23:40 UTC | Jun 14, 19:50 UTC | 20h 11m |
| 2026-06-13 | SVA5599 | - | Jun 13, 18:25 UTC | Jun 13, 22:00 UTC | 3h 35m |
| 2026-06-12 | SVA126 | CDG → JED | Jun 12, 14:20 UTC | Jun 12, 17:15 UTC | 2h 55m |
| 2026-06-11 | SVA127 | LHR → CDG | Jun 11, 21:30 UTC | Jun 12, 11:55 UTC | 14h 25m |
| 2026-06-11 | SVA117 | RUH → LHR | Jun 11, 14:55 UTC | Jun 11, 19:45 UTC | 4h 50m |
| 2026-06-10 | SVA118 | LHR → RUH | Jun 10, 21:20 UTC | Jun 11, 01:25 UTC | 4h 5m |
| 2026-06-10 | SVA117 | RUH → LHR | Jun 10, 15:05 UTC | Jun 10, 19:35 UTC | 4h 30m |
| 2026-06-09 | SVA117 | RUH → LHR | Jun 9, 21:05 UTC | Jun 10, 19:35 UTC | 22h 30m |
| 2026-06-09 | SVA117 | RUH → LHR | Jun 9, 19:05 UTC | Jun 10, 19:00 UTC | 23h 55m |
| 2026-06-09 | SVA378 | CMN → JED | Jun 9, 18:30 UTC | Jun 10, 17:00 UTC | 22h 30m |
| 2026-06-08 | SVA379 | JED → CMN | Jun 8, 23:20 UTC | Jun 9, 15:50 UTC | 16h 30m |
| 2026-06-08 | SVA5645 | - | Jun 8, 16:00 UTC | Jun 8, 21:00 UTC | 5h 0m |
| 2026-06-07 | SVA5645 | - | Jun 7, 21:10 UTC | Jun 8, 21:00 UTC | 23h 50m |
| 2026-06-07 | SVA889 | PKX → RUH | Jun 7, 03:35 UTC | Jun 7, 21:25 UTC | 17h 50m |
| 2026-06-04 | SVA120 | LHR → RUH | Jun 4, 14:55 UTC | Jun 4, 18:15 UTC | 3h 20m |
| 2026-06-03 | SVA119 | JED → LHR | Jun 3, 19:05 UTC | Jun 4, 11:55 UTC | 16h 50m |
| 2026-06-03 | SVA9618 | - | Jun 3, 00:15 UTC | Jun 3, 16:45 UTC | 16h 30m |
| 2026-06-02 | SVA130 | CDG → JED | Jun 2, 06:40 UTC | Jun 2, 22:15 UTC | 15h 35m |
| 2026-06-01 | SVA131 | JED → CDG | Jun 1, 14:40 UTC | Jun 2, 04:05 UTC | 13h 25m |
| 2026-05-31 | SVA215 | JED → AMS | May 31, 17:05 UTC | Jun 1, 12:20 UTC | 19h 15m |
| 2026-05-31 | SVA215 | JED → AMS | May 31, 16:05 UTC | Jun 1, 12:20 UTC | 20h 15m |
| 2026-05-31 | SVA889 | PKX → RUH | May 31, 00:15 UTC | May 31, 21:25 UTC | 21h 10m |
| 2026-05-30 | SVA885 | CAN → RUH | May 30, 08:45 UTC | May 31, 00:35 UTC | 15h 50m |
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 .