sensors Mode-S transponder
01022F
ICAO 24-bit transponder address · allocated to Egypt
Currently assigned to SU-BUN · AIRBUS A-320neo
- Hex
- 01022F
- Octal
- 00201057
- Decimal
- 66,095
- Country
- EG
- Tail
- SU-BUN
- Type
- A20N
- Flights observed
- 116
- Distinct callsigns
- 20
- Country
- EG
- Last broadcast
- 5h ago
Last known position
Country allocation
The ICAO 24-bit address 01022F falls within the block assigned to Egypt (EG) by ICAO Annex 10, Volume III. Every aircraft registered in Egypt 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 |
|---|---|---|---|
| MSC902 | Air Cairo | 20 | 2026-05-22 |
| MSC901 | Air Cairo | 20 | 2026-05-21 |
| MSC912 | Air Cairo | 8 | 2026-05-20 |
| MSC911 | Air Cairo | 8 | 2026-05-15 |
| MSC883 | Air Cairo | 8 | 2026-05-27 |
| MSC907 | Air Cairo | 6 | 2026-05-10 |
| MSC807 | Air Cairo | 6 | 2026-05-24 |
| MSC910 | Air Cairo | 5 | 2026-05-14 |
| MSC909 | - | 4 | 2026-05-28 |
| MSC884 | Air Cairo | 4 | 2026-05-20 |
| MSC881 | Air Cairo | 3 | 2026-05-29 |
| MSC808 | Air Cairo | 3 | 2026-05-24 |
| MSC993 | Air Cairo | 2 | 2026-05-25 |
| MSC925 | Air Cairo | 2 | 2026-05-02 |
| MSC908 | Air Cairo | 2 | 2026-04-16 |
| MSC813 | Air Cairo | 2 | 2026-05-16 |
| MSC3062 | - | 2 | 2026-05-23 |
| MSC926 | Air Cairo | 1 | 2026-05-12 |
| MSC918 | Air Cairo | 1 | 2026-05-01 |
| MSC917 | Air Cairo | 1 | 2026-05-01 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | MSC881 | SSH → ALA | May 29, 22:50 UTC | May 30, 01:20 UTC | 2h 30m |
| 2026-05-28 | MSC909 | - | May 28, 13:10 UTC | May 29, 00:25 UTC | 11h 15m |
| 2026-05-27 | MSC883 | SSH → NQZ | May 27, 18:15 UTC | May 28, 06:45 UTC | 12h 30m |
| 2026-05-27 | MSC883 | SSH → NQZ | May 27, 05:49 UTC | May 28, 05:45 UTC | 23h 55m |
| 2026-05-27 | MSC883 | SSH → NQZ | May 27, 05:24 UTC | May 27, 20:40 UTC | 15h 15m |
| 2026-05-26 | MSC883 | SSH → NQZ | May 26, 19:50 UTC | May 27, 19:45 UTC | 23h 55m |
| 2026-05-26 | MSC883 | SSH → NQZ | May 26, 18:19 UTC | May 27, 06:34 UTC | 12h 15m |
| 2026-05-25 | MSC993 | SSH → EVN | May 25, 23:54 UTC | May 26, 05:54 UTC | 6h 0m |
| 2026-05-25 | MSC180 | - | May 25, 21:30 UTC | May 25, 21:45 UTC | 15m |
| 2026-05-24 | MSC808 | FCO → SSH | May 24, 19:10 UTC | May 25, 06:25 UTC | 11h 15m |
| 2026-05-24 | MSC807 | SSH → FCO | May 24, 03:20 UTC | May 24, 17:15 UTC | 13h 55m |
| 2026-05-23 | MSC3062 | - | May 23, 14:45 UTC | May 24, 01:40 UTC | 10h 56m |
| 2026-05-23 | MSC3062 | - | May 23, 12:50 UTC | May 23, 13:40 UTC | 50m |
| 2026-05-22 | MSC3061 | - | May 22, 22:25 UTC | May 23, 11:00 UTC | 12h 34m |
| 2026-05-22 | MSC3887 | - | May 22, 17:35 UTC | May 22, 20:40 UTC | 3h 5m |
| 2026-05-22 | MSC902 | LED → SSH | May 22, 05:25 UTC | May 22, 08:50 UTC | 3h 25m |
| 2026-05-21 | MSC901 | SSH → LED | May 21, 21:10 UTC | May 22, 02:10 UTC | 5h 0m |
| 2026-05-21 | MSC901 | SSH → LED | May 21, 05:50 UTC | May 22, 02:10 UTC | 20h 20m |
| 2026-05-21 | MSC901 | SSH → LED | May 21, 03:50 UTC | May 22, 02:10 UTC | 22h 20m |
| 2026-05-21 | MSC901 | SSH → LED | May 21, 03:35 UTC | May 22, 01:45 UTC | 22h 10m |
| 2026-05-20 | MSC884 | NQZ → SSH | May 20, 18:20 UTC | May 21, 06:15 UTC | 11h 55m |
| 2026-05-20 | MSC884 | NQZ → SSH | May 20, 07:50 UTC | May 21, 06:15 UTC | 22h 25m |
| 2026-05-20 | MSC912 | CEK → SSH | May 20, 05:50 UTC | May 21, 05:45 UTC | 23h 55m |
| 2026-05-20 | MSC912 | CEK → SSH | May 20, 04:45 UTC | May 21, 03:45 UTC | 23h 0m |
| 2026-05-20 | MSC912 | CEK → SSH | May 20, 00:00 UTC | May 20, 21:00 UTC | 21h 1m |
| 2026-05-19 | MSC912 | CEK → SSH | May 19, 22:10 UTC | May 20, 21:00 UTC | 22h 51m |
| 2026-05-19 | MSC912 | CEK → SSH | May 19, 20:35 UTC | May 20, 19:25 UTC | 22h 51m |
| 2026-05-18 | MSC901 | SSH → LED | May 18, 20:50 UTC | May 19, 08:00 UTC | 11h 10m |
| 2026-05-17 | MSC883 | SSH → NQZ | May 17, 22:45 UTC | May 18, 10:35 UTC | 11h 50m |
| 2026-05-17 | MSC883 | SSH → NQZ | May 17, 13:50 UTC | May 18, 10:35 UTC | 20h 45m |
| 2026-05-17 | MSC883 | SSH → NQZ | May 17, 12:30 UTC | May 18, 10:35 UTC | 22h 5m |
| 2026-05-16 | MSC813 | SSH → BRI | May 16, 20:25 UTC | May 17, 11:01 UTC | 14h 35m |
| 2026-05-16 | MSC813 | SSH → BRI | May 16, 13:51 UTC | May 17, 11:01 UTC | 21h 10m |
| 2026-05-16 | MSC909 | - | May 16, 11:11 UTC | May 17, 09:45 UTC | 22h 35m |
| 2026-05-16 | MSC912 | CEK → SSH | May 16, 04:10 UTC | May 16, 07:41 UTC | 3h 31m |
| 2026-05-15 | MSC911 | SSH → CEK | May 15, 20:20 UTC | May 16, 00:00 UTC | 3h 40m |
| 2026-05-15 | MSC3706 | - | May 15, 07:00 UTC | May 15, 09:30 UTC | 2h 30m |
| 2026-05-14 | MSC910 | UFA → SSH | May 14, 13:25 UTC | May 15, 05:25 UTC | 16h 0m |
| 2026-05-14 | MSC910 | UFA → SSH | May 14, 05:50 UTC | May 15, 05:25 UTC | 23h 35m |
| 2026-05-14 | MSC910 | UFA → SSH | May 14, 03:50 UTC | May 15, 03:45 UTC | 23h 55m |
| 2026-05-14 | MSC910 | UFA → SSH | May 14, 03:00 UTC | May 15, 00:05 UTC | 21h 5m |
| 2026-05-13 | MSC884 | NQZ → SSH | May 13, 20:05 UTC | May 14, 16:40 UTC | 20h 35m |
| 2026-05-13 | MSC884 | NQZ → SSH | May 13, 18:25 UTC | May 14, 16:40 UTC | 22h 15m |
| 2026-05-12 | MSC926 | KGD → SSH | May 12, 20:40 UTC | May 12, 23:40 UTC | 3h 0m |
| 2026-05-12 | MSC902 | LED → SSH | May 12, 03:25 UTC | May 12, 18:10 UTC | 14h 45m |
| 2026-05-11 | MSC902 | LED → SSH | May 11, 21:50 UTC | May 12, 18:10 UTC | 20h 20m |
| 2026-05-11 | MSC902 | LED → SSH | May 11, 20:40 UTC | May 12, 18:10 UTC | 21h 30m |
| 2026-05-10 | MSC907 | SSH → KZN | May 10, 20:14 UTC | May 11, 11:20 UTC | 15h 5m |
| 2026-05-10 | MSC808 | FCO → SSH | May 10, 18:49 UTC | May 10, 20:05 UTC | 1h 15m |
| 2026-05-09 | MSC807 | SSH → FCO | May 9, 21:50 UTC | May 10, 17:25 UTC | 19h 35m |
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 SU-BUN page for operator, model, and routing details .