sensors Mode-S transponder
7100BF
ICAO 24-bit transponder address · allocated to Saudi Arabia
Currently assigned to HZ-AK31 · BOEING 777-300ER
- Hex
- 7100BF
- Octal
- 34200277
- Decimal
- 7,405,759
- Country
- SA
- Tail
- HZ-AK31
- Type
- B77W
- Flights observed
- 176
- Distinct callsigns
- 20
- Country
- SA
- Last broadcast
- 9h ago
Last known position
Country allocation
The ICAO 24-bit address 7100BF 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 |
|---|---|---|---|
| SVA805 | - | 10 | 2026-07-13 |
| SVA804 | Saudi Arabian Airlines | 10 | 2026-07-12 |
| SVA734 | - | 7 | 2026-07-03 |
| SVA818 | Saudi Arabian Airlines | 5 | 2026-05-30 |
| SVA809 | Saudi Arabian Airlines | 5 | 2026-05-30 |
| SVA808 | Saudi Arabian Airlines | 4 | 2026-05-28 |
| SVA735 | - | 4 | 2026-07-04 |
| SVA5218 | - | 4 | 2026-06-30 |
| SVA341 | - | 4 | 2026-04-18 |
| SVA9730 | - | 3 | 2026-04-28 |
| SVA9342 | - | 3 | 2026-06-29 |
| SVA9313 | - | 3 | 2026-05-19 |
| SVA738 | Saudi Arabian Airlines | 3 | 2026-07-01 |
| SVA736 | - | 3 | 2026-07-07 |
| SVA5800 | - | 3 | 2026-06-16 |
| SVA5398 | - | 3 | 2026-06-26 |
| SVA5260 | - | 3 | 2026-06-05 |
| SVA9747 | - | 2 | 2026-06-08 |
| SVA9513 | - | 2 | 2026-05-14 |
| SVA9504 | - | 2 | 2026-06-27 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | SVA805 | - | Jul 13, 19:30 UTC | Jul 13, 23:55 UTC | 4h 25m |
| 2026-07-12 | SVA804 | JED → DAC | Jul 12, 23:30 UTC | Jul 13, 17:40 UTC | 18h 10m |
| 2026-07-11 | SVA805 | - | Jul 11, 19:50 UTC | Jul 12, 15:01 UTC | 19h 10m |
| 2026-07-11 | SVA804 | JED → DAC | Jul 11, 12:30 UTC | Jul 11, 17:30 UTC | 5h 0m |
| 2026-07-10 | SVA817 | - | Jul 10, 09:40 UTC | Jul 10, 10:10 UTC | 30m |
| 2026-07-09 | SVA816 | - | Jul 9, 20:00 UTC | Jul 10, 04:05 UTC | 8h 5m |
| 2026-07-08 | SVA816 | - | Jul 8, 23:50 UTC | Jul 9, 23:30 UTC | 23h 40m |
| 2026-07-08 | SVA805 | - | Jul 8, 22:05 UTC | Jul 9, 20:15 UTC | 22h 10m |
| 2026-07-08 | SVA805 | - | Jul 8, 20:10 UTC | Jul 9, 00:45 UTC | 4h 35m |
| 2026-07-07 | SVA804 | JED → DAC | Jul 7, 23:50 UTC | Jul 8, 18:10 UTC | 18h 20m |
| 2026-07-07 | SVA804 | JED → DAC | Jul 7, 23:35 UTC | Jul 8, 18:10 UTC | 18h 35m |
| 2026-07-07 | SVA804 | JED → DAC | Jul 7, 18:50 UTC | Jul 8, 17:45 UTC | 22h 55m |
| 2026-07-07 | SVA804 | JED → DAC | Jul 7, 16:45 UTC | Jul 8, 15:45 UTC | 23h 0m |
| 2026-07-07 | SVA724 | - | Jul 7, 13:50 UTC | Jul 8, 13:45 UTC | 23h 55m |
| 2026-07-07 | SVA724 | - | Jul 7, 11:50 UTC | Jul 8, 08:10 UTC | 20h 20m |
| 2026-07-07 | SVA736 | - | Jul 7, 11:05 UTC | Jul 8, 08:10 UTC | 21h 5m |
| 2026-07-06 | SVA736 | - | Jul 6, 23:50 UTC | Jul 7, 23:45 UTC | 23h 55m |
| 2026-07-06 | SVA736 | - | Jul 6, 21:50 UTC | Jul 7, 19:30 UTC | 21h 40m |
| 2026-07-06 | SVA805 | - | Jul 6, 19:50 UTC | Jul 7, 19:30 UTC | 23h 40m |
| 2026-07-06 | SVA805 | - | Jul 6, 19:30 UTC | Jul 7, 17:00 UTC | 21h 30m |
| 2026-07-06 | SVA804 | JED → DAC | Jul 6, 00:40 UTC | Jul 6, 17:30 UTC | 16h 50m |
| 2026-07-04 | SVA735 | - | Jul 4, 07:50 UTC | Jul 4, 08:00 UTC | 10m |
| 2026-07-04 | SVA735 | - | Jul 4, 05:35 UTC | Jul 4, 06:05 UTC | 30m |
| 2026-07-03 | SVA734 | - | Jul 3, 07:55 UTC | Jul 4, 03:10 UTC | 19h 15m |
| 2026-07-03 | SVA734 | - | Jul 3, 06:05 UTC | Jul 4, 03:10 UTC | 21h 5m |
| 2026-07-03 | SVA734 | - | Jul 3, 05:45 UTC | Jul 4, 03:10 UTC | 21h 25m |
| 2026-07-03 | SVA734 | - | Jul 3, 00:40 UTC | Jul 3, 03:15 UTC | 2h 35m |
| 2026-07-01 | SVA739 | - | Jul 1, 22:05 UTC | Jul 1, 22:35 UTC | 30m |
| 2026-07-01 | SVA738 | JED → LHE | Jul 1, 17:05 UTC | Jul 1, 19:45 UTC | 2h 40m |
| 2026-06-30 | SVA738 | JED → LHE | Jun 30, 17:50 UTC | Jul 1, 17:45 UTC | 23h 55m |
| 2026-06-30 | SVA9401 | - | Jun 30, 17:25 UTC | Jun 30, 17:50 UTC | 25m |
| 2026-06-30 | SVA9401 | - | Jun 30, 13:40 UTC | Jun 30, 13:50 UTC | 10m |
| 2026-06-30 | SVA5218 | - | Jun 30, 11:35 UTC | Jun 30, 11:50 UTC | 15m |
| 2026-06-30 | SVA5218 | - | Jun 30, 03:10 UTC | Jun 30, 11:00 UTC | 7h 50m |
| 2026-06-29 | SVA5218 | - | Jun 29, 13:59 UTC | Jun 30, 11:00 UTC | 21h 1m |
| 2026-06-29 | SVA5218 | - | Jun 29, 12:20 UTC | Jun 30, 11:00 UTC | 22h 41m |
| 2026-06-29 | SVA9342 | - | Jun 29, 11:20 UTC | Jun 30, 07:30 UTC | 20h 11m |
| 2026-06-29 | SVA9342 | - | Jun 29, 07:59 UTC | Jun 30, 07:30 UTC | 23h 31m |
| 2026-06-29 | SVA9342 | - | Jun 29, 06:59 UTC | Jun 30, 03:30 UTC | 20h 31m |
| 2026-06-28 | SVA5484 | - | Jun 28, 20:50 UTC | Jun 29, 05:00 UTC | 8h 10m |
| 2026-06-27 | SVA9504 | - | Jun 27, 07:45 UTC | Jun 27, 07:55 UTC | 10m |
| 2026-06-26 | SVA5426 | - | Jun 26, 09:50 UTC | Jun 27, 05:19 UTC | 19h 30m |
| 2026-06-26 | SVA9464 | - | Jun 26, 06:04 UTC | Jun 26, 06:15 UTC | 10m |
| 2026-06-26 | SVA5398 | - | Jun 26, 03:50 UTC | Jun 26, 04:04 UTC | 15m |
| 2026-06-25 | SVA5398 | - | Jun 25, 19:49 UTC | Jun 26, 03:20 UTC | 7h 30m |
| 2026-06-24 | SVA5398 | - | Jun 24, 23:59 UTC | Jun 25, 23:24 UTC | 23h 25m |
| 2026-06-24 | SVA9430 | - | Jun 24, 17:14 UTC | Jun 25, 00:44 UTC | 7h 30m |
| 2026-06-24 | SVA5370 | - | Jun 24, 14:55 UTC | Jun 24, 15:09 UTC | 15m |
| 2026-06-23 | SVA9387 | - | Jun 23, 18:50 UTC | Jun 24, 11:05 UTC | 16h 15m |
| 2026-06-23 | SVA9387 | - | Jun 23, 15:09 UTC | Jun 23, 15:19 UTC | 10m |
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-AK31 page for operator, model, and routing details .