sensors Mode-S transponder
7105B2
ICAO 24-bit transponder address · allocated to Saudi Arabia
Currently assigned to HZ-AR33 · BOEING 787-10 Dreamliner
- Hex
- 7105B2
- Octal
- 34202662
- Decimal
- 7,407,026
- Country
- SA
- Tail
- HZ-AR33
- Type
- B78X
- Flights observed
- 75
- Distinct callsigns
- 20
- Country
- SA
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 7105B2 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 |
|---|---|---|---|
| SVA834 | Saudi Arabian Airlines | 9 | 2026-05-25 |
| SVA835 | Saudi Arabian Airlines | 6 | 2026-05-25 |
| SVA215 | Saudi Arabian Airlines | 6 | 2026-05-05 |
| SVA9625 | - | 5 | 2026-05-02 |
| SVA848 | Saudi Arabian Airlines | 5 | 2026-05-27 |
| SVA846 | Saudi Arabian Airlines | 5 | 2026-05-16 |
| SVA9629 | - | 4 | 2026-05-13 |
| SVA870 | Saudi Arabian Airlines | 4 | 2026-04-25 |
| SVA840 | Saudi Arabian Airlines | 4 | 2026-05-10 |
| SVA214 | Saudi Arabian Airlines | 4 | 2026-05-05 |
| SVA127 | Saudi Arabian Airlines | 4 | 2026-05-21 |
| SVA847 | Saudi Arabian Airlines | 3 | 2026-05-17 |
| SVA5590 | - | 3 | 2026-05-13 |
| SVA871 | Saudi Arabian Airlines | 2 | 2026-04-23 |
| SVA5019 | - | 2 | 2026-05-09 |
| SVA5007 | - | 2 | 2026-05-10 |
| SVA849 | Saudi Arabian Airlines | 1 | 2026-04-29 |
| SVA5009 | - | 1 | 2026-05-04 |
| SVA377 | Saudi Arabian Airlines | 1 | 2026-05-22 |
| SVA376 | Saudi Arabian Airlines | 1 | 2026-05-23 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-28 | SVA220 | MAD → MXP | May 28, 15:05 UTC | May 28, 18:40 UTC | 3h 35m |
| 2026-05-27 | SVA227 | JED → MAD | May 27, 19:20 UTC | May 28, 11:00 UTC | 15h 40m |
| 2026-05-27 | SVA848 | JED → BKK | May 27, 12:10 UTC | May 27, 16:35 UTC | 4h 25m |
| 2026-05-25 | SVA835 | KUL → JED | May 25, 09:50 UTC | May 25, 16:40 UTC | 6h 50m |
| 2026-05-25 | SVA834 | JED → KUL | May 25, 07:15 UTC | May 25, 07:50 UTC | 35m |
| 2026-05-25 | SVA834 | JED → KUL | May 25, 02:50 UTC | May 25, 04:10 UTC | 1h 20m |
| 2026-05-23 | SVA376 | CMN → JED | May 23, 07:00 UTC | May 23, 10:20 UTC | 3h 20m |
| 2026-05-22 | SVA377 | JED → CMN | May 22, 08:35 UTC | May 23, 04:05 UTC | 19h 29m |
| 2026-05-21 | SVA126 | CDG → JED | May 21, 15:55 UTC | May 22, 06:30 UTC | 14h 35m |
| 2026-05-21 | SVA127 | JED → CDG | May 21, 09:20 UTC | May 21, 14:00 UTC | 4h 40m |
| 2026-05-17 | SVA847 | BKK → RUH | May 17, 08:40 UTC | May 17, 12:55 UTC | 4h 15m |
| 2026-05-16 | SVA846 | RUH → BKK | May 16, 10:46 UTC | May 17, 06:05 UTC | 19h 20m |
| 2026-05-16 | SVA847 | BKK → RUH | May 16, 08:41 UTC | May 17, 06:05 UTC | 21h 25m |
| 2026-05-15 | SVA846 | RUH → BKK | May 15, 23:55 UTC | May 16, 06:10 UTC | 6h 16m |
| 2026-05-14 | SVA847 | BKK → RUH | May 14, 08:40 UTC | May 14, 12:55 UTC | 4h 15m |
| 2026-05-13 | SVA846 | RUH → BKK | May 13, 10:35 UTC | May 14, 05:55 UTC | 19h 20m |
| 2026-05-13 | SVA846 | RUH → BKK | May 13, 08:50 UTC | May 14, 05:55 UTC | 21h 5m |
| 2026-05-13 | SVA846 | RUH → BKK | May 13, 07:25 UTC | May 14, 05:55 UTC | 22h 30m |
| 2026-05-13 | SVA5590 | - | May 13, 04:35 UTC | May 14, 04:15 UTC | 23h 40m |
| 2026-05-13 | SVA5590 | - | May 13, 02:35 UTC | May 14, 02:25 UTC | 23h 50m |
| 2026-05-13 | SVA9629 | - | May 13, 00:35 UTC | May 14, 00:15 UTC | 23h 40m |
| 2026-05-12 | SVA9629 | - | May 12, 16:35 UTC | May 13, 11:05 UTC | 18h 30m |
| 2026-05-12 | SVA9629 | - | May 12, 14:35 UTC | May 13, 11:05 UTC | 20h 30m |
| 2026-05-12 | SVA9629 | - | May 12, 14:20 UTC | May 13, 11:05 UTC | 20h 45m |
| 2026-05-12 | SVA127 | JED → CDG | May 12, 08:10 UTC | May 12, 11:55 UTC | 3h 45m |
| 2026-05-11 | SVA127 | JED → CDG | May 11, 16:15 UTC | May 12, 11:55 UTC | 19h 41m |
| 2026-05-11 | SVA127 | JED → CDG | May 11, 13:10 UTC | May 12, 11:55 UTC | 22h 46m |
| 2026-05-10 | SVA5007 | - | May 10, 21:30 UTC | May 11, 16:25 UTC | 18h 55m |
| 2026-05-10 | SVA5007 | - | May 10, 18:39 UTC | May 11, 16:25 UTC | 21h 45m |
| 2026-05-10 | SVA840 | JED → KUL | May 10, 16:20 UTC | May 10, 16:40 UTC | 20m |
| 2026-05-10 | SVA840 | JED → KUL | May 10, 09:35 UTC | May 10, 13:10 UTC | 3h 35m |
| 2026-05-09 | SVA5019 | - | May 9, 12:35 UTC | May 10, 09:55 UTC | 21h 20m |
| 2026-05-09 | SVA5019 | - | May 9, 09:50 UTC | May 9, 13:10 UTC | 3h 20m |
| 2026-05-09 | SVA834 | JED → KUL | May 9, 00:15 UTC | May 9, 07:10 UTC | 6h 55m |
| 2026-05-05 | SVA214 | AMS → JED | May 5, 14:30 UTC | May 5, 18:25 UTC | 3h 55m |
| 2026-05-05 | SVA215 | JED → AMS | May 5, 08:35 UTC | May 5, 12:00 UTC | 3h 25m |
| 2026-05-04 | SVA215 | JED → AMS | May 4, 13:10 UTC | May 5, 12:00 UTC | 22h 51m |
| 2026-05-04 | SVA5009 | - | May 4, 10:00 UTC | May 4, 10:15 UTC | 15m |
| 2026-05-04 | SVA834 | JED → KUL | May 4, 07:00 UTC | May 4, 07:25 UTC | 25m |
| 2026-05-04 | SVA834 | JED → KUL | May 4, 00:30 UTC | May 4, 04:00 UTC | 3h 30m |
| 2026-05-03 | SVA5590 | - | May 3, 00:45 UTC | May 4, 00:30 UTC | 23h 44m |
| 2026-05-02 | SVA9625 | - | May 2, 15:10 UTC | May 3, 01:40 UTC | 10h 30m |
| 2026-05-02 | SVA9625 | - | May 2, 01:00 UTC | May 3, 00:10 UTC | 23h 10m |
| 2026-05-01 | SVA9625 | - | May 1, 22:45 UTC | May 2, 22:30 UTC | 23h 45m |
| 2026-05-01 | SVA9625 | - | May 1, 21:40 UTC | May 2, 18:55 UTC | 21h 15m |
| 2026-05-01 | SVA9625 | - | May 1, 18:35 UTC | May 2, 18:30 UTC | 23h 56m |
| 2026-05-01 | SVA840 | JED → KUL | May 1, 15:20 UTC | May 1, 15:45 UTC | 25m |
| 2026-05-01 | SVA840 | JED → KUL | May 1, 09:45 UTC | May 1, 12:25 UTC | 2h 40m |
| 2026-04-29 | SVA849 | BKK → JED | Apr 29, 19:15 UTC | Apr 29, 20:00 UTC | 45m |
| 2026-04-29 | SVA848 | JED → BKK | Apr 29, 10:15 UTC | Apr 29, 16:15 UTC | 6h 0m |
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-AR33 page for operator, model, and routing details .