sensors Mode-S transponder
01022D
ICAO 24-bit transponder address · allocated to Egypt
Currently assigned to SU-BUL · AIRBUS A-320neo
- Hex
- 01022D
- Octal
- 00201055
- Decimal
- 66,093
- Country
- EG
- Tail
- SU-BUL
- Type
- A20N
- Flights observed
- 121
- Distinct callsigns
- 20
- Country
- EG
- Last broadcast
- 9h ago
Last known position
Country allocation
The ICAO 24-bit address 01022D 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 |
|---|---|---|---|
| MSC2912 | Air Cairo | 10 | 2026-05-06 |
| MSC2950 | Air Cairo | 6 | 2026-05-13 |
| MSC2930 | Air Cairo | 6 | 2026-05-10 |
| MSC2990 | Air Cairo | 5 | 2026-05-11 |
| MSC2960 | Air Cairo | 5 | 2026-05-02 |
| MSC2918 | Air Cairo | 5 | 2026-05-09 |
| MSC2908 | Air Cairo | 5 | 2026-05-12 |
| MSC2980 | Air Cairo | 4 | 2026-04-30 |
| MSC2961 | Air Cairo | 4 | 2026-04-26 |
| MSC2913 | Air Cairo | 4 | 2026-05-07 |
| MSC804 | Air Cairo | 3 | 2026-05-28 |
| MSC803 | Air Cairo | 3 | 2026-05-28 |
| MSC3717 | Air Cairo | 3 | 2026-04-24 |
| MSC3112 | - | 3 | 2026-05-29 |
| MSC3111 | - | 3 | 2026-05-29 |
| MSC2974 | Air Cairo | 3 | 2026-05-09 |
| MSC2951 | Air Cairo | 3 | 2026-05-13 |
| MSC2931 | - | 3 | 2026-04-13 |
| MSC2919 | Air Cairo | 3 | 2026-05-10 |
| MSC2909 | Air Cairo | 3 | 2026-04-13 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | MSC3112 | - | May 29, 12:05 UTC | May 29, 15:50 UTC | 3h 45m |
| 2026-05-29 | MSC3111 | - | May 29, 05:30 UTC | May 29, 09:50 UTC | 4h 20m |
| 2026-05-28 | MSC804 | MXP → CAI | May 28, 16:35 UTC | May 28, 19:35 UTC | 3h 0m |
| 2026-05-28 | MSC803 | CAI → MXP | May 28, 11:30 UTC | May 28, 14:50 UTC | 3h 20m |
| 2026-05-26 | MSC804 | MXP → CAI | May 26, 18:30 UTC | May 26, 21:44 UTC | 3h 15m |
| 2026-05-26 | MSC803 | CAI → MXP | May 26, 12:30 UTC | May 26, 15:49 UTC | 3h 20m |
| 2026-05-25 | MSC3108 | - | May 25, 12:10 UTC | May 25, 15:20 UTC | 3h 10m |
| 2026-05-25 | MSC3107 | - | May 25, 05:55 UTC | May 25, 10:10 UTC | 4h 15m |
| 2026-05-24 | MSC804 | MXP → CAI | May 24, 20:35 UTC | May 24, 23:46 UTC | 3h 11m |
| 2026-05-24 | MSC803 | CAI → MXP | May 24, 03:35 UTC | May 24, 18:40 UTC | 15h 5m |
| 2026-05-23 | MSC3110 | - | May 23, 12:25 UTC | May 24, 01:45 UTC | 13h 21m |
| 2026-05-23 | MSC3109 | - | May 23, 05:50 UTC | May 23, 10:00 UTC | 4h 10m |
| 2026-05-22 | MSC3112 | - | May 22, 11:35 UTC | May 22, 15:20 UTC | 3h 45m |
| 2026-05-22 | MSC3111 | - | May 22, 05:15 UTC | May 22, 09:35 UTC | 4h 20m |
| 2026-05-21 | MSC602 | CGN → CAI | May 21, 15:35 UTC | May 21, 19:05 UTC | 3h 30m |
| 2026-05-21 | MSC601 | CAI → CGN | May 21, 09:05 UTC | May 21, 13:01 UTC | 3h 55m |
| 2026-05-20 | MSC806 | MXP → CAI | May 20, 14:45 UTC | May 20, 17:40 UTC | 2h 55m |
| 2026-05-20 | MSC805 | CAI → MXP | May 20, 09:20 UTC | May 20, 12:50 UTC | 3h 30m |
| 2026-05-20 | MSC304 | SAW → CAI | May 20, 04:15 UTC | May 20, 05:15 UTC | 1h 1m |
| 2026-05-20 | MSC303 | CAI → SAW | May 20, 00:35 UTC | May 20, 02:10 UTC | 1h 35m |
| 2026-05-18 | MSC2808 | FCO → LXR | May 18, 12:35 UTC | May 18, 14:15 UTC | 1h 40m |
| 2026-05-18 | MSC2807 | CAI → FCO | May 18, 05:45 UTC | May 18, 10:55 UTC | 5h 10m |
| 2026-05-17 | MSC808 | FCO → SSH | May 17, 19:15 UTC | May 17, 21:55 UTC | 2h 40m |
| 2026-05-17 | MSC807 | SSH → FCO | May 17, 14:05 UTC | May 17, 17:35 UTC | 3h 30m |
| 2026-05-16 | MSC887 | - | May 16, 19:45 UTC | May 17, 09:00 UTC | 13h 15m |
| 2026-05-15 | MSC881 | SSH → ALA | May 15, 23:00 UTC | May 16, 12:31 UTC | 13h 31m |
| 2026-05-15 | MSC881 | SSH → ALA | May 15, 05:30 UTC | May 16, 01:50 UTC | 20h 19m |
| 2026-05-15 | MSC884 | NQZ → SSH | May 15, 04:05 UTC | May 16, 01:50 UTC | 21h 44m |
| 2026-05-14 | MSC884 | NQZ → SSH | May 14, 18:20 UTC | May 15, 06:35 UTC | 12h 15m |
| 2026-05-13 | MSC2951 | STR → HRG | May 13, 15:30 UTC | May 14, 07:35 UTC | 16h 5m |
| 2026-05-13 | MSC2950 | HRG → STR | May 13, 02:35 UTC | May 13, 13:35 UTC | 11h 0m |
| 2026-05-12 | MSC2908 | AAR → SSH | May 12, 07:05 UTC | May 13, 01:15 UTC | 18h 10m |
| 2026-05-11 | MSC2990 | HRG → VIE | May 11, 15:25 UTC | May 12, 05:25 UTC | 14h 1m |
| 2026-05-10 | MSC2930 | HRG → MUC | May 10, 19:19 UTC | May 11, 13:45 UTC | 18h 25m |
| 2026-05-10 | MSC2930 | HRG → MUC | May 10, 17:20 UTC | May 11, 13:45 UTC | 20h 25m |
| 2026-05-10 | MSC2930 | HRG → MUC | May 10, 16:59 UTC | May 11, 13:45 UTC | 20h 45m |
| 2026-05-10 | MSC2919 | CGN → HRG | May 10, 03:00 UTC | May 10, 15:35 UTC | 12h 35m |
| 2026-05-09 | MSC2918 | HRG → CGN | May 9, 15:15 UTC | May 10, 01:39 UTC | 10h 25m |
| 2026-05-09 | MSC2974 | HRG → LEJ | May 9, 02:20 UTC | May 9, 13:55 UTC | 11h 35m |
| 2026-05-08 | MSC2975 | LEJ → HRG | May 8, 14:35 UTC | May 9, 01:00 UTC | 10h 25m |
| 2026-05-08 | MSC2933 | HAJ → HRG | May 8, 02:44 UTC | May 8, 13:15 UTC | 10h 30m |
| 2026-05-07 | MSC2932 | HRG → HAJ | May 7, 13:40 UTC | May 8, 01:35 UTC | 11h 55m |
| 2026-05-07 | MSC2990 | HRG → VIE | May 7, 04:30 UTC | May 7, 12:05 UTC | 7h 35m |
| 2026-05-07 | MSC2913 | CGN → HRG | May 7, 01:35 UTC | May 7, 04:25 UTC | 2h 50m |
| 2026-05-06 | MSC2912 | HRG → CGN | May 6, 20:50 UTC | May 7, 00:15 UTC | 3h 25m |
| 2026-05-06 | MSC2912 | HRG → CGN | May 6, 03:20 UTC | May 7, 00:15 UTC | 20h 54m |
| 2026-05-06 | MSC2912 | HRG → CGN | May 6, 01:40 UTC | May 7, 00:15 UTC | 22h 34m |
| 2026-05-05 | MSC2912 | HRG → CGN | May 5, 06:40 UTC | May 6, 00:05 UTC | 17h 25m |
| 2026-05-04 | MSC2990 | HRG → VIE | May 4, 17:40 UTC | May 5, 05:10 UTC | 11h 31m |
| 2026-05-04 | MSC2817 | CAI → FCO | May 4, 10:50 UTC | May 4, 16:20 UTC | 5h 30m |
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-BUL page for operator, model, and routing details .