sensors Mode-S transponder
7103D6
ICAO 24-bit transponder address · allocated to Saudi Arabia
Currently assigned to HZ-AR12 · BOEING 787-9 Dreamliner
- Hex
- 7103D6
- Octal
- 34201726
- Decimal
- 7,406,550
- Country
- SA
- Tail
- HZ-AR12
- Type
- B789
- Flights observed
- 165
- Distinct callsigns
- 20
- Country
- SA
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 7103D6 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 |
|---|---|---|---|
| SVA375 | - | 23 | 2026-07-03 |
| SVA061 | - | 12 | 2026-06-26 |
| SVA215 | Saudi Arabian Airlines | 10 | 2026-06-10 |
| SVA062 | - | 10 | 2026-06-27 |
| SVA889 | Saudi Arabian Airlines | 9 | 2026-05-27 |
| SVA117 | - | 8 | 2026-07-04 |
| SVA888 | Saudi Arabian Airlines | 7 | 2026-05-05 |
| SVA130 | - | 6 | 2026-06-30 |
| SVA379 | Saudi Arabian Airlines | 5 | 2026-05-30 |
| SVA374 | - | 5 | 2026-07-04 |
| SVA123 | Saudi Arabian Airlines | 5 | 2026-06-09 |
| SVA9631 | - | 4 | 2026-05-12 |
| SVA214 | Saudi Arabian Airlines | 4 | 2026-06-11 |
| SVA127 | - | 4 | 2026-07-05 |
| SVA126 | - | 4 | 2026-07-06 |
| SVA9623 | - | 3 | 2026-05-15 |
| SVA870 | - | 3 | 2026-07-06 |
| SVA846 | Saudi Arabian Airlines | 3 | 2026-05-05 |
| SVA253 | Saudi Arabian Airlines | 3 | 2026-06-13 |
| SVA131 | - | 3 | 2026-06-29 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-12 | SVA9063 | - | Jul 12, 16:10 UTC | Jul 13, 02:20 UTC | 10h 10m |
| 2026-07-06 | SVA870 | - | Jul 6, 17:45 UTC | Jul 7, 12:30 UTC | 18h 45m |
| 2026-07-06 | SVA870 | - | Jul 6, 17:20 UTC | Jul 7, 12:30 UTC | 19h 10m |
| 2026-07-06 | SVA126 | - | Jul 6, 14:05 UTC | Jul 6, 17:10 UTC | 3h 5m |
| 2026-07-05 | SVA127 | - | Jul 5, 21:45 UTC | Jul 6, 11:30 UTC | 13h 45m |
| 2026-07-04 | SVA117 | - | Jul 4, 23:35 UTC | Jul 5, 19:05 UTC | 19h 30m |
| 2026-07-04 | SVA374 | - | Jul 4, 19:45 UTC | Jul 4, 23:00 UTC | 3h 15m |
| 2026-07-03 | SVA375 | - | Jul 3, 21:35 UTC | Jul 4, 16:50 UTC | 19h 15m |
| 2026-07-03 | SVA375 | - | Jul 3, 19:35 UTC | Jul 4, 16:50 UTC | 21h 15m |
| 2026-07-02 | SVA375 | RUH → CMN | Jul 2, 21:40 UTC | Jul 3, 16:55 UTC | 19h 15m |
| 2026-07-02 | SVA375 | RUH → CMN | Jul 2, 19:50 UTC | Jul 3, 16:55 UTC | 21h 5m |
| 2026-07-02 | SVA375 | RUH → CMN | Jul 2, 12:25 UTC | Jul 2, 16:55 UTC | 4h 30m |
| 2026-07-01 | SVA375 | RUH → CMN | Jul 1, 19:45 UTC | Jul 2, 16:55 UTC | 21h 10m |
| 2026-07-01 | SVA375 | RUH → CMN | Jul 1, 17:45 UTC | Jul 2, 16:55 UTC | 23h 10m |
| 2026-07-01 | SVA230 | - | Jul 1, 16:35 UTC | Jul 2, 15:15 UTC | 22h 40m |
| 2026-07-01 | SVA231 | - | Jul 1, 10:10 UTC | Jul 1, 14:05 UTC | 3h 55m |
| 2026-06-30 | SVA130 | - | Jun 30, 06:40 UTC | Jun 30, 09:55 UTC | 3h 15m |
| 2026-06-29 | SVA131 | - | Jun 29, 23:54 UTC | Jun 30, 03:45 UTC | 3h 51m |
| 2026-06-28 | SVA220 | - | Jun 28, 15:49 UTC | Jun 28, 19:44 UTC | 3h 55m |
| 2026-06-27 | SVA227 | - | Jun 27, 23:14 UTC | Jun 28, 13:34 UTC | 14h 20m |
| 2026-06-27 | SVA062 | - | Jun 27, 04:15 UTC | Jun 27, 21:15 UTC | 17h 0m |
| 2026-06-26 | SVA062 | - | Jun 26, 23:34 UTC | Jun 27, 21:15 UTC | 21h 40m |
| 2026-06-26 | SVA062 | - | Jun 26, 23:15 UTC | Jun 27, 21:15 UTC | 22h 0m |
| 2026-06-26 | SVA061 | - | Jun 26, 08:54 UTC | Jun 26, 18:54 UTC | 10h 0m |
| 2026-06-25 | SVA061 | - | Jun 25, 09:34 UTC | Jun 26, 09:30 UTC | 23h 55m |
| 2026-06-25 | SVA130 | - | Jun 25, 06:44 UTC | Jun 25, 10:15 UTC | 3h 30m |
| 2026-06-24 | SVA131 | - | Jun 24, 23:50 UTC | Jun 25, 03:44 UTC | 3h 55m |
| 2026-06-18 | SVA062 | - | Jun 18, 23:20 UTC | Jun 19, 08:54 UTC | 9h 34m |
| 2026-06-18 | SVA061 | - | Jun 18, 08:20 UTC | Jun 18, 18:50 UTC | 10h 30m |
| 2026-06-17 | SVA061 | - | Jun 17, 10:00 UTC | Jun 18, 09:30 UTC | 23h 30m |
| 2026-06-17 | SVA130 | - | Jun 17, 06:40 UTC | Jun 17, 10:05 UTC | 3h 25m |
| 2026-06-17 | SVA131 | - | Jun 17, 00:00 UTC | Jun 17, 04:10 UTC | 4h 10m |
| 2026-06-15 | SVA376 | - | Jun 15, 06:55 UTC | Jun 15, 10:15 UTC | 3h 20m |
| 2026-06-14 | SVA377 | - | Jun 14, 14:10 UTC | Jun 15, 04:04 UTC | 13h 54m |
| 2026-06-14 | SVA373 | - | Jun 14, 07:30 UTC | Jun 14, 11:35 UTC | 4h 5m |
| 2026-06-13 | SVA373 | - | Jun 13, 15:35 UTC | Jun 14, 11:35 UTC | 20h 1m |
| 2026-06-13 | SVA250 | BHX → JED | Jun 13, 13:50 UTC | Jun 14, 11:35 UTC | 21h 46m |
| 2026-06-13 | SVA253 | JED → BHX | Jun 13, 06:30 UTC | Jun 13, 11:35 UTC | 5h 5m |
| 2026-06-12 | SVA887 | PKX → JED | Jun 12, 18:20 UTC | Jun 12, 23:45 UTC | 5h 25m |
| 2026-06-12 | SVA886 | JED → ISB | Jun 12, 03:45 UTC | Jun 12, 12:25 UTC | 8h 40m |
| 2026-06-11 | SVA214 | AMS → JED | Jun 11, 14:20 UTC | Jun 11, 18:05 UTC | 3h 45m |
| 2026-06-10 | SVA215 | JED → AMS | Jun 10, 17:35 UTC | Jun 11, 11:50 UTC | 18h 15m |
| 2026-06-10 | SVA215 | JED → AMS | Jun 10, 15:35 UTC | Jun 11, 11:50 UTC | 20h 15m |
| 2026-06-10 | SVA215 | JED → AMS | Jun 10, 15:05 UTC | Jun 11, 11:50 UTC | 20h 45m |
| 2026-06-09 | SVA124 | MAN → JED | Jun 9, 14:10 UTC | Jun 10, 04:55 UTC | 14h 45m |
| 2026-06-09 | SVA123 | GVA → MAN | Jun 9, 07:50 UTC | Jun 9, 11:50 UTC | 4h 0m |
| 2026-06-08 | SVA123 | GVA → MAN | Jun 8, 09:35 UTC | Jun 9, 09:30 UTC | 23h 55m |
| 2026-06-07 | SVA5593 | - | Jun 7, 15:35 UTC | Jun 8, 10:10 UTC | 18h 35m |
| 2026-06-07 | SVA5593 | - | Jun 7, 14:25 UTC | Jun 8, 10:10 UTC | 19h 45m |
| 2026-06-06 | SVA215 | JED → AMS | Jun 6, 17:34 UTC | Jun 7, 12:00 UTC | 18h 25m |
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-AR12 page for operator, model, and routing details .