sensors Mode-S transponder
71010F
ICAO 24-bit transponder address · allocated to Saudi Arabia
Currently assigned to HZ-AK37 · BOEING 777-300ER
- Hex
- 71010F
- Octal
- 34200417
- Decimal
- 7,405,839
- Country
- SA
- Tail
- HZ-AK37
- Type
- B77W
- Flights observed
- 140
- Distinct callsigns
- 20
- Country
- SA
- Last broadcast
- 1h ago
Current position
Country allocation
The ICAO 24-bit address 71010F 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 |
|---|---|---|---|
| SVA143 | Saudi Arabian Airlines | 21 | 2026-06-07 |
| SVA037 | - | 17 | 2026-07-05 |
| SVA023 | - | 16 | 2026-07-02 |
| SVA121 | - | 12 | 2026-07-11 |
| SVA144 | - | 10 | 2026-07-13 |
| SVA038 | - | 9 | 2026-07-06 |
| SVA111 | - | 8 | 2026-07-11 |
| SVA109 | Saudi Arabian Airlines | 6 | 2026-05-17 |
| SVA022 | - | 6 | 2026-07-02 |
| SVA036 | - | 5 | 2026-06-23 |
| SVA035 | - | 5 | 2026-06-23 |
| SVA122 | - | 4 | 2026-07-09 |
| SVA110 | - | 4 | 2026-07-12 |
| SVA105 | Saudi Arabian Airlines | 3 | 2026-07-07 |
| SVA042 | Saudi Arabian Airlines | 3 | 2026-06-21 |
| SVA021 | - | 3 | 2026-06-28 |
| SVA020 | - | 3 | 2026-06-29 |
| SVA041 | Saudi Arabian Airlines | 2 | 2026-06-20 |
| SVA560 | - | 1 | 2026-07-04 |
| SVA118 | Saudi Arabian Airlines | 1 | 2026-05-01 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | SVA144 | - | Jul 13, 09:55 UTC | Jul 14, 05:45 UTC | 19h 50m |
| 2026-07-12 | SVA110 | - | Jul 12, 09:50 UTC | Jul 13, 05:05 UTC | 19h 15m |
| 2026-07-11 | SVA111 | LHR → LHR | Jul 11, 15:30 UTC | Jul 12, 05:40 UTC | 14h 10m |
| 2026-07-11 | SVA121 | - | Jul 11, 07:40 UTC | Jul 11, 12:30 UTC | 4h 50m |
| 2026-07-09 | SVA122 | - | Jul 9, 15:15 UTC | Jul 9, 19:35 UTC | 4h 20m |
| 2026-07-08 | SVA121 | - | Jul 8, 17:50 UTC | Jul 9, 12:45 UTC | 18h 55m |
| 2026-07-08 | SVA121 | - | Jul 8, 16:55 UTC | Jul 9, 12:45 UTC | 19h 50m |
| 2026-07-07 | SVA105 | JED → LHR | Jul 7, 17:50 UTC | Jul 8, 13:45 UTC | 19h 55m |
| 2026-07-07 | SVA105 | JED → LHR | Jul 7, 15:50 UTC | Jul 8, 13:45 UTC | 21h 55m |
| 2026-07-07 | SVA105 | JED → LHR | Jul 7, 15:30 UTC | Jul 8, 13:45 UTC | 22h 15m |
| 2026-07-07 | SVA121 | - | Jul 7, 08:15 UTC | Jul 7, 13:20 UTC | 5h 5m |
| 2026-07-06 | SVA121 | - | Jul 6, 10:05 UTC | Jul 7, 09:45 UTC | 23h 40m |
| 2026-07-06 | SVA038 | - | Jul 6, 00:50 UTC | Jul 6, 10:30 UTC | 9h 40m |
| 2026-07-05 | SVA037 | - | Jul 5, 07:55 UTC | Jul 5, 19:45 UTC | 11h 50m |
| 2026-07-04 | SVA037 | - | Jul 4, 16:45 UTC | Jul 5, 13:05 UTC | 20h 20m |
| 2026-07-04 | SVA560 | - | Jul 4, 13:50 UTC | Jul 4, 15:00 UTC | 1h 10m |
| 2026-07-02 | SVA022 | - | Jul 2, 16:30 UTC | Jul 3, 02:15 UTC | 9h 45m |
| 2026-07-02 | SVA023 | - | Jul 2, 02:40 UTC | Jul 2, 13:40 UTC | 11h 0m |
| 2026-06-29 | SVA020 | - | Jun 29, 00:44 UTC | Jun 29, 09:34 UTC | 8h 50m |
| 2026-06-28 | SVA021 | - | Jun 28, 07:20 UTC | Jun 28, 18:14 UTC | 10h 55m |
| 2026-06-26 | SVA020 | - | Jun 26, 23:34 UTC | Jun 27, 09:09 UTC | 9h 35m |
| 2026-06-26 | SVA021 | - | Jun 26, 07:24 UTC | Jun 26, 18:24 UTC | 11h 0m |
| 2026-06-23 | SVA036 | - | Jun 23, 23:14 UTC | Jun 24, 09:24 UTC | 10h 10m |
| 2026-06-23 | SVA035 | - | Jun 23, 08:54 UTC | Jun 23, 19:29 UTC | 10h 35m |
| 2026-06-21 | SVA042 | LAX → JED | Jun 21, 04:49 UTC | Jun 21, 18:25 UTC | 13h 35m |
| 2026-06-20 | SVA041 | JED → LAX | Jun 20, 08:14 UTC | Jun 20, 22:30 UTC | 14h 15m |
| 2026-06-17 | SVA122 | LHR → RUH | Jun 17, 15:30 UTC | Jun 17, 19:10 UTC | 3h 40m |
| 2026-06-17 | SVA121 | AMM → LHR | Jun 17, 08:15 UTC | Jun 17, 12:35 UTC | 4h 20m |
| 2026-06-16 | SVA020 | - | Jun 16, 00:00 UTC | Jun 16, 08:30 UTC | 8h 30m |
| 2026-06-15 | SVA021 | - | Jun 15, 07:20 UTC | Jun 15, 18:29 UTC | 11h 10m |
| 2026-06-14 | SVA036 | IAD → JED | Jun 14, 07:50 UTC | Jun 15, 07:45 UTC | 23h 55m |
| 2026-06-13 | SVA036 | IAD → JED | Jun 13, 23:15 UTC | Jun 14, 08:55 UTC | 9h 40m |
| 2026-06-13 | SVA035 | - | Jun 13, 07:35 UTC | Jun 13, 19:25 UTC | 11h 50m |
| 2026-06-12 | SVA035 | - | Jun 12, 15:50 UTC | Jun 13, 13:10 UTC | 21h 19m |
| 2026-06-12 | SVA035 | - | Jun 12, 13:50 UTC | Jun 13, 13:10 UTC | 23h 19m |
| 2026-06-12 | SVA042 | LAX → JED | Jun 12, 12:25 UTC | Jun 13, 11:45 UTC | 23h 19m |
| 2026-06-12 | SVA042 | LAX → JED | Jun 12, 04:10 UTC | Jun 12, 16:30 UTC | 12h 20m |
| 2026-06-11 | SVA041 | JED → LAX | Jun 11, 08:20 UTC | Jun 11, 22:35 UTC | 14h 15m |
| 2026-06-09 | SVA022 | JFK → RUH | Jun 9, 16:45 UTC | Jun 10, 01:50 UTC | 9h 5m |
| 2026-06-09 | SVA023 | RUH → JFK | Jun 9, 02:30 UTC | Jun 9, 13:25 UTC | 10h 55m |
| 2026-06-08 | SVA023 | RUH → JFK | Jun 8, 11:50 UTC | Jun 9, 08:50 UTC | 21h 0m |
| 2026-06-08 | SVA023 | RUH → JFK | Jun 8, 09:55 UTC | Jun 9, 08:50 UTC | 22h 55m |
| 2026-06-07 | SVA143 | RUH → CDG | Jun 7, 09:50 UTC | Jun 8, 05:10 UTC | 19h 20m |
| 2026-06-07 | SVA143 | RUH → CDG | Jun 7, 09:25 UTC | Jun 8, 05:10 UTC | 19h 45m |
| 2026-06-06 | SVA111 | RUH → LHR | Jun 6, 11:49 UTC | Jun 7, 06:25 UTC | 18h 35m |
| 2026-06-06 | SVA144 | CDG → RUH | Jun 6, 10:00 UTC | Jun 7, 06:25 UTC | 20h 25m |
| 2026-06-05 | SVA143 | RUH → CDG | Jun 5, 09:50 UTC | Jun 6, 05:15 UTC | 19h 25m |
| 2026-06-04 | SVA143 | RUH → CDG | Jun 4, 09:50 UTC | Jun 5, 05:10 UTC | 19h 20m |
| 2026-06-04 | SVA143 | RUH → CDG | Jun 4, 01:20 UTC | Jun 4, 05:15 UTC | 3h 55m |
| 2026-06-02 | SVA144 | CDG → RUH | Jun 2, 10:45 UTC | Jun 2, 14:45 UTC | 4h 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-AK37 page for operator, model, and routing details .