sensors Mode-S transponder
7100B5
ICAO 24-bit transponder address · allocated to Saudi Arabia
Currently assigned to HZ-AQ11 · AIRBUS A-330-300
- Hex
- 7100B5
- Octal
- 34200265
- Decimal
- 7,405,749
- Country
- SA
- Tail
- HZ-AQ11
- Type
- A333
- Flights observed
- 109
- Distinct callsigns
- 20
- Country
- SA
- Last broadcast
- 6h ago
Last known position
Country allocation
The ICAO 24-bit address 7100B5 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 |
|---|---|---|---|
| SVA257 | Saudi Arabian Airlines | 7 | 2026-06-05 |
| SVA301 | Saudi Arabian Airlines | 6 | 2026-06-28 |
| SVA309 | - | 5 | 2026-06-21 |
| SVA708 | - | 4 | 2026-07-08 |
| SVA322 | - | 4 | 2026-07-17 |
| SVA307 | - | 4 | 2026-07-10 |
| SVA256 | Saudi Arabian Airlines | 4 | 2026-06-06 |
| SVA589 | Saudi Arabian Airlines | 3 | 2026-07-13 |
| SVA588 | - | 3 | 2026-07-13 |
| SVA389 | Saudi Arabian Airlines | 3 | 2026-06-26 |
| SVA387 | - | 3 | 2026-07-12 |
| SVA323 | - | 3 | 2026-07-04 |
| SVA313 | Saudi Arabian Airlines | 3 | 2026-07-01 |
| SVA311 | - | 3 | 2026-07-06 |
| SVA792 | Saudi Arabian Airlines | 2 | 2026-06-02 |
| SVA597 | - | 2 | 2026-07-18 |
| SVA596 | - | 2 | 2026-07-17 |
| SVA388 | Saudi Arabian Airlines | 2 | 2026-06-22 |
| SVA321 | - | 2 | 2026-07-17 |
| SVA312 | Saudi Arabian Airlines | 2 | 2026-06-11 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-18 | SVA597 | - | Jul 18, 10:15 UTC | Jul 18, 10:35 UTC | 20m |
| 2026-07-17 | SVA596 | - | Jul 17, 22:10 UTC | Jul 18, 07:50 UTC | 9h 41m |
| 2026-07-17 | SVA321 | - | Jul 17, 19:20 UTC | Jul 17, 19:35 UTC | 15m |
| 2026-07-17 | SVA322 | - | Jul 17, 02:25 UTC | Jul 17, 11:30 UTC | 9h 5m |
| 2026-07-16 | SVA555 | DXB → RUH | Jul 16, 14:20 UTC | Jul 17, 00:04 UTC | 9h 45m |
| 2026-07-16 | SVA554 | - | Jul 16, 11:45 UTC | Jul 16, 13:05 UTC | 1h 20m |
| 2026-07-13 | SVA589 | DXB → JED | Jul 13, 13:45 UTC | Jul 13, 14:35 UTC | 50m |
| 2026-07-13 | SVA588 | - | Jul 13, 00:35 UTC | Jul 13, 12:05 UTC | 11h 30m |
| 2026-07-12 | SVA387 | - | Jul 12, 22:20 UTC | Jul 12, 23:00 UTC | 40m |
| 2026-07-10 | SVA307 | - | Jul 10, 10:00 UTC | Jul 10, 10:15 UTC | 15m |
| 2026-07-09 | SVA597 | - | Jul 9, 09:50 UTC | Jul 9, 10:25 UTC | 35m |
| 2026-07-08 | SVA596 | - | Jul 8, 18:40 UTC | Jul 9, 08:05 UTC | 13h 25m |
| 2026-07-08 | SVA708 | - | Jul 8, 04:40 UTC | Jul 8, 16:15 UTC | 11h 35m |
| 2026-07-07 | SVA708 | - | Jul 7, 09:20 UTC | Jul 8, 05:40 UTC | 20h 20m |
| 2026-07-06 | SVA311 | - | Jul 6, 22:25 UTC | Jul 7, 06:35 UTC | 8h 10m |
| 2026-07-06 | SVA321 | - | Jul 6, 19:30 UTC | Jul 6, 19:50 UTC | 20m |
| 2026-07-06 | SVA322 | - | Jul 6, 02:10 UTC | Jul 6, 11:25 UTC | 9h 15m |
| 2026-07-05 | SVA418 | - | Jul 5, 15:25 UTC | Jul 5, 23:55 UTC | 8h 30m |
| 2026-07-05 | SVA417 | - | Jul 5, 02:20 UTC | Jul 5, 11:10 UTC | 8h 50m |
| 2026-07-04 | SVA323 | - | Jul 4, 23:35 UTC | Jul 4, 23:55 UTC | 20m |
| 2026-07-03 | SVA210 | MXP → RUH | Jul 3, 14:25 UTC | Jul 3, 17:10 UTC | 2h 45m |
| 2026-07-02 | SVA211 | - | Jul 2, 18:55 UTC | Jul 3, 11:45 UTC | 16h 50m |
| 2026-07-02 | SVA708 | - | Jul 2, 04:30 UTC | Jul 2, 16:30 UTC | 12h 0m |
| 2026-07-01 | SVA708 | - | Jul 1, 18:35 UTC | Jul 2, 16:30 UTC | 21h 55m |
| 2026-07-01 | SVA313 | RUH → CAI | Jul 1, 16:00 UTC | Jul 1, 16:20 UTC | 20m |
| 2026-06-30 | SVA236 | GVA → JED | Jun 30, 14:15 UTC | Jun 30, 17:30 UTC | 3h 15m |
| 2026-06-30 | SVA237 | - | Jun 30, 08:50 UTC | Jun 30, 12:00 UTC | 3h 10m |
| 2026-06-29 | SVA322 | CAI → RUH | Jun 29, 02:05 UTC | Jun 29, 02:25 UTC | 20m |
| 2026-06-28 | SVA323 | RUH → CAI | Jun 28, 23:34 UTC | Jun 29, 00:14 UTC | 40m |
| 2026-06-28 | SVA301 | JED → CAI | Jun 28, 07:34 UTC | Jun 28, 08:05 UTC | 30m |
| 2026-06-27 | SVA318 | - | Jun 27, 06:50 UTC | Jun 27, 12:29 UTC | 5h 40m |
| 2026-06-26 | SVA335 | - | Jun 26, 20:40 UTC | Jun 27, 04:39 UTC | 8h 0m |
| 2026-06-26 | SVA389 | JED → CAI | Jun 26, 12:19 UTC | Jun 26, 19:00 UTC | 6h 40m |
| 2026-06-26 | SVA307 | - | Jun 26, 09:50 UTC | Jun 26, 10:10 UTC | 20m |
| 2026-06-25 | SVA322 | CAI → RUH | Jun 25, 02:14 UTC | Jun 25, 02:25 UTC | 10m |
| 2026-06-24 | SVA323 | RUH → CAI | Jun 24, 23:34 UTC | Jun 25, 00:09 UTC | 35m |
| 2026-06-22 | SVA388 | CAI → JED | Jun 22, 20:39 UTC | Jun 22, 20:49 UTC | 10m |
| 2026-06-22 | SVA389 | JED → CAI | Jun 22, 12:19 UTC | Jun 22, 18:40 UTC | 6h 20m |
| 2026-06-22 | SVA307 | JED → CAI | Jun 22, 09:45 UTC | Jun 22, 10:00 UTC | 15m |
| 2026-06-21 | SVA309 | - | Jun 21, 23:34 UTC | Jun 21, 23:50 UTC | 15m |
| 2026-06-21 | SVA300 | CAI → JED | Jun 21, 10:04 UTC | Jun 21, 10:14 UTC | 10m |
| 2026-06-21 | SVA301 | JED → CAI | Jun 21, 07:45 UTC | Jun 21, 07:59 UTC | 15m |
| 2026-06-20 | SVA236 | GVA → JED | Jun 20, 14:05 UTC | Jun 20, 17:19 UTC | 3h 15m |
| 2026-06-20 | SVA237 | JED → GVA | Jun 20, 09:19 UTC | Jun 20, 12:04 UTC | 2h 45m |
| 2026-06-19 | SVA386 | - | Jun 19, 23:34 UTC | Jun 19, 23:44 UTC | 10m |
| 2026-06-19 | SVA387 | JED → CAI | Jun 19, 20:49 UTC | Jun 19, 21:19 UTC | 30m |
| 2026-06-19 | SVA387 | JED → CAI | Jun 19, 01:50 UTC | Jun 19, 21:19 UTC | 19h 30m |
| 2026-06-18 | SVA309 | - | Jun 18, 23:10 UTC | Jun 18, 23:35 UTC | 25m |
| 2026-06-17 | SVA309 | - | Jun 17, 12:30 UTC | Jun 17, 23:30 UTC | 11h 0m |
| 2026-06-17 | SVA307 | JED → CAI | Jun 17, 01:35 UTC | Jun 17, 10:10 UTC | 8h 35m |
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-AQ11 page for operator, model, and routing details .