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
- 82
- Distinct callsigns
- 20
- Country
- SA
- Last broadcast
- 1h 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 |
|---|---|---|---|
| SVA808 | Saudi Arabian Airlines | 4 | 2026-05-28 |
| SVA341 | - | 4 | 2026-04-18 |
| SVA9730 | - | 3 | 2026-04-28 |
| SVA9313 | - | 3 | 2026-05-19 |
| SVA818 | Saudi Arabian Airlines | 3 | 2026-04-19 |
| SVA809 | Saudi Arabian Airlines | 3 | 2026-05-28 |
| SVA805 | Saudi Arabian Airlines | 3 | 2026-05-16 |
| SVA804 | Saudi Arabian Airlines | 3 | 2026-05-15 |
| SVA9513 | - | 2 | 2026-05-14 |
| SVA9441 | - | 2 | 2026-05-06 |
| SVA9429 | - | 2 | 2026-05-05 |
| SVA9413 | - | 2 | 2026-05-03 |
| SVA9345 | - | 2 | 2026-04-24 |
| SVA9321 | - | 2 | 2026-04-23 |
| SVA802 | Saudi Arabian Airlines | 2 | 2026-05-15 |
| SVA758 | Saudi Arabian Airlines | 2 | 2026-05-29 |
| SVA756 | - | 2 | 2026-04-13 |
| SVA734 | Saudi Arabian Airlines | 2 | 2026-05-24 |
| SVA726 | - | 2 | 2026-04-15 |
| SVA5363 | - | 2 | 2026-05-20 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | SVA759 | DEL → JED | May 29, 14:55 UTC | May 30, 03:45 UTC | 12h 50m |
| 2026-05-29 | SVA758 | JED → DEL | May 29, 12:35 UTC | May 29, 13:05 UTC | 30m |
| 2026-05-29 | SVA758 | JED → DEL | May 29, 08:50 UTC | May 29, 12:00 UTC | 3h 10m |
| 2026-05-28 | SVA809 | DAC → JED | May 28, 09:55 UTC | May 29, 09:10 UTC | 23h 15m |
| 2026-05-28 | SVA809 | DAC → JED | May 28, 07:30 UTC | May 28, 10:35 UTC | 3h 5m |
| 2026-05-28 | SVA808 | RUH → DAC | May 28, 02:25 UTC | May 28, 05:15 UTC | 2h 50m |
| 2026-05-25 | SVA704 | JED → KHI | May 25, 18:00 UTC | May 25, 18:20 UTC | 20m |
| 2026-05-24 | SVA735 | LHE → JED | May 24, 07:20 UTC | May 24, 07:50 UTC | 30m |
| 2026-05-24 | SVA734 | MED → LHE | May 24, 02:45 UTC | May 24, 05:25 UTC | 2h 40m |
| 2026-05-22 | SVA3779 | COK → RUH | May 22, 08:35 UTC | May 22, 09:05 UTC | 30m |
| 2026-05-22 | SVA3776 | RUH → COK | May 22, 05:05 UTC | May 22, 06:10 UTC | 1h 5m |
| 2026-05-21 | SVA3776 | RUH → COK | May 21, 08:25 UTC | May 22, 06:10 UTC | 21h 45m |
| 2026-05-20 | SVA5363 | - | May 20, 07:50 UTC | May 21, 03:15 UTC | 19h 25m |
| 2026-05-20 | SVA5363 | - | May 20, 07:25 UTC | May 21, 03:15 UTC | 19h 50m |
| 2026-05-19 | SVA9313 | - | May 19, 09:50 UTC | May 20, 04:35 UTC | 18h 45m |
| 2026-05-19 | SVA9313 | - | May 19, 07:00 UTC | May 20, 04:35 UTC | 21h 35m |
| 2026-05-19 | SVA9313 | - | May 19, 04:25 UTC | May 20, 03:45 UTC | 23h 20m |
| 2026-05-18 | SVA5911 | - | May 18, 19:35 UTC | May 19, 09:55 UTC | 14h 20m |
| 2026-05-18 | SVA9650 | - | May 18, 13:45 UTC | May 18, 17:25 UTC | 3h 40m |
| 2026-05-17 | SVA5737 | - | May 17, 18:35 UTC | May 17, 19:05 UTC | 30m |
| 2026-05-16 | SVA805 | DAC → JED | May 16, 21:05 UTC | May 17, 13:55 UTC | 16h 50m |
| 2026-05-16 | SVA805 | DAC → JED | May 16, 18:50 UTC | May 17, 13:55 UTC | 19h 5m |
| 2026-05-15 | SVA804 | JED → DAC | May 15, 23:10 UTC | May 16, 16:45 UTC | 17h 36m |
| 2026-05-15 | SVA804 | JED → DAC | May 15, 20:50 UTC | May 16, 16:45 UTC | 19h 56m |
| 2026-05-15 | SVA802 | JED → DAC | May 15, 03:10 UTC | May 15, 18:45 UTC | 15h 34m |
| 2026-05-14 | SVA5439 | - | May 14, 23:30 UTC | May 14, 23:40 UTC | 10m |
| 2026-05-14 | SVA9513 | - | May 14, 21:15 UTC | May 14, 21:25 UTC | 10m |
| 2026-05-14 | SVA9513 | - | May 14, 01:50 UTC | May 14, 20:40 UTC | 18h 50m |
| 2026-05-13 | SVA5199 | - | May 13, 22:05 UTC | May 13, 22:20 UTC | 15m |
| 2026-05-12 | SVA9504 | - | May 12, 23:15 UTC | May 13, 17:40 UTC | 18h 25m |
| 2026-05-12 | SVA803 | DAC → JED | May 12, 20:45 UTC | May 13, 17:40 UTC | 20h 55m |
| 2026-05-12 | SVA802 | JED → DAC | May 12, 02:50 UTC | May 12, 18:35 UTC | 15h 45m |
| 2026-05-11 | SVA807 | DAC → RUH | May 11, 05:30 UTC | May 11, 22:35 UTC | 17h 5m |
| 2026-05-10 | SVA806 | RUH → DAC | May 10, 22:55 UTC | May 11, 03:30 UTC | 4h 35m |
| 2026-05-07 | SVA5433 | - | May 7, 13:50 UTC | May 7, 14:30 UTC | 40m |
| 2026-05-06 | SVA9441 | - | May 6, 12:40 UTC | May 7, 07:30 UTC | 18h 49m |
| 2026-05-06 | SVA9441 | - | May 6, 08:30 UTC | May 7, 07:30 UTC | 22h 59m |
| 2026-05-05 | SVA9437 | - | May 5, 10:55 UTC | May 6, 05:30 UTC | 18h 35m |
| 2026-05-05 | SVA5251 | - | May 5, 06:45 UTC | May 5, 06:55 UTC | 10m |
| 2026-05-05 | SVA9429 | - | May 5, 03:45 UTC | May 5, 04:00 UTC | 15m |
| 2026-05-04 | SVA9429 | - | May 4, 19:50 UTC | May 5, 03:10 UTC | 7h 20m |
| 2026-05-03 | SVA5312 | - | May 3, 11:30 UTC | May 3, 18:30 UTC | 7h 0m |
| 2026-05-03 | SVA5312 | - | May 3, 10:40 UTC | May 3, 10:50 UTC | 10m |
| 2026-05-03 | SVA9413 | - | May 3, 05:35 UTC | May 3, 05:50 UTC | 15m |
| 2026-05-02 | SVA9413 | - | May 2, 21:50 UTC | May 3, 05:00 UTC | 7h 9m |
| 2026-05-01 | SVA5219 | - | May 1, 08:40 UTC | May 1, 16:40 UTC | 8h 0m |
| 2026-04-30 | SVA9400 | - | Apr 30, 21:20 UTC | May 1, 05:25 UTC | 8h 5m |
| 2026-04-29 | SVA5937 | - | Apr 29, 03:00 UTC | Apr 29, 06:00 UTC | 3h 0m |
| 2026-04-28 | SVA9730 | - | Apr 28, 21:15 UTC | Apr 29, 00:20 UTC | 3h 5m |
| 2026-04-27 | SVA9730 | - | Apr 27, 23:50 UTC | Apr 28, 23: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-AK31 page for operator, model, and routing details .