sensors Mode-S transponder
71002B
ICAO 24-bit transponder address · allocated to Saudi Arabia
Currently assigned to HZ-ARC · BOEING 787-9 Dreamliner
- Hex
- 71002B
- Octal
- 34200053
- Decimal
- 7,405,611
- Country
- SA
- Tail
- HZ-ARC
- Type
- B789
- Flights observed
- 235
- Distinct callsigns
- 20
- Country
- SA
- Last broadcast
- Jul 26, 21:05 UTC
Current position
Country allocation
The ICAO 24-bit address 71002B 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 |
|---|---|---|---|
| SVA870 | - | 27 | 2026-07-15 |
| SVA117 | Saudi Arabian Airlines | 22 | 2026-06-18 |
| SVA061 | - | 19 | 2026-07-07 |
| SVA375 | - | 16 | 2026-07-23 |
| SVA123 | - | 16 | 2026-06-20 |
| SVA119 | - | 13 | 2026-06-30 |
| SVA888 | Saudi Arabian Airlines | 10 | 2026-07-26 |
| SVA847 | Saudi Arabian Airlines | 10 | 2026-07-25 |
| SVA062 | - | 10 | 2026-07-07 |
| SVA130 | - | 7 | 2026-07-14 |
| SVA846 | Saudi Arabian Airlines | 6 | 2026-07-24 |
| SVA889 | - | 5 | 2026-07-22 |
| SVA871 | - | 5 | 2026-07-15 |
| SVA374 | Saudi Arabian Airlines | 5 | 2026-05-26 |
| SVA127 | Saudi Arabian Airlines | 5 | 2026-05-29 |
| SVA120 | Saudi Arabian Airlines | 5 | 2026-06-26 |
| SVA229 | - | 4 | 2026-07-11 |
| SVA131 | - | 4 | 2026-07-13 |
| SVA124 | - | 4 | 2026-06-21 |
| SVA884 | Saudi Arabian Airlines | 3 | 2026-07-20 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | SVA888 | RUH → PKX | Jul 26, 00:05 UTC | Jul 26, 21:05 UTC | 21h 1m |
| 2026-07-25 | SVA888 | RUH → PKX | Jul 25, 10:50 UTC | Jul 26, 05:55 UTC | 19h 5m |
| 2026-07-25 | SVA847 | BKK → RUH | Jul 25, 09:00 UTC | Jul 26, 05:55 UTC | 20h 55m |
| 2026-07-24 | SVA846 | RUH → BKK | Jul 24, 15:45 UTC | Jul 25, 06:55 UTC | 15h 10m |
| 2026-07-23 | SVA231 | - | Jul 23, 19:45 UTC | Jul 24, 13:55 UTC | 18h 10m |
| 2026-07-23 | SVA375 | - | Jul 23, 12:45 UTC | Jul 23, 17:45 UTC | 5h 0m |
| 2026-07-22 | SVA889 | - | Jul 22, 14:00 UTC | Jul 22, 22:15 UTC | 8h 15m |
| 2026-07-22 | SVA888 | RUH → PKX | Jul 22, 00:00 UTC | Jul 22, 05:25 UTC | 5h 25m |
| 2026-07-21 | SVA885 | - | Jul 21, 10:55 UTC | Jul 21, 16:45 UTC | 5h 50m |
| 2026-07-20 | SVA884 | RUH → CAN | Jul 20, 22:10 UTC | Jul 21, 04:10 UTC | 5h 59m |
| 2026-07-20 | SVA224 | - | Jul 20, 14:05 UTC | Jul 20, 17:50 UTC | 3h 45m |
| 2026-07-20 | SVA225 | JED → MAD | Jul 20, 07:20 UTC | Jul 20, 11:50 UTC | 4h 30m |
| 2026-07-19 | SVA888 | RUH → PKX | Jul 19, 00:50 UTC | Jul 19, 20:45 UTC | 19h 55m |
| 2026-07-19 | SVA888 | RUH → PKX | Jul 19, 00:40 UTC | Jul 19, 20:45 UTC | 20h 5m |
| 2026-07-18 | SVA888 | RUH → PKX | Jul 18, 10:50 UTC | Jul 19, 06:05 UTC | 19h 15m |
| 2026-07-18 | SVA888 | RUH → PKX | Jul 18, 10:40 UTC | Jul 19, 06:05 UTC | 19h 25m |
| 2026-07-17 | SVA884 | - | Jul 17, 08:49 UTC | Jul 18, 03:40 UTC | 18h 51m |
| 2026-07-17 | SVA884 | - | Jul 17, 06:54 UTC | Jul 18, 03:40 UTC | 20h 46m |
| 2026-07-17 | SVA377 | - | Jul 17, 00:40 UTC | Jul 17, 04:49 UTC | 4h 10m |
| 2026-07-15 | SVA871 | - | Jul 15, 15:55 UTC | Jul 15, 23:20 UTC | 7h 25m |
| 2026-07-15 | SVA870 | - | Jul 15, 03:40 UTC | Jul 15, 13:10 UTC | 9h 30m |
| 2026-07-14 | SVA870 | - | Jul 14, 08:50 UTC | Jul 15, 08:45 UTC | 23h 54m |
| 2026-07-14 | SVA130 | - | Jul 14, 07:00 UTC | Jul 15, 06:30 UTC | 23h 29m |
| 2026-07-13 | SVA131 | AMS → CDG | Jul 13, 14:40 UTC | Jul 14, 04:05 UTC | 13h 25m |
| 2026-07-12 | SVA215 | - | Jul 12, 17:01 UTC | Jul 13, 11:45 UTC | 18h 45m |
| 2026-07-12 | SVA215 | - | Jul 12, 14:50 UTC | Jul 13, 11:45 UTC | 20h 55m |
| 2026-07-12 | SVA215 | - | Jul 12, 14:40 UTC | Jul 13, 10:45 UTC | 20h 5m |
| 2026-07-11 | SVA229 | - | Jul 11, 18:25 UTC | Jul 12, 12:40 UTC | 18h 15m |
| 2026-07-11 | SVA840 | - | Jul 11, 09:05 UTC | Jul 11, 16:20 UTC | 7h 15m |
| 2026-07-10 | SVA887 | - | Jul 10, 04:50 UTC | Jul 10, 23:40 UTC | 18h 50m |
| 2026-07-10 | SVA886 | - | Jul 10, 03:30 UTC | Jul 10, 23:40 UTC | 20h 10m |
| 2026-07-09 | SVA228 | BCN → JED | Jul 9, 15:10 UTC | Jul 9, 18:35 UTC | 3h 25m |
| 2026-07-09 | SVA229 | - | Jul 9, 10:10 UTC | Jul 9, 13:00 UTC | 2h 50m |
| 2026-07-07 | SVA062 | - | Jul 7, 23:15 UTC | Jul 8, 08:40 UTC | 9h 25m |
| 2026-07-07 | SVA061 | - | Jul 7, 07:45 UTC | Jul 7, 18:35 UTC | 10h 50m |
| 2026-07-06 | SVA061 | - | Jul 6, 21:50 UTC | Jul 7, 18:35 UTC | 20h 45m |
| 2026-07-06 | SVA061 | - | Jul 6, 18:50 UTC | Jul 7, 18:35 UTC | 23h 45m |
| 2026-07-06 | SVA061 | - | Jul 6, 15:55 UTC | Jul 7, 12:45 UTC | 20h 50m |
| 2026-07-05 | SVA870 | - | Jul 5, 16:50 UTC | Jul 6, 12:45 UTC | 19h 55m |
| 2026-07-05 | SVA870 | - | Jul 5, 15:00 UTC | Jul 6, 12:45 UTC | 21h 45m |
| 2026-07-04 | SVA882 | - | Jul 4, 23:35 UTC | Jul 5, 05:00 UTC | 5h 25m |
| 2026-07-04 | SVA882 | - | Jul 4, 06:50 UTC | Jul 5, 05:00 UTC | 22h 10m |
| 2026-07-04 | SVA062 | - | Jul 4, 04:50 UTC | Jul 5, 04:45 UTC | 23h 55m |
| 2026-07-04 | SVA062 | - | Jul 4, 04:10 UTC | Jul 5, 02:15 UTC | 22h 5m |
| 2026-07-04 | SVA062 | - | Jul 4, 00:50 UTC | Jul 5, 00:30 UTC | 23h 40m |
| 2026-07-03 | SVA062 | - | Jul 3, 23:20 UTC | Jul 4, 08:05 UTC | 8h 45m |
| 2026-07-03 | SVA061 | - | Jul 3, 08:15 UTC | Jul 3, 19:10 UTC | 10h 55m |
| 2026-07-02 | SVA061 | - | Jul 2, 23:05 UTC | Jul 3, 19:10 UTC | 20h 5m |
| 2026-07-02 | SVA061 | - | Jul 2, 21:25 UTC | Jul 3, 19:10 UTC | 21h 45m |
| 2026-07-02 | SVA061 | - | Jul 2, 18:50 UTC | Jul 3, 18:45 UTC | 23h 55m |
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-ARC page for operator, model, and routing details .