sensors Mode-S transponder
7105B1
ICAO 24-bit transponder address · allocated to Saudi Arabia
Currently assigned to HZ-AR32 · BOEING 787-10 Dreamliner
- Hex
- 7105B1
- Octal
- 34202661
- Decimal
- 7,407,025
- Country
- SA
- Tail
- HZ-AR32
- Type
- B78X
- Flights observed
- 85
- Distinct callsigns
- 20
- Country
- SA
- Last broadcast
- 5h ago
Last known position
Country allocation
The ICAO 24-bit address 7105B1 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 |
|---|---|---|---|
| SVA840 | Saudi Arabian Airlines | 7 | 2026-05-17 |
| SVA9629 | - | 5 | 2026-05-16 |
| SVA119 | Saudi Arabian Airlines | 5 | 2026-06-06 |
| SVA846 | Saudi Arabian Airlines | 4 | 2026-06-13 |
| SVA373 | - | 4 | 2026-06-15 |
| SVA127 | Saudi Arabian Airlines | 4 | 2026-05-29 |
| SVA120 | Saudi Arabian Airlines | 4 | 2026-06-07 |
| SVA870 | Saudi Arabian Airlines | 3 | 2026-05-27 |
| SVA856 | Saudi Arabian Airlines | 3 | 2026-05-28 |
| SVA847 | Saudi Arabian Airlines | 3 | 2026-06-14 |
| SVA5591 | - | 3 | 2026-06-10 |
| SVA5010 | - | 3 | 2026-06-05 |
| SVA9684 | - | 2 | 2026-06-01 |
| SVA9616 | - | 2 | 2026-06-10 |
| SVA887 | Saudi Arabian Airlines | 2 | 2026-05-11 |
| SVA886 | Saudi Arabian Airlines | 2 | 2026-05-11 |
| SVA871 | Saudi Arabian Airlines | 2 | 2026-05-27 |
| SVA848 | Saudi Arabian Airlines | 2 | 2026-06-15 |
| SVA834 | Saudi Arabian Airlines | 2 | 2026-06-03 |
| SVA5644 | - | 2 | 2026-05-14 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-16 | SVA372 | CMN → JED | Jun 16, 14:15 UTC | Jun 16, 18:20 UTC | 4h 5m |
| 2026-06-15 | SVA373 | - | Jun 15, 19:14 UTC | Jun 16, 11:25 UTC | 16h 10m |
| 2026-06-15 | SVA848 | JED → BKK | Jun 15, 10:30 UTC | Jun 15, 16:59 UTC | 6h 30m |
| 2026-06-14 | SVA848 | JED → BKK | Jun 14, 14:25 UTC | Jun 15, 13:10 UTC | 22h 45m |
| 2026-06-14 | SVA847 | BKK → RUH | Jun 14, 12:20 UTC | Jun 15, 10:50 UTC | 22h 29m |
| 2026-06-14 | SVA847 | BKK → RUH | Jun 14, 08:40 UTC | Jun 14, 14:45 UTC | 6h 5m |
| 2026-06-13 | SVA846 | RUH → BKK | Jun 13, 23:50 UTC | Jun 14, 06:30 UTC | 6h 40m |
| 2026-06-11 | SVA841 | KUL → JED | Jun 11, 19:15 UTC | Jun 11, 22:55 UTC | 3h 40m |
| 2026-06-10 | SVA9616 | - | Jun 10, 23:00 UTC | Jun 11, 17:20 UTC | 18h 20m |
| 2026-06-10 | SVA5591 | - | Jun 10, 05:55 UTC | Jun 10, 21:00 UTC | 15h 5m |
| 2026-06-09 | SVA5591 | - | Jun 9, 23:15 UTC | Jun 10, 03:50 UTC | 4h 35m |
| 2026-06-07 | SVA120 | LHR → RUH | Jun 7, 13:50 UTC | Jun 7, 17:55 UTC | 4h 5m |
| 2026-06-06 | SVA119 | JED → LHR | Jun 6, 18:39 UTC | Jun 7, 11:30 UTC | 16h 50m |
| 2026-06-05 | SVA5010 | - | Jun 5, 22:20 UTC | Jun 6, 16:50 UTC | 18h 30m |
| 2026-06-05 | SVA5010 | - | Jun 5, 21:55 UTC | Jun 6, 16:50 UTC | 18h 55m |
| 2026-06-05 | SVA5010 | - | Jun 5, 19:00 UTC | Jun 6, 16:50 UTC | 21h 50m |
| 2026-06-04 | SVA5008 | - | Jun 4, 22:55 UTC | Jun 5, 17:00 UTC | 18h 5m |
| 2026-06-04 | SVA9618 | - | Jun 4, 21:25 UTC | Jun 5, 17:00 UTC | 19h 35m |
| 2026-06-04 | SVA9616 | - | Jun 4, 05:55 UTC | Jun 4, 19:40 UTC | 13h 45m |
| 2026-06-03 | SVA5591 | - | Jun 3, 09:45 UTC | Jun 4, 04:15 UTC | 18h 30m |
| 2026-06-03 | SVA834 | JED → KUL | Jun 3, 07:10 UTC | Jun 3, 07:40 UTC | 30m |
| 2026-06-02 | SVA120 | LHR → RUH | Jun 2, 14:15 UTC | Jun 3, 04:10 UTC | 13h 55m |
| 2026-06-02 | SVA119 | JED → LHR | Jun 2, 07:50 UTC | Jun 2, 11:25 UTC | 3h 35m |
| 2026-06-01 | SVA119 | JED → LHR | Jun 1, 10:20 UTC | Jun 2, 10:15 UTC | 23h 55m |
| 2026-06-01 | SVA9684 | - | Jun 1, 08:20 UTC | Jun 2, 08:15 UTC | 23h 55m |
| 2026-06-01 | SVA9684 | - | Jun 1, 07:50 UTC | Jun 1, 12:00 UTC | 4h 10m |
| 2026-06-01 | SVA5649 | - | Jun 1, 01:55 UTC | Jun 1, 06:00 UTC | 4h 5m |
| 2026-05-30 | SVA126 | CDG → JED | May 30, 14:30 UTC | May 30, 18:15 UTC | 3h 45m |
| 2026-05-29 | SVA127 | JED → CDG | May 29, 19:00 UTC | May 30, 11:50 UTC | 16h 50m |
| 2026-05-28 | SVA856 | JED → SIN | May 28, 23:50 UTC | May 29, 07:05 UTC | 7h 15m |
| 2026-05-27 | SVA871 | MNL → JED | May 27, 17:10 UTC | May 27, 23:45 UTC | 6h 35m |
| 2026-05-27 | SVA870 | JED → MNL | May 27, 06:25 UTC | May 27, 15:05 UTC | 8h 40m |
| 2026-05-25 | SVA372 | CMN → JED | May 25, 14:25 UTC | May 25, 17:40 UTC | 3h 15m |
| 2026-05-25 | SVA373 | JED → CMN | May 25, 07:10 UTC | May 25, 11:45 UTC | 4h 35m |
| 2026-05-23 | SVA871 | MNL → JED | May 23, 16:00 UTC | May 23, 22:20 UTC | 6h 20m |
| 2026-05-23 | SVA870 | JED → MNL | May 23, 03:40 UTC | May 23, 12:25 UTC | 8h 45m |
| 2026-05-22 | SVA870 | JED → MNL | May 22, 16:20 UTC | May 23, 12:25 UTC | 20h 4m |
| 2026-05-22 | SVA839 | SIN → JED | May 22, 13:15 UTC | May 22, 13:25 UTC | 10m |
| 2026-05-21 | SVA847 | BKK → RUH | May 21, 09:40 UTC | May 21, 13:55 UTC | 4h 15m |
| 2026-05-20 | SVA846 | RUH → BKK | May 20, 12:20 UTC | May 21, 06:45 UTC | 18h 25m |
| 2026-05-20 | SVA846 | RUH → BKK | May 20, 11:45 UTC | May 21, 06:45 UTC | 19h 0m |
| 2026-05-20 | SVA846 | RUH → BKK | May 20, 08:30 UTC | May 21, 06:45 UTC | 22h 15m |
| 2026-05-19 | SVA126 | CDG → JED | May 19, 15:05 UTC | May 20, 06:15 UTC | 15h 11m |
| 2026-05-19 | SVA127 | JED → CDG | May 19, 09:05 UTC | May 19, 13:10 UTC | 4h 5m |
| 2026-05-18 | SVA127 | JED → CDG | May 18, 16:20 UTC | May 19, 13:10 UTC | 20h 49m |
| 2026-05-18 | SVA127 | JED → CDG | May 18, 14:20 UTC | May 19, 13:10 UTC | 22h 49m |
| 2026-05-18 | SVA120 | LHR → RUH | May 18, 14:05 UTC | May 19, 12:15 UTC | 22h 9m |
| 2026-05-17 | SVA119 | JED → LHR | May 17, 18:35 UTC | May 18, 11:40 UTC | 17h 5m |
| 2026-05-17 | SVA840 | JED → KUL | May 17, 15:31 UTC | May 17, 16:30 UTC | 1h 0m |
| 2026-05-16 | SVA9629 | - | May 16, 16:35 UTC | May 17, 11:40 UTC | 19h 5m |
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-AR32 page for operator, model, and routing details .