sensors Mode-S transponder
7100BC
ICAO 24-bit transponder address · allocated to Saudi Arabia
Currently assigned to HZ-AQ18 · AIRBUS A-330-300
- Hex
- 7100BC
- Octal
- 34200274
- Decimal
- 7,405,756
- Country
- SA
- Tail
- HZ-AQ18
- Type
- A333
- Flights observed
- 102
- Distinct callsigns
- 20
- Country
- SA
- Last broadcast
- 42m ago
Last known position
Country allocation
The ICAO 24-bit address 7100BC 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 |
|---|---|---|---|
| SVA321 | - | 7 | 2026-06-28 |
| SVA708 | - | 5 | 2026-07-13 |
| SVA311 | Saudi Arabian Airlines | 5 | 2026-05-30 |
| SVA257 | - | 5 | 2026-06-21 |
| SVA256 | Saudi Arabian Airlines | 4 | 2026-06-21 |
| SVA589 | Saudi Arabian Airlines | 3 | 2026-05-19 |
| SVA417 | Saudi Arabian Airlines | 3 | 2026-05-25 |
| SVA387 | - | 3 | 2026-06-30 |
| SVA312 | Saudi Arabian Airlines | 3 | 2026-05-26 |
| SVA305 | Saudi Arabian Airlines | 3 | 2026-07-13 |
| SVA259 | Saudi Arabian Airlines | 3 | 2026-04-30 |
| SVA238 | - | 3 | 2026-07-06 |
| SVA128 | - | 3 | 2026-06-29 |
| SVA9829 | - | 2 | 2026-04-25 |
| SVA9810 | - | 2 | 2026-06-18 |
| SVA709 | - | 2 | 2026-07-14 |
| SVA700 | - | 2 | 2026-07-12 |
| SVA389 | Saudi Arabian Airlines | 2 | 2026-06-13 |
| SVA386 | - | 2 | 2026-06-30 |
| SVA3230 | Saudi Arabian Airlines | 2 | 2026-04-26 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | SVA709 | - | Jul 14, 10:20 UTC | Jul 14, 11:00 UTC | 40m |
| 2026-07-13 | SVA708 | - | Jul 13, 15:55 UTC | Jul 14, 06:05 UTC | 14h 10m |
| 2026-07-13 | SVA305 | JED → CAI | Jul 13, 13:05 UTC | Jul 13, 13:20 UTC | 15m |
| 2026-07-12 | SVA305 | JED → CAI | Jul 12, 15:40 UTC | Jul 13, 13:20 UTC | 21h 40m |
| 2026-07-12 | SVA700 | - | Jul 12, 00:10 UTC | Jul 12, 13:15 UTC | 13h 5m |
| 2026-07-09 | SVA559 | - | Jul 9, 12:30 UTC | Jul 9, 13:20 UTC | 50m |
| 2026-07-08 | SVA212 | - | Jul 8, 15:35 UTC | Jul 9, 10:45 UTC | 19h 10m |
| 2026-07-08 | SVA213 | - | Jul 8, 09:25 UTC | Jul 8, 13:05 UTC | 3h 40m |
| 2026-07-06 | SVA238 | - | Jul 6, 14:25 UTC | Jul 6, 18:15 UTC | 3h 50m |
| 2026-07-06 | SVA239 | - | Jul 6, 08:25 UTC | Jul 6, 12:15 UTC | 3h 50m |
| 2026-06-30 | SVA386 | - | Jun 30, 23:25 UTC | Jun 30, 23:35 UTC | 10m |
| 2026-06-30 | SVA387 | - | Jun 30, 20:35 UTC | Jun 30, 21:10 UTC | 35m |
| 2026-06-29 | SVA128 | - | Jun 29, 17:05 UTC | Jun 30, 13:15 UTC | 20h 10m |
| 2026-06-29 | SVA128 | - | Jun 29, 15:39 UTC | Jun 30, 13:00 UTC | 21h 21m |
| 2026-06-28 | SVA129 | - | Jun 28, 21:59 UTC | Jun 29, 13:30 UTC | 15h 30m |
| 2026-06-28 | SVA321 | - | Jun 28, 13:29 UTC | Jun 28, 19:44 UTC | 6h 15m |
| 2026-06-28 | SVA308 | - | Jun 28, 01:44 UTC | Jun 28, 10:50 UTC | 9h 5m |
| 2026-06-27 | SVA322 | CAI → RUH | Jun 27, 01:59 UTC | Jun 27, 02:29 UTC | 30m |
| 2026-06-26 | SVA238 | GVA → RUH | Jun 26, 14:15 UTC | Jun 27, 00:14 UTC | 10h 0m |
| 2026-06-26 | SVA239 | - | Jun 26, 08:15 UTC | Jun 26, 11:45 UTC | 3h 30m |
| 2026-06-24 | SVA128 | - | Jun 24, 16:05 UTC | Jun 25, 04:20 UTC | 12h 15m |
| 2026-06-24 | SVA129 | - | Jun 24, 09:39 UTC | Jun 24, 13:14 UTC | 3h 35m |
| 2026-06-23 | SVA322 | CAI → RUH | Jun 23, 02:40 UTC | Jun 23, 23:55 UTC | 21h 15m |
| 2026-06-23 | SVA323 | RUH → CAI | Jun 23, 00:09 UTC | Jun 23, 00:39 UTC | 30m |
| 2026-06-21 | SVA256 | IST → JED | Jun 21, 13:09 UTC | Jun 21, 14:59 UTC | 1h 50m |
| 2026-06-21 | SVA257 | - | Jun 21, 08:20 UTC | Jun 21, 10:14 UTC | 1h 55m |
| 2026-06-20 | SVA386 | - | Jun 20, 23:04 UTC | Jun 20, 23:19 UTC | 15m |
| 2026-06-20 | SVA387 | JED → CAI | Jun 20, 20:40 UTC | Jun 20, 21:19 UTC | 40m |
| 2026-06-20 | SVA318 | - | Jun 20, 06:49 UTC | Jun 20, 12:34 UTC | 5h 45m |
| 2026-06-19 | SVA335 | JED → CAI | Jun 19, 15:24 UTC | Jun 20, 04:44 UTC | 13h 20m |
| 2026-06-18 | SVA9810 | - | Jun 18, 20:50 UTC | Jun 19, 13:09 UTC | 16h 19m |
| 2026-06-18 | SVA9810 | - | Jun 18, 13:05 UTC | Jun 19, 12:59 UTC | 23h 54m |
| 2026-06-18 | SVA256 | IST → JED | Jun 18, 12:50 UTC | Jun 19, 02:14 UTC | 13h 24m |
| 2026-06-18 | SVA257 | - | Jun 18, 08:20 UTC | Jun 18, 10:15 UTC | 1h 55m |
| 2026-06-17 | SVA257 | - | Jun 17, 13:05 UTC | Jun 18, 10:15 UTC | 21h 10m |
| 2026-06-17 | SVA256 | IST → JED | Jun 17, 12:40 UTC | Jun 18, 10:15 UTC | 21h 35m |
| 2026-06-17 | SVA257 | - | Jun 17, 08:35 UTC | Jun 17, 10:40 UTC | 2h 5m |
| 2026-06-16 | SVA387 | JED → CAI | Jun 16, 20:30 UTC | Jun 16, 21:05 UTC | 35m |
| 2026-06-16 | SVA305 | JED → CAI | Jun 16, 13:09 UTC | Jun 16, 13:34 UTC | 25m |
| 2026-06-14 | SVA210 | MXP → RUH | Jun 14, 14:20 UTC | Jun 14, 16:35 UTC | 2h 15m |
| 2026-06-13 | SVA211 | - | Jun 13, 20:40 UTC | Jun 14, 11:55 UTC | 15h 15m |
| 2026-06-13 | SVA389 | JED → CAI | Jun 13, 18:20 UTC | Jun 13, 18:40 UTC | 20m |
| 2026-06-12 | SVA302 | CAI → JED | Jun 12, 18:20 UTC | Jun 12, 18:30 UTC | 10m |
| 2026-06-12 | SVA303 | JED → CAI | Jun 12, 15:45 UTC | Jun 12, 16:00 UTC | 15m |
| 2026-06-11 | SVA309 | JED → CAI | Jun 11, 18:20 UTC | Jun 11, 23:30 UTC | 5h 10m |
| 2026-06-11 | SVA5509 | - | Jun 11, 04:00 UTC | Jun 11, 16:05 UTC | 12h 5m |
| 2026-06-07 | SVA5505 | - | Jun 7, 09:30 UTC | Jun 7, 19:10 UTC | 9h 40m |
| 2026-06-05 | SVA389 | JED → CAI | Jun 5, 18:30 UTC | Jun 5, 18:50 UTC | 20m |
| 2026-06-03 | SVA260 | IST → JED | Jun 3, 19:45 UTC | Jun 4, 10:45 UTC | 15h 0m |
| 2026-06-03 | SVA261 | JED → IST | Jun 3, 06:20 UTC | Jun 3, 17:50 UTC | 11h 30m |
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-AQ18 page for operator, model, and routing details .