sensors Mode-S transponder
7103DD
ICAO 24-bit transponder address · allocated to Saudi Arabia
Currently assigned to HZ-AQ28 · AIRBUS A-330-300
- Hex
- 7103DD
- Octal
- 34201735
- Decimal
- 7,406,557
- Country
- SA
- Tail
- HZ-AQ28
- Type
- A333
- Flights observed
- 68
- Distinct callsigns
- 20
- Country
- SA
- Last broadcast
- 3h ago
Last known position
Country allocation
The ICAO 24-bit address 7103DD 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 |
|---|---|---|---|
| SVA211 | Saudi Arabian Airlines | 11 | 2026-05-03 |
| SVA239 | Saudi Arabian Airlines | 8 | 2026-05-22 |
| SVA238 | Saudi Arabian Airlines | 6 | 2026-05-22 |
| SVA210 | Saudi Arabian Airlines | 4 | 2026-05-03 |
| SVA708 | Saudi Arabian Airlines | 3 | 2026-05-23 |
| SVA417 | Saudi Arabian Airlines | 3 | 2026-06-01 |
| SVA9811 | - | 2 | 2026-05-06 |
| SVA588 | Saudi Arabian Airlines | 2 | 2026-05-07 |
| SVA383 | Saudi Arabian Airlines | 2 | 2026-06-02 |
| SVA3776 | Saudi Arabian Airlines | 2 | 2026-04-23 |
| SVA313 | Saudi Arabian Airlines | 2 | 2026-05-18 |
| SVA258 | Saudi Arabian Airlines | 2 | 2026-04-26 |
| SVA257 | Saudi Arabian Airlines | 2 | 2026-05-24 |
| SVA256 | Saudi Arabian Airlines | 2 | 2026-05-24 |
| SVA9807 | - | 1 | 2026-05-06 |
| SVA9651 | - | 1 | 2026-05-14 |
| SVA9609 | - | 1 | 2026-05-10 |
| SVA796 | Saudi Arabian Airlines | 1 | 2026-04-17 |
| SVA701 | - | 1 | 2026-04-14 |
| SVA589 | Saudi Arabian Airlines | 1 | 2026-04-27 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-02 | SVA380 | CAI → MED | Jun 2, 19:00 UTC | Jun 2, 19:15 UTC | 15m |
| 2026-06-02 | SVA381 | MED → CAI | Jun 2, 16:35 UTC | Jun 2, 17:10 UTC | 35m |
| 2026-06-02 | SVA383 | JED → CAI | Jun 2, 02:15 UTC | Jun 2, 02:30 UTC | 15m |
| 2026-06-01 | SVA418 | CAI → RUH | Jun 1, 13:35 UTC | Jun 1, 13:45 UTC | 10m |
| 2026-06-01 | SVA417 | RUH → CAI | Jun 1, 11:05 UTC | Jun 1, 11:30 UTC | 25m |
| 2026-05-27 | SVA383 | JED → CAI | May 27, 01:39 UTC | May 27, 01:59 UTC | 20m |
| 2026-05-24 | SVA256 | IST → JED | May 24, 12:50 UTC | May 24, 14:35 UTC | 1h 45m |
| 2026-05-24 | SVA257 | JED → IST | May 24, 08:55 UTC | May 24, 10:40 UTC | 1h 45m |
| 2026-05-23 | SVA708 | RUH → KHI | May 23, 04:25 UTC | May 23, 19:40 UTC | 15h 15m |
| 2026-05-22 | SVA238 | GVA → RUH | May 22, 15:20 UTC | May 23, 11:00 UTC | 19h 39m |
| 2026-05-22 | SVA238 | GVA → RUH | May 22, 14:15 UTC | May 23, 11:00 UTC | 20h 44m |
| 2026-05-22 | SVA239 | RUH → GVA | May 22, 08:45 UTC | May 22, 12:25 UTC | 3h 40m |
| 2026-05-21 | SVA417 | RUH → CAI | May 21, 11:05 UTC | May 21, 11:30 UTC | 25m |
| 2026-05-20 | SVA5644 | - | May 20, 07:15 UTC | May 20, 07:25 UTC | 10m |
| 2026-05-19 | SVA5634 | - | May 19, 14:30 UTC | May 19, 14:40 UTC | 10m |
| 2026-05-18 | SVA417 | RUH → CAI | May 18, 18:35 UTC | May 19, 11:25 UTC | 16h 50m |
| 2026-05-18 | SVA313 | RUH → CAI | May 18, 09:40 UTC | May 18, 16:15 UTC | 6h 35m |
| 2026-05-18 | SVA311 | RUH → CAI | May 18, 06:35 UTC | May 18, 07:00 UTC | 25m |
| 2026-05-14 | SVA5548 | - | May 14, 05:05 UTC | May 14, 06:15 UTC | 1h 10m |
| 2026-05-14 | SVA9651 | - | May 14, 01:25 UTC | May 14, 03:20 UTC | 1h 55m |
| 2026-05-10 | SVA5542 | - | May 10, 08:50 UTC | May 10, 11:00 UTC | 2h 10m |
| 2026-05-10 | SVA9609 | - | May 10, 05:00 UTC | May 10, 06:50 UTC | 1h 50m |
| 2026-05-08 | SVA312 | CAI → RUH | May 8, 18:10 UTC | May 8, 18:25 UTC | 15m |
| 2026-05-08 | SVA313 | RUH → CAI | May 8, 06:45 UTC | May 8, 16:15 UTC | 9h 30m |
| 2026-05-07 | SVA588 | JED → DXB | May 7, 10:30 UTC | May 8, 07:14 UTC | 20h 44m |
| 2026-05-06 | SVA9811 | - | May 6, 16:10 UTC | May 7, 11:00 UTC | 18h 50m |
| 2026-05-06 | SVA9811 | - | May 6, 13:20 UTC | May 7, 11:00 UTC | 21h 40m |
| 2026-05-06 | SVA9807 | - | May 6, 12:05 UTC | May 7, 11:00 UTC | 22h 55m |
| 2026-05-03 | SVA210 | MXP → RUH | May 3, 14:35 UTC | May 4, 05:50 UTC | 15h 15m |
| 2026-05-03 | SVA211 | JED → MXP | May 3, 09:40 UTC | May 3, 12:20 UTC | 2h 40m |
| 2026-05-02 | SVA211 | JED → MXP | May 2, 15:20 UTC | May 3, 12:20 UTC | 20h 59m |
| 2026-05-02 | SVA211 | JED → MXP | May 2, 14:30 UTC | May 3, 12:20 UTC | 21h 49m |
| 2026-05-01 | SVA211 | JED → MXP | May 1, 17:35 UTC | May 2, 11:55 UTC | 18h 20m |
| 2026-05-01 | SVA211 | JED → MXP | May 1, 15:20 UTC | May 2, 11:55 UTC | 20h 35m |
| 2026-05-01 | SVA210 | MXP → RUH | May 1, 15:00 UTC | May 2, 11:55 UTC | 20h 55m |
| 2026-04-30 | SVA211 | JED → MXP | Apr 30, 17:25 UTC | May 1, 13:05 UTC | 19h 40m |
| 2026-04-30 | SVA211 | JED → MXP | Apr 30, 15:20 UTC | May 1, 13:05 UTC | 21h 45m |
| 2026-04-30 | SVA210 | MXP → RUH | Apr 30, 14:30 UTC | May 1, 13:05 UTC | 22h 35m |
| 2026-04-30 | SVA211 | JED → MXP | Apr 30, 09:00 UTC | Apr 30, 12:15 UTC | 3h 15m |
| 2026-04-27 | SVA589 | DXB → JED | Apr 27, 14:00 UTC | Apr 27, 15:10 UTC | 1h 10m |
| 2026-04-27 | SVA588 | JED → DXB | Apr 27, 10:45 UTC | Apr 27, 11:45 UTC | 1h 0m |
| 2026-04-26 | SVA258 | IST → MED | Apr 26, 11:20 UTC | Apr 27, 11:15 UTC | 23h 55m |
| 2026-04-26 | SVA258 | IST → MED | Apr 26, 11:10 UTC | Apr 26, 12:40 UTC | 1h 30m |
| 2026-04-25 | SVA259 | MED → IST | Apr 25, 18:40 UTC | Apr 26, 08:55 UTC | 14h 15m |
| 2026-04-25 | SVA708 | RUH → KHI | Apr 25, 04:50 UTC | Apr 25, 16:15 UTC | 11h 25m |
| 2026-04-24 | SVA708 | RUH → KHI | Apr 24, 17:20 UTC | Apr 25, 16:15 UTC | 22h 55m |
| 2026-04-24 | SVA238 | GVA → RUH | Apr 24, 15:20 UTC | Apr 25, 10:40 UTC | 19h 20m |
| 2026-04-24 | SVA238 | GVA → RUH | Apr 24, 14:15 UTC | Apr 25, 10:40 UTC | 20h 25m |
| 2026-04-24 | SVA239 | RUH → GVA | Apr 24, 08:30 UTC | Apr 24, 12:35 UTC | 4h 5m |
| 2026-04-23 | SVA239 | RUH → GVA | Apr 23, 15:45 UTC | Apr 24, 12:35 UTC | 20h 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-AQ28 page for operator, model, and routing details .