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
- 166
- Distinct callsigns
- 20
- Country
- SA
- Last broadcast
- 5d 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 | - | 12 | 2026-07-07 |
| SVA119 | Saudi Arabian Airlines | 11 | 2026-07-17 |
| SVA848 | Saudi Arabian Airlines | 8 | 2026-07-17 |
| SVA120 | - | 8 | 2026-07-18 |
| SVA5010 | - | 7 | 2026-06-27 |
| SVA215 | Saudi Arabian Airlines | 6 | 2026-07-25 |
| SVA127 | Saudi Arabian Airlines | 6 | 2026-07-23 |
| SVA9629 | - | 5 | 2026-05-16 |
| SVA834 | - | 5 | 2026-06-20 |
| SVA227 | Saudi Arabian Airlines | 5 | 2026-07-25 |
| SVA126 | - | 5 | 2026-07-24 |
| SVA856 | - | 4 | 2026-07-13 |
| SVA846 | Saudi Arabian Airlines | 4 | 2026-06-13 |
| SVA844 | Saudi Arabian Airlines | 4 | 2026-07-22 |
| SVA373 | - | 4 | 2026-06-15 |
| SVA131 | Saudi Arabian Airlines | 4 | 2026-07-22 |
| SVA885 | - | 3 | 2026-07-02 |
| SVA870 | Saudi Arabian Airlines | 3 | 2026-05-27 |
| SVA847 | Saudi Arabian Airlines | 3 | 2026-06-14 |
| SVA5591 | - | 3 | 2026-06-10 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | SVA214 | AMS → JED | Jul 26, 15:15 UTC | Jul 26, 17:55 UTC | 2h 40m |
| 2026-07-25 | SVA215 | JED → AMS | Jul 25, 18:20 UTC | Jul 26, 12:00 UTC | 17h 41m |
| 2026-07-25 | SVA227 | JED → MAD | Jul 25, 12:10 UTC | Jul 25, 15:30 UTC | 3h 20m |
| 2026-07-24 | SVA227 | JED → MAD | Jul 24, 16:20 UTC | Jul 25, 15:30 UTC | 23h 10m |
| 2026-07-24 | SVA126 | - | Jul 24, 14:20 UTC | Jul 25, 14:15 UTC | 23h 55m |
| 2026-07-24 | SVA126 | - | Jul 24, 14:10 UTC | Jul 25, 12:15 UTC | 22h 5m |
| 2026-07-23 | SVA127 | JED → CDG | Jul 23, 19:45 UTC | Jul 24, 11:45 UTC | 16h 0m |
| 2026-07-23 | SVA130 | CDG → JED | Jul 23, 07:40 UTC | Jul 23, 18:15 UTC | 10h 35m |
| 2026-07-22 | SVA131 | JED → CDG | Jul 22, 11:10 UTC | Jul 23, 04:15 UTC | 17h 5m |
| 2026-07-22 | SVA131 | JED → CDG | Jul 22, 04:20 UTC | Jul 23, 04:15 UTC | 23h 55m |
| 2026-07-22 | SVA844 | JED → BKK | Jul 22, 02:20 UTC | Jul 23, 02:15 UTC | 23h 55m |
| 2026-07-22 | SVA844 | JED → BKK | Jul 22, 00:20 UTC | Jul 23, 00:05 UTC | 23h 45m |
| 2026-07-21 | SVA844 | JED → BKK | Jul 21, 16:20 UTC | Jul 22, 12:50 UTC | 20h 30m |
| 2026-07-21 | SVA844 | JED → BKK | Jul 21, 15:15 UTC | Jul 22, 12:50 UTC | 21h 35m |
| 2026-07-20 | SVA883 | CAN → JED | Jul 20, 17:00 UTC | Jul 21, 11:00 UTC | 17h 59m |
| 2026-07-19 | SVA882 | JED → CAN | Jul 19, 15:20 UTC | Jul 20, 05:40 UTC | 14h 20m |
| 2026-07-18 | SVA227 | - | Jul 18, 16:20 UTC | Jul 19, 11:15 UTC | 18h 55m |
| 2026-07-18 | SVA227 | - | Jul 18, 14:20 UTC | Jul 19, 11:15 UTC | 20h 55m |
| 2026-07-18 | SVA120 | - | Jul 18, 14:10 UTC | Jul 19, 11:15 UTC | 21h 5m |
| 2026-07-17 | SVA119 | JED → LHR | Jul 17, 19:09 UTC | Jul 18, 11:30 UTC | 16h 21m |
| 2026-07-17 | SVA848 | JED → BKK | Jul 17, 10:25 UTC | Jul 17, 16:59 UTC | 6h 35m |
| 2026-07-16 | SVA848 | JED → BKK | Jul 16, 18:40 UTC | Jul 17, 16:59 UTC | 22h 20m |
| 2026-07-16 | SVA220 | - | Jul 16, 15:14 UTC | Jul 17, 13:10 UTC | 21h 55m |
| 2026-07-16 | SVA227 | - | Jul 16, 07:55 UTC | Jul 16, 11:15 UTC | 3h 20m |
| 2026-07-14 | SVA228 | BCN → JED | Jul 14, 15:00 UTC | Jul 14, 18:15 UTC | 3h 15m |
| 2026-07-13 | SVA229 | - | Jul 13, 18:35 UTC | Jul 14, 12:45 UTC | 18h 10m |
| 2026-07-13 | SVA856 | - | Jul 13, 09:40 UTC | Jul 13, 09:50 UTC | 10m |
| 2026-07-12 | SVA214 | - | Jul 12, 14:25 UTC | Jul 13, 07:30 UTC | 17h 5m |
| 2026-07-11 | SVA215 | - | Jul 11, 16:20 UTC | Jul 12, 11:40 UTC | 19h 20m |
| 2026-07-11 | SVA215 | MAD → AMS | Jul 11, 15:15 UTC | Jul 12, 11:40 UTC | 20h 25m |
| 2026-07-10 | SVA849 | - | Jul 10, 19:10 UTC | Jul 11, 11:00 UTC | 15h 50m |
| 2026-07-10 | SVA848 | - | Jul 10, 10:20 UTC | Jul 10, 17:00 UTC | 6h 40m |
| 2026-07-09 | SVA848 | - | Jul 9, 16:20 UTC | Jul 10, 16:15 UTC | 23h 55m |
| 2026-07-09 | SVA120 | - | Jul 9, 14:20 UTC | Jul 10, 13:10 UTC | 22h 50m |
| 2026-07-09 | SVA120 | - | Jul 9, 14:05 UTC | Jul 10, 11:20 UTC | 21h 15m |
| 2026-07-08 | SVA119 | - | Jul 8, 14:20 UTC | Jul 9, 11:25 UTC | 21h 5m |
| 2026-07-08 | SVA119 | - | Jul 8, 14:05 UTC | Jul 9, 11:25 UTC | 21h 20m |
| 2026-07-07 | SVA119 | - | Jul 7, 18:35 UTC | Jul 8, 11:30 UTC | 16h 55m |
| 2026-07-07 | SVA840 | - | Jul 7, 09:15 UTC | Jul 7, 16:20 UTC | 7h 5m |
| 2026-07-06 | SVA840 | - | Jul 6, 21:40 UTC | Jul 7, 16:20 UTC | 18h 40m |
| 2026-07-06 | SVA840 | - | Jul 6, 18:40 UTC | Jul 7, 16:20 UTC | 21h 40m |
| 2026-07-06 | SVA857 | - | Jul 6, 16:10 UTC | Jul 6, 16:20 UTC | 10m |
| 2026-07-05 | SVA214 | - | Jul 5, 14:35 UTC | Jul 6, 07:35 UTC | 17h 0m |
| 2026-07-04 | SVA215 | - | Jul 4, 16:20 UTC | Jul 5, 11:50 UTC | 19h 30m |
| 2026-07-04 | SVA215 | - | Jul 4, 14:20 UTC | Jul 5, 11:50 UTC | 21h 30m |
| 2026-07-04 | SVA215 | - | Jul 4, 14:10 UTC | Jul 5, 11:50 UTC | 21h 40m |
| 2026-07-03 | SVA119 | - | Jul 3, 18:30 UTC | Jul 4, 11:25 UTC | 16h 55m |
| 2026-07-03 | SVA840 | - | Jul 3, 09:10 UTC | Jul 3, 16:10 UTC | 7h 0m |
| 2026-07-02 | SVA840 | - | Jul 2, 14:35 UTC | Jul 3, 12:45 UTC | 22h 10m |
| 2026-07-02 | SVA885 | - | Jul 2, 12:50 UTC | Jul 3, 11:55 UTC | 23h 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 .