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
- 148
- Distinct callsigns
- 20
- Country
- SA
- Last broadcast
- 5h 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 | - | 14 | 2026-07-12 |
| SVA239 | - | 11 | 2026-07-03 |
| SVA256 | Saudi Arabian Airlines | 7 | 2026-07-17 |
| SVA238 | - | 7 | 2026-07-03 |
| SVA257 | Saudi Arabian Airlines | 6 | 2026-07-16 |
| SVA210 | - | 6 | 2026-07-12 |
| SVA708 | - | 5 | 2026-07-06 |
| SVA417 | - | 5 | 2026-06-21 |
| SVA313 | - | 5 | 2026-07-05 |
| SVA311 | - | 5 | 2026-07-04 |
| SVA389 | - | 4 | 2026-07-14 |
| SVA388 | - | 4 | 2026-07-14 |
| SVA588 | - | 3 | 2026-06-30 |
| SVA418 | Saudi Arabian Airlines | 3 | 2026-06-23 |
| SVA387 | - | 3 | 2026-07-11 |
| SVA383 | Saudi Arabian Airlines | 3 | 2026-06-29 |
| SVA312 | Saudi Arabian Airlines | 3 | 2026-06-24 |
| SVA258 | Saudi Arabian Airlines | 3 | 2026-06-03 |
| SVA9822 | - | 2 | 2026-06-16 |
| SVA9811 | - | 2 | 2026-05-06 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-17 | SVA256 | IST → JED | Jul 17, 12:50 UTC | Jul 17, 21:00 UTC | 8h 10m |
| 2026-07-16 | SVA257 | JED → IST | Jul 16, 15:19 UTC | Jul 17, 10:40 UTC | 19h 20m |
| 2026-07-16 | SVA236 | GVA → JED | Jul 16, 14:29 UTC | Jul 17, 10:40 UTC | 20h 10m |
| 2026-07-16 | SVA237 | - | Jul 16, 08:25 UTC | Jul 16, 12:20 UTC | 3h 55m |
| 2026-07-15 | SVA302 | - | Jul 15, 18:30 UTC | Jul 15, 18:40 UTC | 10m |
| 2026-07-14 | SVA303 | - | Jul 14, 21:20 UTC | Jul 15, 16:15 UTC | 18h 54m |
| 2026-07-14 | SVA388 | - | Jul 14, 21:00 UTC | Jul 15, 16:15 UTC | 19h 14m |
| 2026-07-14 | SVA389 | CAI → CAI | Jul 14, 19:20 UTC | Jul 14, 19:25 UTC | 5m |
| 2026-07-14 | SVA389 | - | Jul 14, 18:20 UTC | Jul 14, 18:40 UTC | 20m |
| 2026-07-13 | SVA388 | - | Jul 13, 20:30 UTC | Jul 14, 18:40 UTC | 22h 10m |
| 2026-07-13 | SVA389 | - | Jul 13, 18:10 UTC | Jul 13, 18:40 UTC | 30m |
| 2026-07-12 | SVA210 | - | Jul 12, 14:25 UTC | Jul 13, 06:25 UTC | 16h 0m |
| 2026-07-12 | SVA211 | - | Jul 12, 09:05 UTC | Jul 12, 11:30 UTC | 2h 25m |
| 2026-07-12 | SVA211 | - | Jul 12, 08:01 UTC | Jul 12, 09:00 UTC | 1h 0m |
| 2026-07-11 | SVA386 | - | Jul 11, 23:05 UTC | Jul 11, 23:20 UTC | 15m |
| 2026-07-11 | SVA387 | - | Jul 11, 15:30 UTC | Jul 11, 21:15 UTC | 5h 45m |
| 2026-07-11 | SVA305 | JED → CAI | Jul 11, 12:55 UTC | Jul 11, 13:10 UTC | 15m |
| 2026-07-10 | SVA256 | IST → JED | Jul 10, 13:20 UTC | Jul 11, 13:10 UTC | 23h 50m |
| 2026-07-10 | SVA256 | IST → JED | Jul 10, 12:45 UTC | Jul 10, 14:35 UTC | 1h 50m |
| 2026-07-10 | SVA257 | - | Jul 10, 08:15 UTC | Jul 10, 10:15 UTC | 2h 0m |
| 2026-07-07 | SVA210 | - | Jul 7, 15:20 UTC | Jul 8, 07:50 UTC | 16h 30m |
| 2026-07-07 | SVA211 | - | Jul 7, 10:05 UTC | Jul 7, 12:55 UTC | 2h 50m |
| 2026-07-06 | SVA708 | - | Jul 6, 04:35 UTC | Jul 6, 21:05 UTC | 16h 30m |
| 2026-07-05 | SVA708 | - | Jul 5, 18:35 UTC | Jul 6, 10:50 UTC | 16h 15m |
| 2026-07-05 | SVA313 | - | Jul 5, 15:35 UTC | Jul 5, 16:05 UTC | 30m |
| 2026-07-04 | SVA311 | - | Jul 4, 22:00 UTC | Jul 5, 06:45 UTC | 8h 45m |
| 2026-07-04 | SVA321 | - | Jul 4, 13:40 UTC | Jul 4, 19:40 UTC | 6h 0m |
| 2026-07-04 | SVA322 | - | Jul 4, 02:00 UTC | Jul 4, 11:20 UTC | 9h 20m |
| 2026-07-03 | SVA238 | - | Jul 3, 14:35 UTC | Jul 3, 23:50 UTC | 9h 15m |
| 2026-07-03 | SVA239 | - | Jul 3, 08:20 UTC | Jul 3, 12:40 UTC | 4h 20m |
| 2026-07-02 | SVA239 | - | Jul 2, 13:20 UTC | Jul 3, 12:40 UTC | 23h 20m |
| 2026-07-02 | SVA239 | - | Jul 2, 12:35 UTC | Jul 3, 11:15 UTC | 22h 40m |
| 2026-07-02 | SVA257 | - | Jul 2, 08:25 UTC | Jul 2, 10:20 UTC | 1h 55m |
| 2026-06-30 | SVA589 | DXB → JED | Jun 30, 13:50 UTC | Jun 30, 14:40 UTC | 50m |
| 2026-06-30 | SVA588 | - | Jun 30, 10:55 UTC | Jun 30, 12:05 UTC | 1h 10m |
| 2026-06-29 | SVA307 | - | Jun 29, 09:40 UTC | Jun 29, 10:00 UTC | 20m |
| 2026-06-29 | SVA382 | - | Jun 29, 04:00 UTC | Jun 29, 04:09 UTC | 10m |
| 2026-06-29 | SVA383 | JED → CAI | Jun 29, 01:39 UTC | Jun 29, 02:09 UTC | 30m |
| 2026-06-28 | SVA388 | - | Jun 28, 20:29 UTC | Jun 28, 20:45 UTC | 15m |
| 2026-06-28 | SVA389 | - | Jun 28, 18:10 UTC | Jun 28, 18:34 UTC | 25m |
| 2026-06-28 | SVA307 | - | Jun 28, 09:45 UTC | Jun 28, 10:04 UTC | 20m |
| 2026-06-25 | SVA302 | - | Jun 25, 18:04 UTC | Jun 25, 18:24 UTC | 20m |
| 2026-06-25 | SVA303 | JED → CAI | Jun 25, 15:44 UTC | Jun 25, 16:05 UTC | 20m |
| 2026-06-24 | SVA312 | CAI → RUH | Jun 24, 18:29 UTC | Jun 24, 18:39 UTC | 10m |
| 2026-06-24 | SVA313 | RUH → CAI | Jun 24, 09:05 UTC | Jun 24, 15:59 UTC | 6h 55m |
| 2026-06-24 | SVA311 | - | Jun 24, 06:20 UTC | Jun 24, 06:35 UTC | 15m |
| 2026-06-23 | SVA418 | CAI → RUH | Jun 23, 13:24 UTC | Jun 23, 19:39 UTC | 6h 15m |
| 2026-06-22 | SVA312 | CAI → RUH | Jun 22, 18:09 UTC | Jun 23, 11:10 UTC | 17h 0m |
| 2026-06-22 | SVA313 | RUH → CAI | Jun 22, 09:04 UTC | Jun 22, 16:05 UTC | 7h 0m |
| 2026-06-21 | SVA311 | - | Jun 21, 21:54 UTC | Jun 22, 06:49 UTC | 8h 55m |
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 .