sensors Mode-S transponder
710108
ICAO 24-bit transponder address · allocated to Saudi Arabia
Currently assigned to HZ-AK30 · BOEING 777-300ER
- Hex
- 710108
- Octal
- 34200410
- Decimal
- 7,405,832
- Country
- SA
- Tail
- HZ-AK30
- Type
- B77W
- Flights observed
- 191
- Distinct callsigns
- 20
- Country
- SA
- Last broadcast
- 1h ago
Last known position
Country allocation
The ICAO 24-bit address 710108 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 |
|---|---|---|---|
| SVA121 | - | 20 | 2026-07-09 |
| SVA862 | - | 16 | 2026-07-02 |
| SVA861 | Saudi Arabian Airlines | 10 | 2026-05-20 |
| SVA804 | Saudi Arabian Airlines | 10 | 2026-07-09 |
| SVA122 | - | 10 | 2026-07-10 |
| SVA111 | - | 10 | 2026-07-11 |
| SVA143 | - | 8 | 2026-07-11 |
| SVA818 | - | 6 | 2026-06-24 |
| SVA110 | Saudi Arabian Airlines | 6 | 2026-06-12 |
| SVA372 | Saudi Arabian Airlines | 5 | 2026-06-08 |
| SVA805 | - | 4 | 2026-06-19 |
| SVA756 | - | 4 | 2026-06-25 |
| SVA725 | Saudi Arabian Airlines | 4 | 2026-04-22 |
| SVA144 | - | 4 | 2026-07-12 |
| SVA828 | - | 3 | 2026-07-13 |
| SVA811 | Saudi Arabian Airlines | 3 | 2026-06-11 |
| SVA800 | Saudi Arabian Airlines | 3 | 2026-05-17 |
| SVA734 | Saudi Arabian Airlines | 3 | 2026-05-18 |
| SVA5810 | - | 3 | 2026-06-03 |
| SVA5594 | - | 3 | 2026-05-10 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | SVA829 | - | Jul 14, 05:15 UTC | Jul 14, 09:30 UTC | 4h 15m |
| 2026-07-13 | SVA828 | - | Jul 13, 11:00 UTC | Jul 14, 03:20 UTC | 16h 20m |
| 2026-07-13 | SVA829 | - | Jul 13, 05:10 UTC | Jul 13, 09:25 UTC | 4h 15m |
| 2026-07-12 | SVA828 | - | Jul 12, 22:20 UTC | Jul 13, 03:15 UTC | 4h 55m |
| 2026-07-12 | SVA828 | - | Jul 12, 13:50 UTC | Jul 12, 21:00 UTC | 7h 10m |
| 2026-07-12 | SVA144 | - | Jul 12, 09:55 UTC | Jul 12, 13:45 UTC | 3h 50m |
| 2026-07-11 | SVA143 | - | Jul 11, 10:05 UTC | Jul 12, 05:10 UTC | 19h 5m |
| 2026-07-11 | SVA143 | LHR → CDG | Jul 11, 09:35 UTC | Jul 12, 05:10 UTC | 19h 35m |
| 2026-07-11 | SVA111 | - | Jul 11, 02:20 UTC | Jul 11, 06:01 UTC | 3h 40m |
| 2026-07-10 | SVA122 | - | Jul 10, 15:25 UTC | Jul 11, 02:15 UTC | 10h 50m |
| 2026-07-09 | SVA121 | DAC → LHR | Jul 9, 19:20 UTC | Jul 10, 12:50 UTC | 17h 30m |
| 2026-07-09 | SVA804 | JED → DAC | Jul 9, 12:25 UTC | Jul 9, 17:10 UTC | 4h 45m |
| 2026-07-08 | SVA804 | JED → DAC | Jul 8, 20:05 UTC | Jul 9, 17:10 UTC | 21h 5m |
| 2026-07-08 | SVA804 | JED → DAC | Jul 8, 18:05 UTC | Jul 9, 17:10 UTC | 23h 5m |
| 2026-07-08 | SVA122 | - | Jul 8, 16:05 UTC | Jul 9, 15:05 UTC | 23h 0m |
| 2026-07-08 | SVA122 | - | Jul 8, 15:55 UTC | Jul 9, 13:15 UTC | 21h 20m |
| 2026-07-08 | SVA121 | - | Jul 8, 08:10 UTC | Jul 8, 13:05 UTC | 4h 55m |
| 2026-07-07 | SVA121 | - | Jul 7, 16:05 UTC | Jul 8, 13:05 UTC | 21h 0m |
| 2026-07-07 | SVA121 | - | Jul 7, 14:05 UTC | Jul 8, 13:05 UTC | 23h 0m |
| 2026-07-07 | SVA121 | - | Jul 7, 13:40 UTC | Jul 8, 12:00 UTC | 22h 20m |
| 2026-07-07 | SVA760 | - | Jul 7, 08:10 UTC | Jul 7, 11:50 UTC | 3h 40m |
| 2026-07-06 | SVA760 | - | Jul 6, 10:05 UTC | Jul 7, 10:00 UTC | 23h 55m |
| 2026-07-06 | SVA807 | - | Jul 6, 05:40 UTC | Jul 6, 10:25 UTC | 4h 45m |
| 2026-07-05 | SVA806 | - | Jul 5, 22:45 UTC | Jul 6, 03:35 UTC | 4h 50m |
| 2026-07-04 | SVA144 | - | Jul 4, 09:50 UTC | Jul 4, 13:50 UTC | 4h 0m |
| 2026-07-03 | SVA143 | - | Jul 3, 10:10 UTC | Jul 4, 05:15 UTC | 19h 5m |
| 2026-07-03 | SVA143 | - | Jul 3, 08:05 UTC | Jul 4, 05:15 UTC | 21h 10m |
| 2026-07-02 | SVA862 | - | Jul 2, 20:30 UTC | Jul 3, 05:25 UTC | 8h 55m |
| 2026-07-01 | SVA122 | - | Jul 1, 15:45 UTC | Jul 1, 20:15 UTC | 4h 30m |
| 2026-06-30 | SVA121 | - | Jun 30, 18:05 UTC | Jul 1, 13:00 UTC | 18h 55m |
| 2026-06-30 | SVA121 | - | Jun 30, 16:05 UTC | Jul 1, 13:00 UTC | 20h 55m |
| 2026-06-30 | SVA121 | - | Jun 30, 15:45 UTC | Jul 1, 13:00 UTC | 21h 15m |
| 2026-06-30 | SVA121 | - | Jun 30, 08:35 UTC | Jun 30, 12:55 UTC | 4h 20m |
| 2026-06-29 | SVA121 | - | Jun 29, 14:14 UTC | Jun 30, 12:55 UTC | 22h 41m |
| 2026-06-29 | SVA121 | - | Jun 29, 12:05 UTC | Jun 30, 12:00 UTC | 23h 56m |
| 2026-06-29 | SVA144 | - | Jun 29, 10:15 UTC | Jun 30, 10:00 UTC | 23h 46m |
| 2026-06-28 | SVA143 | - | Jun 28, 10:04 UTC | Jun 29, 05:00 UTC | 18h 55m |
| 2026-06-27 | SVA143 | - | Jun 27, 10:05 UTC | Jun 28, 04:55 UTC | 18h 50m |
| 2026-06-27 | SVA143 | - | Jun 27, 09:50 UTC | Jun 28, 04:55 UTC | 19h 5m |
| 2026-06-27 | SVA111 | - | Jun 27, 01:15 UTC | Jun 27, 06:05 UTC | 4h 50m |
| 2026-06-26 | SVA111 | - | Jun 26, 09:00 UTC | Jun 27, 06:05 UTC | 21h 5m |
| 2026-06-26 | SVA111 | DEL → LHR | Jun 26, 06:25 UTC | Jun 27, 05:59 UTC | 23h 35m |
| 2026-06-25 | SVA756 | - | Jun 25, 10:04 UTC | Jun 26, 04:14 UTC | 18h 10m |
| 2026-06-25 | SVA756 | - | Jun 25, 08:04 UTC | Jun 26, 04:14 UTC | 20h 10m |
| 2026-06-25 | SVA756 | DAC → DEL | Jun 25, 07:39 UTC | Jun 26, 04:14 UTC | 20h 35m |
| 2026-06-24 | SVA808 | - | Jun 24, 11:39 UTC | Jun 25, 05:29 UTC | 17h 50m |
| 2026-06-24 | SVA819 | - | Jun 24, 10:49 UTC | Jun 24, 11:05 UTC | 15m |
| 2026-06-24 | SVA818 | - | Jun 24, 08:30 UTC | Jun 24, 08:45 UTC | 15m |
| 2026-06-24 | SVA818 | - | Jun 24, 00:30 UTC | Jun 24, 07:50 UTC | 7h 20m |
| 2026-06-21 | SVA736 | - | Jun 21, 11:15 UTC | Jun 21, 19:50 UTC | 8h 35m |
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-AK30 page for operator, model, and routing details .