sensors Mode-S transponder
7100BD
ICAO 24-bit transponder address · allocated to Saudi Arabia
Currently assigned to HZ-AQ19 · AIRBUS A-330-300
- Hex
- 7100BD
- Octal
- 34200275
- Decimal
- 7,405,757
- Country
- SA
- Tail
- HZ-AQ19
- Type
- A333
- Flights observed
- 65
- Distinct callsigns
- 20
- Country
- SA
- Last broadcast
- 20h ago
Last known position
Country allocation
The ICAO 24-bit address 7100BD 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 |
|---|---|---|---|
| SVA387 | - | 4 | 2026-06-27 |
| SVA236 | Saudi Arabian Airlines | 4 | 2026-06-02 |
| SVA211 | - | 4 | 2026-06-16 |
| SVA313 | Saudi Arabian Airlines | 3 | 2026-06-19 |
| SVA305 | Saudi Arabian Airlines | 3 | 2026-06-07 |
| SVA237 | Saudi Arabian Airlines | 3 | 2026-06-02 |
| SVA9649 | - | 2 | 2026-05-19 |
| SVA708 | - | 2 | 2026-06-20 |
| SVA589 | Saudi Arabian Airlines | 2 | 2026-06-28 |
| SVA588 | - | 2 | 2026-06-27 |
| SVA5549 | - | 2 | 2026-06-05 |
| SVA323 | Saudi Arabian Airlines | 2 | 2026-06-21 |
| SVA321 | Saudi Arabian Airlines | 2 | 2026-05-27 |
| SVA311 | Saudi Arabian Airlines | 2 | 2026-05-28 |
| SVA210 | Saudi Arabian Airlines | 2 | 2026-06-16 |
| SVA128 | - | 2 | 2026-06-26 |
| SVA9827 | - | 1 | 2026-05-20 |
| SVA9822 | - | 1 | 2026-06-01 |
| SVA9756 | - | 1 | 2026-05-22 |
| SVA9660 | - | 1 | 2026-06-05 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-28 | SVA589 | DXB → JED | Jun 28, 13:49 UTC | Jun 28, 14:39 UTC | 50m |
| 2026-06-27 | SVA588 | - | Jun 27, 23:10 UTC | Jun 28, 12:05 UTC | 12h 55m |
| 2026-06-27 | SVA387 | - | Jun 27, 20:39 UTC | Jun 27, 21:04 UTC | 25m |
| 2026-06-26 | SVA128 | - | Jun 26, 17:19 UTC | Jun 27, 13:09 UTC | 19h 50m |
| 2026-06-26 | SVA128 | - | Jun 26, 15:45 UTC | Jun 27, 13:09 UTC | 21h 25m |
| 2026-06-26 | SVA129 | - | Jun 26, 02:20 UTC | Jun 26, 13:15 UTC | 10h 55m |
| 2026-06-25 | SVA256 | IST → JED | Jun 25, 12:50 UTC | Jun 26, 00:15 UTC | 11h 25m |
| 2026-06-25 | SVA257 | - | Jun 25, 08:24 UTC | Jun 25, 10:35 UTC | 2h 10m |
| 2026-06-23 | SVA387 | JED → CAI | Jun 23, 20:44 UTC | Jun 23, 21:10 UTC | 25m |
| 2026-06-22 | SVA386 | - | Jun 22, 23:20 UTC | Jun 23, 13:15 UTC | 13h 55m |
| 2026-06-22 | SVA387 | JED → CAI | Jun 22, 02:10 UTC | Jun 22, 21:14 UTC | 19h 5m |
| 2026-06-21 | SVA323 | RUH → CAI | Jun 21, 23:24 UTC | Jun 21, 23:44 UTC | 20m |
| 2026-06-20 | SVA312 | CAI → RUH | Jun 20, 18:14 UTC | Jun 20, 18:34 UTC | 20m |
| 2026-06-20 | SVA708 | - | Jun 20, 04:20 UTC | Jun 20, 16:29 UTC | 12h 10m |
| 2026-06-19 | SVA708 | - | Jun 19, 18:14 UTC | Jun 20, 10:55 UTC | 16h 40m |
| 2026-06-19 | SVA313 | RUH → CAI | Jun 19, 02:04 UTC | Jun 19, 15:59 UTC | 13h 55m |
| 2026-06-18 | SVA323 | RUH → CAI | Jun 18, 23:35 UTC | Jun 18, 23:55 UTC | 20m |
| 2026-06-16 | SVA210 | MXP → RUH | Jun 16, 14:25 UTC | Jun 16, 17:40 UTC | 3h 15m |
| 2026-06-16 | SVA211 | - | Jun 16, 09:20 UTC | Jun 16, 11:55 UTC | 2h 35m |
| 2026-06-15 | SVA783 | COK → JED | Jun 15, 06:04 UTC | Jun 15, 07:29 UTC | 1h 25m |
| 2026-06-15 | SVA784 | JED → COK | Jun 15, 00:05 UTC | Jun 15, 04:04 UTC | 4h 0m |
| 2026-06-12 | SVA307 | JED → CAI | Jun 12, 09:40 UTC | Jun 12, 09:55 UTC | 15m |
| 2026-06-11 | SVA366 | TUN → JED | Jun 11, 11:10 UTC | Jun 11, 21:30 UTC | 10h 20m |
| 2026-06-11 | SVA5535 | - | Jun 11, 05:30 UTC | Jun 11, 08:30 UTC | 3h 0m |
| 2026-06-07 | SVA305 | JED → CAI | Jun 7, 13:10 UTC | Jun 7, 13:25 UTC | 15m |
| 2026-06-05 | SVA9660 | - | Jun 5, 09:55 UTC | Jun 5, 11:30 UTC | 1h 35m |
| 2026-06-05 | SVA5549 | - | Jun 5, 01:45 UTC | Jun 5, 04:40 UTC | 2h 55m |
| 2026-06-04 | SVA5549 | - | Jun 4, 03:20 UTC | Jun 5, 03:15 UTC | 23h 55m |
| 2026-06-03 | SVA9654 | - | Jun 3, 09:20 UTC | Jun 4, 04:00 UTC | 18h 40m |
| 2026-06-03 | SVA5547 | - | Jun 3, 03:30 UTC | Jun 4, 03:15 UTC | 23h 45m |
| 2026-06-02 | SVA236 | GVA → JED | Jun 2, 15:20 UTC | Jun 3, 10:50 UTC | 19h 30m |
| 2026-06-02 | SVA236 | GVA → JED | Jun 2, 14:20 UTC | Jun 3, 10:50 UTC | 20h 30m |
| 2026-06-02 | SVA237 | JED → GVA | Jun 2, 01:45 UTC | Jun 2, 12:20 UTC | 10h 35m |
| 2026-06-01 | SVA9822 | - | Jun 1, 06:30 UTC | Jun 1, 08:15 UTC | 1h 45m |
| 2026-05-31 | SVA210 | MXP → RUH | May 31, 15:00 UTC | Jun 1, 04:55 UTC | 13h 55m |
| 2026-05-31 | SVA211 | JED → MXP | May 31, 09:30 UTC | May 31, 12:40 UTC | 3h 10m |
| 2026-05-30 | SVA211 | JED → MXP | May 30, 15:20 UTC | May 31, 12:40 UTC | 21h 20m |
| 2026-05-30 | SVA211 | JED → MXP | May 30, 14:20 UTC | May 31, 12:40 UTC | 22h 20m |
| 2026-05-29 | SVA263 | RUH → IST | May 29, 18:30 UTC | May 30, 12:25 UTC | 17h 55m |
| 2026-05-29 | SVA313 | RUH → CAI | May 29, 15:40 UTC | May 29, 16:10 UTC | 30m |
| 2026-05-28 | SVA311 | RUH → CAI | May 28, 18:10 UTC | May 29, 06:40 UTC | 12h 30m |
| 2026-05-28 | SVA313 | RUH → CAI | May 28, 09:15 UTC | May 28, 16:15 UTC | 7h 0m |
| 2026-05-27 | SVA311 | RUH → CAI | May 27, 21:40 UTC | May 28, 06:55 UTC | 9h 15m |
| 2026-05-27 | SVA321 | RUH → CAI | May 27, 19:30 UTC | May 27, 19:45 UTC | 15m |
| 2026-05-24 | SVA236 | GVA → JED | May 24, 14:30 UTC | May 24, 18:00 UTC | 3h 30m |
| 2026-05-24 | SVA237 | JED → GVA | May 24, 09:35 UTC | May 24, 12:20 UTC | 2h 45m |
| 2026-05-22 | SVA387 | JED → CAI | May 22, 20:50 UTC | May 22, 21:15 UTC | 25m |
| 2026-05-22 | SVA9756 | - | May 22, 07:25 UTC | May 22, 12:40 UTC | 5h 15m |
| 2026-05-21 | SVA305 | JED → CAI | May 21, 13:05 UTC | May 21, 23:20 UTC | 10h 15m |
| 2026-05-21 | SVA3228 | IST → MED | May 21, 01:20 UTC | May 21, 23:20 UTC | 22h 0m |
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-AQ19 page for operator, model, and routing details .