sensors Mode-S transponder
7100B3
ICAO 24-bit transponder address · allocated to Saudi Arabia
Currently assigned to HZ-AK25 · BOEING 777-300ER
- Hex
- 7100B3
- Octal
- 34200263
- Decimal
- 7,405,747
- Country
- SA
- Tail
- HZ-AK25
- Type
- B77W
- Flights observed
- 185
- Distinct callsigns
- 20
- Country
- SA
- Last broadcast
- Jul 26, 16:25 UTC
Last known position
Country allocation
The ICAO 24-bit address 7100B3 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 |
|---|---|---|---|
| SVA798 | - | 20 | 2026-07-19 |
| SVA862 | Saudi Arabian Airlines | 13 | 2026-07-25 |
| SVA143 | Saudi Arabian Airlines | 9 | 2026-07-24 |
| SVA826 | - | 8 | 2026-06-15 |
| SVA372 | Saudi Arabian Airlines | 8 | 2026-06-12 |
| SVA819 | Saudi Arabian Airlines | 7 | 2026-05-21 |
| SVA373 | - | 7 | 2026-06-12 |
| SVA827 | Saudi Arabian Airlines | 6 | 2026-06-15 |
| SVA818 | Saudi Arabian Airlines | 6 | 2026-05-20 |
| SVA799 | Saudi Arabian Airlines | 6 | 2026-07-20 |
| SVA861 | Saudi Arabian Airlines | 4 | 2026-07-26 |
| SVA810 | - | 4 | 2026-06-22 |
| SVA341 | - | 4 | 2026-07-14 |
| SVA121 | - | 4 | 2026-07-21 |
| SVA111 | Saudi Arabian Airlines | 4 | 2026-07-22 |
| SVA110 | - | 4 | 2026-07-22 |
| SVA804 | Saudi Arabian Airlines | 3 | 2026-06-23 |
| SVA758 | Saudi Arabian Airlines | 3 | 2026-05-22 |
| SVA736 | - | 3 | 2026-07-05 |
| SVA5814 | - | 3 | 2026-06-08 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | SVA861 | MNL → RUH | Jul 26, 07:55 UTC | Jul 26, 16:25 UTC | 8h 30m |
| 2026-07-25 | SVA862 | RUH → MNL | Jul 25, 10:50 UTC | Jul 26, 05:40 UTC | 18h 50m |
| 2026-07-25 | SVA862 | RUH → MNL | Jul 25, 10:00 UTC | Jul 26, 05:40 UTC | 19h 40m |
| 2026-07-25 | SVA862 | RUH → MNL | Jul 25, 07:55 UTC | Jul 26, 05:40 UTC | 21h 45m |
| 2026-07-24 | SVA862 | RUH → MNL | Jul 24, 10:50 UTC | Jul 25, 05:40 UTC | 18h 50m |
| 2026-07-24 | SVA862 | RUH → MNL | Jul 24, 09:45 UTC | Jul 25, 05:40 UTC | 19h 55m |
| 2026-07-24 | SVA143 | RUH → CDG | Jul 24, 00:45 UTC | Jul 24, 05:15 UTC | 4h 30m |
| 2026-07-23 | SVA144 | - | Jul 23, 09:55 UTC | Jul 23, 13:55 UTC | 4h 0m |
| 2026-07-22 | SVA143 | RUH → CDG | Jul 22, 11:10 UTC | Jul 23, 05:25 UTC | 18h 15m |
| 2026-07-22 | SVA143 | RUH → CDG | Jul 22, 10:20 UTC | Jul 23, 05:25 UTC | 19h 5m |
| 2026-07-22 | SVA143 | RUH → CDG | Jul 22, 04:50 UTC | Jul 23, 04:45 UTC | 23h 55m |
| 2026-07-22 | SVA110 | - | Jul 22, 02:55 UTC | Jul 23, 02:45 UTC | 23h 50m |
| 2026-07-22 | SVA111 | RUH → LHR | Jul 22, 02:00 UTC | Jul 22, 14:15 UTC | 12h 15m |
| 2026-07-21 | SVA122 | - | Jul 21, 21:15 UTC | Jul 21, 21:30 UTC | 15m |
| 2026-07-21 | SVA122 | - | Jul 21, 15:50 UTC | Jul 21, 20:05 UTC | 4h 15m |
| 2026-07-21 | SVA121 | - | Jul 21, 07:45 UTC | Jul 21, 12:35 UTC | 4h 50m |
| 2026-07-20 | SVA799 | DAC → MED | Jul 20, 10:05 UTC | Jul 20, 14:35 UTC | 4h 30m |
| 2026-07-19 | SVA798 | - | Jul 19, 13:50 UTC | Jul 20, 07:45 UTC | 17h 55m |
| 2026-07-19 | SVA798 | - | Jul 19, 11:50 UTC | Jul 20, 07:45 UTC | 19h 55m |
| 2026-07-19 | SVA798 | - | Jul 19, 09:55 UTC | Jul 20, 07:45 UTC | 21h 50m |
| 2026-07-19 | SVA798 | - | Jul 19, 02:45 UTC | Jul 19, 07:40 UTC | 4h 55m |
| 2026-07-18 | SVA798 | - | Jul 18, 11:50 UTC | Jul 19, 07:40 UTC | 19h 50m |
| 2026-07-18 | SVA798 | - | Jul 18, 09:55 UTC | Jul 19, 07:40 UTC | 21h 45m |
| 2026-07-18 | SVA798 | - | Jul 18, 02:45 UTC | Jul 18, 07:35 UTC | 4h 51m |
| 2026-07-16 | SVA799 | DAC → MED | Jul 16, 10:04 UTC | Jul 16, 14:40 UTC | 4h 35m |
| 2026-07-15 | SVA798 | - | Jul 15, 12:50 UTC | Jul 16, 07:45 UTC | 18h 55m |
| 2026-07-15 | SVA798 | - | Jul 15, 10:50 UTC | Jul 16, 07:45 UTC | 20h 55m |
| 2026-07-15 | SVA799 | DAC → MED | Jul 15, 10:00 UTC | Jul 16, 06:45 UTC | 20h 45m |
| 2026-07-14 | SVA798 | - | Jul 14, 15:20 UTC | Jul 15, 07:50 UTC | 16h 29m |
| 2026-07-14 | SVA341 | - | Jul 14, 09:30 UTC | Jul 14, 11:10 UTC | 1h 40m |
| 2026-07-13 | SVA341 | - | Jul 13, 14:00 UTC | Jul 14, 11:10 UTC | 21h 10m |
| 2026-07-13 | SVA799 | DAC → MED | Jul 13, 10:50 UTC | Jul 14, 10:45 UTC | 23h 55m |
| 2026-07-13 | SVA799 | DAC → MED | Jul 13, 10:00 UTC | Jul 13, 14:30 UTC | 4h 30m |
| 2026-07-12 | SVA798 | - | Jul 12, 11:50 UTC | Jul 13, 07:35 UTC | 19h 45m |
| 2026-07-12 | SVA798 | - | Jul 12, 09:50 UTC | Jul 13, 07:35 UTC | 21h 45m |
| 2026-07-11 | SVA798 | - | Jul 11, 12:50 UTC | Jul 12, 07:35 UTC | 18h 45m |
| 2026-07-11 | SVA798 | - | Jul 11, 10:50 UTC | Jul 12, 07:35 UTC | 20h 45m |
| 2026-07-11 | SVA798 | - | Jul 11, 10:00 UTC | Jul 12, 07:35 UTC | 21h 35m |
| 2026-07-11 | SVA798 | - | Jul 11, 02:40 UTC | Jul 11, 07:40 UTC | 5h 0m |
| 2026-07-09 | SVA799 | DAC → MED | Jul 9, 09:50 UTC | Jul 9, 13:50 UTC | 4h 0m |
| 2026-07-08 | SVA798 | - | Jul 8, 12:50 UTC | Jul 9, 07:35 UTC | 18h 45m |
| 2026-07-08 | SVA798 | - | Jul 8, 10:50 UTC | Jul 9, 07:35 UTC | 20h 45m |
| 2026-07-08 | SVA798 | - | Jul 8, 10:25 UTC | Jul 9, 07:35 UTC | 21h 10m |
| 2026-07-07 | SVA798 | - | Jul 7, 13:00 UTC | Jul 8, 07:15 UTC | 18h 15m |
| 2026-07-06 | SVA122 | - | Jul 6, 15:30 UTC | Jul 7, 09:50 UTC | 18h 20m |
| 2026-07-05 | SVA121 | - | Jul 5, 19:35 UTC | Jul 6, 13:00 UTC | 17h 25m |
| 2026-07-05 | SVA121 | - | Jul 5, 17:25 UTC | Jul 6, 13:00 UTC | 19h 35m |
| 2026-07-05 | SVA736 | - | Jul 5, 12:35 UTC | Jul 5, 13:40 UTC | 1h 5m |
| 2026-07-02 | SVA861 | - | Jul 2, 08:20 UTC | Jul 2, 16:50 UTC | 8h 30m |
| 2026-07-01 | SVA862 | - | Jul 1, 10:50 UTC | Jul 2, 05:35 UTC | 18h 45m |
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-AK25 page for operator, model, and routing details .