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
- 49
- Distinct callsigns
- 20
- Country
- SA
- Last broadcast
- 2h 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 | Saudi Arabian Airlines | 6 | 2026-05-25 |
| SVA311 | Saudi Arabian Airlines | 5 | 2026-05-30 |
| SVA708 | Saudi Arabian Airlines | 4 | 2026-05-25 |
| SVA589 | Saudi Arabian Airlines | 3 | 2026-05-19 |
| SVA417 | Saudi Arabian Airlines | 3 | 2026-05-25 |
| SVA312 | Saudi Arabian Airlines | 3 | 2026-05-26 |
| SVA259 | Saudi Arabian Airlines | 3 | 2026-04-30 |
| SVA9829 | - | 2 | 2026-04-25 |
| SVA3230 | Saudi Arabian Airlines | 2 | 2026-04-26 |
| SVA9649 | - | 1 | 2026-05-09 |
| SVA9645 | - | 1 | 2026-05-21 |
| SVA709 | Saudi Arabian Airlines | 1 | 2026-04-16 |
| SVA700 | Saudi Arabian Airlines | 1 | 2026-04-20 |
| SVA636 | Saudi Arabian Airlines | 1 | 2026-05-21 |
| SVA596 | Saudi Arabian Airlines | 1 | 2026-05-16 |
| SVA588 | Saudi Arabian Airlines | 1 | 2026-04-22 |
| SVA554 | Saudi Arabian Airlines | 1 | 2026-05-28 |
| SVA380 | Saudi Arabian Airlines | 1 | 2026-05-01 |
| SVA3776 | Saudi Arabian Airlines | 1 | 2026-04-30 |
| SVA320 | Saudi Arabian Airlines | 1 | 2026-04-18 |
Recent flights last 49
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-30 | SVA311 | RUH → CAI | May 30, 06:25 UTC | May 30, 06:45 UTC | 20m |
| 2026-05-28 | SVA554 | RUH → DXB | May 28, 11:25 UTC | May 28, 15:20 UTC | 3h 55m |
| 2026-05-26 | SVA312 | CAI → RUH | May 26, 18:19 UTC | May 26, 18:40 UTC | 20m |
| 2026-05-25 | SVA708 | RUH → KHI | May 25, 22:15 UTC | May 26, 16:10 UTC | 17h 55m |
| 2026-05-25 | SVA321 | RUH → CAI | May 25, 13:30 UTC | May 25, 19:44 UTC | 6h 15m |
| 2026-05-25 | SVA417 | RUH → CAI | May 25, 11:00 UTC | May 25, 11:20 UTC | 20m |
| 2026-05-23 | SVA312 | CAI → RUH | May 23, 18:30 UTC | May 23, 18:45 UTC | 15m |
| 2026-05-23 | SVA311 | RUH → CAI | May 23, 06:25 UTC | May 23, 06:50 UTC | 25m |
| 2026-05-21 | SVA636 | AMM → JED | May 21, 18:15 UTC | May 21, 18:30 UTC | 15m |
| 2026-05-21 | SVA9645 | - | May 21, 00:00 UTC | May 21, 00:20 UTC | 20m |
| 2026-05-19 | SVA589 | DXB → JED | May 19, 14:20 UTC | May 20, 07:05 UTC | 16h 46m |
| 2026-05-18 | SVA589 | DXB → JED | May 18, 18:20 UTC | May 19, 14:55 UTC | 20h 34m |
| 2026-05-17 | SVA210 | MXP → RUH | May 17, 14:25 UTC | May 17, 16:45 UTC | 2h 20m |
| 2026-05-17 | SVA211 | JED → MXP | May 17, 09:25 UTC | May 17, 12:01 UTC | 2h 35m |
| 2026-05-16 | SVA596 | MED → DXB | May 16, 07:51 UTC | May 16, 08:20 UTC | 30m |
| 2026-05-15 | SVA311 | RUH → CAI | May 15, 06:25 UTC | May 15, 06:50 UTC | 25m |
| 2026-05-13 | SVA256 | IST → JED | May 13, 12:50 UTC | May 13, 14:30 UTC | 1h 40m |
| 2026-05-13 | SVA257 | JED → IST | May 13, 08:35 UTC | May 13, 10:25 UTC | 1h 50m |
| 2026-05-11 | SVA321 | RUH → CAI | May 11, 13:55 UTC | May 11, 19:45 UTC | 5h 50m |
| 2026-05-11 | SVA417 | RUH → CAI | May 11, 11:15 UTC | May 11, 11:40 UTC | 25m |
| 2026-05-09 | SVA9649 | - | May 9, 22:39 UTC | May 10, 08:25 UTC | 9h 45m |
| 2026-05-08 | SVA238 | GVA → RUH | May 8, 14:10 UTC | May 8, 17:55 UTC | 3h 45m |
| 2026-05-07 | SVA312 | CAI → RUH | May 7, 18:10 UTC | May 7, 18:20 UTC | 10m |
| 2026-05-07 | SVA313 | RUH → CAI | May 7, 15:50 UTC | May 7, 16:15 UTC | 25m |
| 2026-05-06 | SVA708 | RUH → KHI | May 6, 04:35 UTC | May 6, 05:30 UTC | 55m |
| 2026-05-01 | SVA380 | CAI → MED | May 1, 19:50 UTC | May 1, 20:15 UTC | 25m |
| 2026-05-01 | SVA258 | IST → MED | May 1, 11:50 UTC | May 1, 13:35 UTC | 1h 45m |
| 2026-04-30 | SVA259 | MED → IST | Apr 30, 15:30 UTC | May 1, 09:15 UTC | 17h 45m |
| 2026-04-30 | SVA259 | MED → IST | Apr 30, 13:35 UTC | May 1, 09:15 UTC | 19h 40m |
| 2026-04-30 | SVA259 | MED → IST | Apr 30, 12:20 UTC | May 1, 09:15 UTC | 20h 55m |
| 2026-04-30 | SVA3776 | RUH → COK | Apr 30, 06:20 UTC | Apr 30, 10:15 UTC | 3h 55m |
| 2026-04-28 | SVA311 | RUH → CAI | Apr 28, 21:50 UTC | Apr 29, 06:39 UTC | 8h 50m |
| 2026-04-28 | SVA321 | RUH → CAI | Apr 28, 13:45 UTC | Apr 28, 19:50 UTC | 6h 5m |
| 2026-04-28 | SVA417 | RUH → CAI | Apr 28, 10:50 UTC | Apr 28, 11:10 UTC | 20m |
| 2026-04-26 | SVA3230 | IST → MED | Apr 26, 00:20 UTC | Apr 26, 02:05 UTC | 1h 45m |
| 2026-04-25 | SVA9829 | - | Apr 25, 12:35 UTC | Apr 25, 22:35 UTC | 10h 0m |
| 2026-04-25 | SVA3230 | IST → MED | Apr 25, 01:00 UTC | Apr 25, 09:55 UTC | 8h 55m |
| 2026-04-24 | SVA9829 | - | Apr 24, 21:40 UTC | Apr 24, 23:00 UTC | 1h 20m |
| 2026-04-22 | SVA589 | DXB → JED | Apr 22, 14:00 UTC | Apr 22, 15:15 UTC | 1h 15m |
| 2026-04-22 | SVA588 | JED → DXB | Apr 22, 10:40 UTC | Apr 22, 11:40 UTC | 1h 0m |
| 2026-04-20 | SVA700 | JED → KHI | Apr 20, 23:45 UTC | Apr 21, 05:55 UTC | 6h 10m |
| 2026-04-18 | SVA320 | CAI → RUH | Apr 18, 22:15 UTC | Apr 18, 22:30 UTC | 15m |
| 2026-04-18 | SVA321 | - | Apr 18, 19:40 UTC | Apr 18, 20:05 UTC | 25m |
| 2026-04-16 | SVA709 | KHI → MED | Apr 16, 09:50 UTC | Apr 16, 11:04 UTC | 1h 15m |
| 2026-04-16 | SVA708 | RUH → KHI | Apr 16, 05:29 UTC | Apr 16, 05:45 UTC | 15m |
| 2026-04-16 | SVA708 | RUH → KHI | Apr 16, 04:40 UTC | Apr 16, 05:05 UTC | 25m |
| 2026-04-14 | SVA311 | RUH → CAI | Apr 14, 06:30 UTC | Apr 14, 06:45 UTC | 15m |
| 2026-04-13 | SVA321 | - | Apr 13, 19:45 UTC | Apr 13, 19:55 UTC | 10m |
| 2026-04-13 | SVA321 | - | Apr 13, 19:30 UTC | Apr 13, 19:45 UTC | 15m |
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 .