sensors Mode-S transponder
711504
ICAO 24-bit transponder address · allocated to Saudi Arabia
Currently assigned to HZ-FBK · AIRBUS A-320neo
- Hex
- 711504
- Octal
- 34212404
- Decimal
- 7,410,948
- Country
- SA
- Tail
- HZ-FBK
- Type
- A20N
- Flights observed
- 65
- Distinct callsigns
- 20
- Country
- SA
- Last broadcast
- 2d ago
Last known position
Country allocation
The ICAO 24-bit address 711504 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 |
|---|---|---|---|
| FAD807 | Rog-Air | 10 | 2026-05-16 |
| FAD808 | Rog-Air | 9 | 2026-05-16 |
| FAD775 | Rog-Air | 5 | 2026-04-22 |
| FAD771 | Rog-Air | 5 | 2026-04-20 |
| FAD574 | Rog-Air | 5 | 2026-05-25 |
| FAD776 | Rog-Air | 4 | 2026-04-22 |
| FAD573 | Rog-Air | 4 | 2026-05-25 |
| FAD812 | - | 2 | 2026-04-17 |
| FAD811 | Rog-Air | 2 | 2026-04-17 |
| FAD772 | Rog-Air | 2 | 2026-04-20 |
| FAD656 | Rog-Air | 2 | 2026-05-01 |
| FAD653 | Rog-Air | 2 | 2026-05-01 |
| FAD428 | - | 2 | 2026-04-18 |
| FAD762 | Rog-Air | 1 | 2026-05-13 |
| FAD761 | Rog-Air | 1 | 2026-05-13 |
| FAD756 | Rog-Air | 1 | 2026-05-15 |
| FAD755 | Rog-Air | 1 | 2026-05-07 |
| FAD6783 | - | 1 | 2026-05-18 |
| FAD6782 | - | 1 | 2026-05-18 |
| FAD655 | Rog-Air | 1 | 2026-04-30 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-30 | FAD615 | RUH → CAI | May 30, 21:55 UTC | May 30, 22:25 UTC | 30m |
| 2026-05-29 | FAD652 | ISB → RUH | May 29, 00:50 UTC | May 29, 06:20 UTC | 5h 30m |
| 2026-05-25 | FAD574 | IST → RUH | May 25, 18:50 UTC | May 25, 20:40 UTC | 1h 49m |
| 2026-05-25 | FAD573 | RUH → IST | May 25, 06:35 UTC | May 25, 16:15 UTC | 9h 40m |
| 2026-05-21 | FAD574 | IST → RUH | May 21, 18:05 UTC | May 21, 20:00 UTC | 1h 55m |
| 2026-05-20 | FAD574 | IST → RUH | May 20, 18:10 UTC | May 20, 20:00 UTC | 1h 50m |
| 2026-05-20 | FAD573 | RUH → IST | May 20, 14:40 UTC | May 20, 16:00 UTC | 1h 20m |
| 2026-05-18 | FAD6783 | - | May 18, 11:40 UTC | May 18, 12:00 UTC | 20m |
| 2026-05-18 | FAD6782 | - | May 18, 09:40 UTC | May 18, 10:05 UTC | 25m |
| 2026-05-16 | FAD808 | IST → JED | May 16, 20:50 UTC | May 16, 22:35 UTC | 1h 45m |
| 2026-05-16 | FAD807 | JED → IST | May 16, 05:15 UTC | May 16, 18:50 UTC | 13h 36m |
| 2026-05-15 | FAD756 | CAI → JED | May 15, 09:00 UTC | May 15, 09:10 UTC | 10m |
| 2026-05-14 | FAD808 | IST → JED | May 14, 20:25 UTC | May 15, 07:05 UTC | 10h 40m |
| 2026-05-14 | FAD807 | JED → IST | May 14, 09:45 UTC | May 14, 18:00 UTC | 8h 15m |
| 2026-05-13 | FAD762 | CAI → JED | May 13, 19:10 UTC | May 13, 19:20 UTC | 10m |
| 2026-05-13 | FAD761 | JED → CAI | May 13, 17:15 UTC | May 13, 17:35 UTC | 20m |
| 2026-05-12 | FAD808 | IST → JED | May 12, 21:05 UTC | May 13, 17:35 UTC | 20h 30m |
| 2026-05-12 | FAD808 | IST → JED | May 12, 20:45 UTC | May 13, 17:35 UTC | 20h 50m |
| 2026-05-12 | FAD807 | JED → IST | May 12, 16:50 UTC | May 12, 18:25 UTC | 1h 35m |
| 2026-05-11 | FAD807 | JED → IST | May 11, 21:05 UTC | May 12, 18:25 UTC | 21h 20m |
| 2026-05-11 | FAD807 | JED → IST | May 11, 20:20 UTC | May 12, 18:25 UTC | 22h 5m |
| 2026-05-11 | FAD808 | IST → JED | May 11, 17:05 UTC | May 12, 17:00 UTC | 23h 55m |
| 2026-05-11 | FAD807 | JED → IST | May 11, 16:20 UTC | May 11, 21:40 UTC | 5h 21m |
| 2026-05-10 | FAD808 | IST → JED | May 10, 21:04 UTC | May 11, 21:00 UTC | 23h 56m |
| 2026-05-10 | FAD808 | IST → JED | May 10, 20:09 UTC | May 11, 18:05 UTC | 21h 56m |
| 2026-05-10 | FAD807 | JED → IST | May 10, 09:00 UTC | May 10, 18:20 UTC | 9h 20m |
| 2026-05-09 | FAD807 | JED → IST | May 9, 16:30 UTC | May 10, 07:04 UTC | 14h 35m |
| 2026-05-09 | FAD807 | JED → IST | May 9, 11:05 UTC | May 10, 07:04 UTC | 20h 0m |
| 2026-05-08 | FAD808 | IST → JED | May 8, 16:15 UTC | May 8, 22:10 UTC | 5h 55m |
| 2026-05-07 | FAD755 | JED → CAI | May 7, 06:45 UTC | May 7, 07:05 UTC | 20m |
| 2026-05-05 | FAD808 | IST → JED | May 5, 20:30 UTC | May 5, 22:20 UTC | 1h 50m |
| 2026-05-05 | FAD807 | JED → IST | May 5, 10:55 UTC | May 5, 18:40 UTC | 7h 45m |
| 2026-05-04 | FAD574 | IST → RUH | May 4, 19:10 UTC | May 4, 20:50 UTC | 1h 40m |
| 2026-05-04 | FAD573 | RUH → IST | May 4, 15:20 UTC | May 4, 17:25 UTC | 2h 5m |
| 2026-05-04 | FAD613 | RUH → CAI | May 4, 07:45 UTC | May 4, 08:05 UTC | 20m |
| 2026-05-01 | FAD653 | RUH → SKT | May 1, 21:45 UTC | May 2, 06:20 UTC | 8h 36m |
| 2026-05-01 | FAD653 | RUH → SKT | May 1, 05:05 UTC | May 2, 03:15 UTC | 22h 10m |
| 2026-05-01 | FAD656 | LHE → RUH | May 1, 02:55 UTC | May 2, 00:45 UTC | 21h 50m |
| 2026-04-30 | FAD656 | LHE → RUH | Apr 30, 23:05 UTC | May 1, 22:55 UTC | 23h 50m |
| 2026-04-30 | FAD655 | RUH → LHE | Apr 30, 22:10 UTC | May 1, 06:15 UTC | 8h 5m |
| 2026-04-29 | FAD574 | IST → RUH | Apr 29, 18:15 UTC | Apr 29, 19:55 UTC | 1h 40m |
| 2026-04-29 | FAD573 | RUH → IST | Apr 29, 13:40 UTC | Apr 29, 15:45 UTC | 2h 5m |
| 2026-04-22 | FAD776 | CAI → MED | Apr 22, 20:00 UTC | Apr 22, 20:10 UTC | 10m |
| 2026-04-22 | FAD775 | MED → CAI | Apr 22, 18:10 UTC | Apr 22, 18:20 UTC | 10m |
| 2026-04-21 | FAD776 | CAI → MED | Apr 21, 20:05 UTC | Apr 22, 18:20 UTC | 22h 15m |
| 2026-04-21 | FAD775 | MED → CAI | Apr 21, 17:55 UTC | Apr 21, 18:15 UTC | 20m |
| 2026-04-20 | FAD775 | MED → CAI | Apr 20, 19:45 UTC | Apr 21, 18:15 UTC | 22h 30m |
| 2026-04-20 | FAD772 | CAI → MED | Apr 20, 07:05 UTC | Apr 20, 18:15 UTC | 11h 10m |
| 2026-04-20 | FAD771 | MED → CAI | Apr 20, 05:10 UTC | Apr 20, 05:25 UTC | 15m |
| 2026-04-19 | FAD771 | MED → CAI | Apr 19, 07:20 UTC | Apr 20, 05:25 UTC | 22h 5m |
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-FBK page for operator, model, and routing details .