sensors Mode-S transponder
7103D9
ICAO 24-bit transponder address · allocated to Saudi Arabia
Currently assigned to HZ-AQ24 · AIRBUS A-330-300
- Hex
- 7103D9
- Octal
- 34201731
- Decimal
- 7,406,553
- Country
- SA
- Tail
- HZ-AQ24
- Type
- A333
- Flights observed
- 90
- Distinct callsigns
- 20
- Country
- SA
- Last broadcast
- 8h ago
Last known position
Country allocation
The ICAO 24-bit address 7103D9 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 |
|---|---|---|---|
| SVA236 | Saudi Arabian Airlines | 6 | 2026-07-11 |
| SVA237 | - | 5 | 2026-07-11 |
| SVA596 | - | 4 | 2026-06-20 |
| SVA311 | - | 4 | 2026-07-03 |
| SVA264 | Saudi Arabian Airlines | 4 | 2026-06-04 |
| SVA597 | - | 3 | 2026-06-20 |
| SVA388 | - | 3 | 2026-06-27 |
| SVA263 | Saudi Arabian Airlines | 3 | 2026-06-04 |
| SVA257 | - | 3 | 2026-06-22 |
| SVA256 | Saudi Arabian Airlines | 3 | 2026-06-22 |
| SVA9829 | - | 2 | 2026-05-07 |
| SVA9817 | - | 2 | 2026-05-07 |
| SVA792 | Saudi Arabian Airlines | 2 | 2026-04-23 |
| SVA589 | Saudi Arabian Airlines | 2 | 2026-06-21 |
| SVA588 | - | 2 | 2026-06-21 |
| SVA389 | - | 2 | 2026-06-27 |
| SVA383 | Saudi Arabian Airlines | 2 | 2026-06-27 |
| SVA382 | - | 2 | 2026-06-27 |
| SVA3775 | Saudi Arabian Airlines | 2 | 2026-04-17 |
| SVA3774 | Saudi Arabian Airlines | 2 | 2026-04-17 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-17 | SVA775 | COK → RUH | Jul 17, 15:05 UTC | Jul 17, 18:40 UTC | 3h 35m |
| 2026-07-17 | SVA774 | RUH → COK | Jul 17, 09:20 UTC | Jul 17, 13:25 UTC | 4h 5m |
| 2026-07-15 | SVA128 | - | Jul 15, 15:40 UTC | Jul 15, 18:45 UTC | 3h 5m |
| 2026-07-15 | SVA129 | - | Jul 15, 09:55 UTC | Jul 15, 13:35 UTC | 3h 40m |
| 2026-07-13 | SVA230 | - | Jul 13, 17:30 UTC | Jul 13, 21:40 UTC | 4h 10m |
| 2026-07-13 | SVA231 | - | Jul 13, 11:45 UTC | Jul 13, 15:55 UTC | 4h 10m |
| 2026-07-11 | SVA236 | GVA → JED | Jul 11, 14:20 UTC | Jul 11, 17:55 UTC | 3h 35m |
| 2026-07-11 | SVA237 | - | Jul 11, 08:10 UTC | Jul 11, 12:10 UTC | 4h 0m |
| 2026-07-10 | SVA237 | - | Jul 10, 15:30 UTC | Jul 11, 12:10 UTC | 20h 40m |
| 2026-07-10 | SVA305 | JED → CAI | Jul 10, 13:00 UTC | Jul 10, 13:20 UTC | 20m |
| 2026-07-09 | SVA236 | GVA → JED | Jul 9, 16:20 UTC | Jul 10, 13:20 UTC | 21h 0m |
| 2026-07-09 | SVA236 | GVA → JED | Jul 9, 14:20 UTC | Jul 10, 13:20 UTC | 23h 0m |
| 2026-07-09 | SVA236 | GVA → JED | Jul 9, 14:05 UTC | Jul 9, 17:35 UTC | 3h 30m |
| 2026-07-09 | SVA237 | - | Jul 9, 09:20 UTC | Jul 9, 12:15 UTC | 2h 55m |
| 2026-07-05 | SVA302 | - | Jul 5, 18:20 UTC | Jul 6, 05:55 UTC | 11h 35m |
| 2026-07-05 | SVA701 | KHI → JED | Jul 5, 00:15 UTC | Jul 5, 16:05 UTC | 15h 50m |
| 2026-07-03 | SVA310 | - | Jul 3, 09:05 UTC | Jul 3, 09:20 UTC | 15m |
| 2026-07-03 | SVA311 | - | Jul 3, 06:20 UTC | Jul 3, 06:35 UTC | 15m |
| 2026-06-30 | SVA312 | - | Jun 30, 18:35 UTC | Jul 1, 07:55 UTC | 13h 20m |
| 2026-06-30 | SVA313 | RUH → CAI | Jun 30, 16:00 UTC | Jun 30, 16:15 UTC | 15m |
| 2026-06-27 | SVA388 | - | Jun 27, 20:44 UTC | Jun 27, 21:04 UTC | 20m |
| 2026-06-27 | SVA389 | - | Jun 27, 12:19 UTC | Jun 27, 19:00 UTC | 6h 40m |
| 2026-06-27 | SVA382 | - | Jun 27, 04:05 UTC | Jun 27, 10:05 UTC | 6h 0m |
| 2026-06-27 | SVA383 | JED → CAI | Jun 27, 01:49 UTC | Jun 27, 02:25 UTC | 35m |
| 2026-06-22 | SVA256 | IST → JED | Jun 22, 12:49 UTC | Jun 22, 14:34 UTC | 1h 45m |
| 2026-06-22 | SVA257 | - | Jun 22, 08:29 UTC | Jun 22, 10:30 UTC | 2h 0m |
| 2026-06-21 | SVA589 | DXB → JED | Jun 21, 13:50 UTC | Jun 21, 21:05 UTC | 7h 15m |
| 2026-06-21 | SVA588 | - | Jun 21, 10:29 UTC | Jun 21, 11:49 UTC | 1h 20m |
| 2026-06-20 | SVA388 | CAI → JED | Jun 20, 20:40 UTC | Jun 20, 20:49 UTC | 10m |
| 2026-06-20 | SVA597 | - | Jun 20, 09:39 UTC | Jun 20, 18:54 UTC | 9h 15m |
| 2026-06-20 | SVA596 | - | Jun 20, 06:45 UTC | Jun 20, 07:59 UTC | 1h 15m |
| 2026-06-18 | SVA596 | - | Jun 18, 06:40 UTC | Jun 18, 07:20 UTC | 40m |
| 2026-06-13 | SVA318 | CAI → MED | Jun 13, 06:50 UTC | Jun 13, 12:30 UTC | 5h 40m |
| 2026-06-13 | SVA335 | JED → CAI | Jun 13, 04:10 UTC | Jun 13, 04:50 UTC | 40m |
| 2026-06-11 | SVA596 | MED → DXB | Jun 11, 06:45 UTC | Jun 11, 10:35 UTC | 3h 50m |
| 2026-06-09 | SVA387 | JED → CAI | Jun 9, 20:50 UTC | Jun 9, 21:45 UTC | 55m |
| 2026-06-09 | SVA305 | JED → CAI | Jun 9, 13:00 UTC | Jun 9, 13:25 UTC | 25m |
| 2026-06-07 | SVA256 | IST → JED | Jun 7, 12:50 UTC | Jun 7, 14:35 UTC | 1h 45m |
| 2026-06-06 | SVA257 | JED → IST | Jun 6, 16:20 UTC | Jun 7, 10:30 UTC | 18h 10m |
| 2026-06-06 | SVA236 | GVA → JED | Jun 6, 14:40 UTC | Jun 7, 10:30 UTC | 19h 50m |
| 2026-06-05 | SVA237 | JED → GVA | Jun 5, 18:30 UTC | Jun 6, 12:49 UTC | 18h 20m |
| 2026-06-05 | SVA313 | RUH → CAI | Jun 5, 04:50 UTC | Jun 5, 16:00 UTC | 11h 10m |
| 2026-06-04 | SVA264 | IST → RUH | Jun 4, 15:20 UTC | Jun 5, 10:50 UTC | 19h 30m |
| 2026-06-04 | SVA264 | IST → RUH | Jun 4, 13:45 UTC | Jun 5, 10:50 UTC | 21h 5m |
| 2026-06-04 | SVA263 | RUH → IST | Jun 4, 09:50 UTC | Jun 4, 11:45 UTC | 1h 55m |
| 2026-06-03 | SVA311 | RUH → CAI | Jun 3, 06:30 UTC | Jun 3, 06:55 UTC | 25m |
| 2026-06-02 | SVA311 | RUH → CAI | Jun 2, 09:05 UTC | Jun 3, 06:55 UTC | 21h 50m |
| 2026-06-01 | SVA311 | RUH → CAI | Jun 1, 12:25 UTC | Jun 2, 06:45 UTC | 18h 20m |
| 2026-06-01 | SVA382 | CAI → JED | Jun 1, 04:30 UTC | Jun 1, 12:30 UTC | 8h 0m |
| 2026-06-01 | SVA383 | JED → CAI | Jun 1, 02:25 UTC | Jun 1, 02:45 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-AQ24 page for operator, model, and routing details .