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
- 245
- Distinct callsigns
- 20
- Country
- EG
- Last broadcast
- Jul 26, 21:15 UTC
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 | 17 | 2026-07-24 |
| MSC2950 | Air Cairo | 11 | 2026-06-12 |
| MSC2960 | - | 10 | 2026-06-24 |
| MSC2980 | - | 9 | 2026-06-27 |
| MSC2930 | - | 9 | 2026-07-10 |
| MSC2913 | - | 9 | 2026-07-16 |
| MSC2961 | - | 8 | 2026-06-26 |
| MSC2990 | - | 6 | 2026-07-07 |
| MSC2975 | Air Cairo | 6 | 2026-07-19 |
| MSC2974 | - | 6 | 2026-07-18 |
| MSC2931 | Air Cairo | 6 | 2026-07-16 |
| MSC2919 | - | 6 | 2026-07-12 |
| MSC2918 | - | 6 | 2026-06-30 |
| MSC2981 | - | 5 | 2026-07-12 |
| MSC2933 | - | 5 | 2026-07-17 |
| MSC2908 | Air Cairo | 5 | 2026-05-12 |
| MSC884 | Air Cairo | 4 | 2026-06-07 |
| MSC3111 | - | 4 | 2026-06-05 |
| MSC3109 | - | 4 | 2026-06-06 |
| MSC2972 | Air Cairo | 4 | 2026-07-20 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | MSC3612 | - | Jul 26, 18:40 UTC | Jul 26, 21:15 UTC | 2h 35m |
| 2026-07-26 | MSC3611 | - | Jul 26, 07:30 UTC | Jul 26, 17:20 UTC | 9h 50m |
| 2026-07-25 | MSC3778 | CDG → LXR | Jul 25, 14:10 UTC | Jul 26, 06:10 UTC | 16h 0m |
| 2026-07-25 | MSC3777 | LXR → CDG | Jul 25, 01:35 UTC | Jul 25, 12:20 UTC | 10h 45m |
| 2026-07-24 | MSC2912 | HRG → CGN | Jul 24, 14:15 UTC | Jul 25, 00:25 UTC | 10h 10m |
| 2026-07-23 | MSC3618 | - | Jul 23, 17:25 UTC | Jul 24, 12:45 UTC | 19h 20m |
| 2026-07-23 | MSC3617 | - | Jul 23, 07:00 UTC | Jul 23, 16:20 UTC | 9h 20m |
| 2026-07-22 | MSC3613 | LEJ → POZ | Jul 22, 14:30 UTC | Jul 23, 04:55 UTC | 14h 25m |
| 2026-07-22 | MSC2909 | ERF → HRG | Jul 22, 02:05 UTC | Jul 22, 12:50 UTC | 10h 45m |
| 2026-07-21 | MSC2973 | LEJ → ERF | Jul 21, 12:40 UTC | Jul 22, 00:55 UTC | 12h 15m |
| 2026-07-20 | MSC2972 | RMF → LEJ | Jul 20, 19:10 UTC | Jul 21, 11:05 UTC | 15h 54m |
| 2026-07-20 | MSC3614 | - | Jul 20, 06:20 UTC | Jul 20, 17:35 UTC | 11h 15m |
| 2026-07-19 | MSC2911 | BSL → HRG | Jul 19, 18:05 UTC | Jul 20, 04:40 UTC | 10h 35m |
| 2026-07-19 | MSC2975 | LEJ → HRG | Jul 19, 06:15 UTC | Jul 19, 16:05 UTC | 9h 50m |
| 2026-07-18 | MSC2974 | VIE → LEJ | Jul 18, 18:20 UTC | Jul 19, 04:10 UTC | 9h 50m |
| 2026-07-18 | MSC2911 | BSL → HRG | Jul 18, 07:50 UTC | Jul 18, 17:05 UTC | 9h 15m |
| 2026-07-17 | MSC2910 | HRG → BSL | Jul 17, 15:15 UTC | Jul 18, 05:50 UTC | 14h 36m |
| 2026-07-17 | MSC2933 | HAJ → DUS | Jul 17, 02:25 UTC | Jul 17, 13:29 UTC | 11h 5m |
| 2026-07-16 | MSC2932 | - | Jul 16, 20:29 UTC | Jul 17, 01:00 UTC | 4h 30m |
| 2026-07-16 | MSC2931 | MUC → HRG | Jul 16, 14:50 UTC | Jul 16, 18:00 UTC | 3h 10m |
| 2026-07-16 | MSC2913 | - | Jul 16, 01:45 UTC | Jul 16, 13:00 UTC | 11h 15m |
| 2026-07-15 | MSC2912 | - | Jul 15, 06:00 UTC | Jul 16, 00:30 UTC | 18h 30m |
| 2026-07-14 | MSC2921 | - | Jul 14, 17:00 UTC | Jul 15, 04:15 UTC | 11h 14m |
| 2026-07-14 | MSC2920 | VIE → ZRH | Jul 14, 06:30 UTC | Jul 14, 15:50 UTC | 9h 20m |
| 2026-07-13 | MSC2975 | LEJ → VIE | Jul 13, 18:10 UTC | Jul 14, 05:00 UTC | 10h 50m |
| 2026-07-13 | MSC2974 | POZ → LEJ | Jul 13, 06:15 UTC | Jul 13, 16:25 UTC | 10h 10m |
| 2026-07-13 | MSC3613 | - | Jul 13, 01:01 UTC | Jul 13, 04:35 UTC | 3h 35m |
| 2026-07-12 | MSC2981 | - | Jul 12, 16:30 UTC | Jul 12, 20:15 UTC | 3h 45m |
| 2026-07-12 | MSC2919 | CGN → DUS | Jul 12, 03:10 UTC | Jul 12, 13:30 UTC | 10h 20m |
| 2026-07-11 | MSC2975 | LEJ → CGN | Jul 11, 15:00 UTC | Jul 12, 01:30 UTC | 10h 30m |
| 2026-07-11 | MSC2935 | HAJ → LEJ | Jul 11, 01:45 UTC | Jul 11, 13:40 UTC | 11h 55m |
| 2026-07-10 | MSC2934 | - | Jul 10, 20:25 UTC | Jul 11, 00:25 UTC | 4h 0m |
| 2026-07-10 | MSC2931 | MUC → HRG | Jul 10, 15:00 UTC | Jul 10, 18:20 UTC | 3h 20m |
| 2026-07-10 | MSC2930 | - | Jul 10, 01:20 UTC | Jul 10, 12:50 UTC | 11h 30m |
| 2026-07-09 | MSC2971 | - | Jul 9, 11:50 UTC | Jul 9, 23:45 UTC | 11h 55m |
| 2026-07-09 | MSC2970 | - | Jul 9, 06:50 UTC | Jul 9, 10:30 UTC | 3h 40m |
| 2026-07-07 | MSC2921 | - | Jul 7, 17:00 UTC | Jul 7, 20:30 UTC | 3h 30m |
| 2026-07-07 | MSC2920 | - | Jul 7, 09:05 UTC | Jul 7, 15:40 UTC | 6h 35m |
| 2026-07-07 | MSC2991 | - | Jul 7, 06:15 UTC | Jul 7, 08:25 UTC | 2h 10m |
| 2026-07-07 | MSC2990 | - | Jul 7, 01:50 UTC | Jul 7, 04:50 UTC | 3h 0m |
| 2026-07-06 | MSC170 | - | Jul 6, 23:15 UTC | Jul 6, 23:30 UTC | 15m |
| 2026-07-05 | MSC171 | - | Jul 5, 03:30 UTC | Jul 5, 03:45 UTC | 15m |
| 2026-07-04 | MSC3778 | CDG → LXR | Jul 4, 15:20 UTC | Jul 4, 18:20 UTC | 3h 0m |
| 2026-07-04 | MSC3777 | - | Jul 4, 09:55 UTC | Jul 4, 13:20 UTC | 3h 25m |
| 2026-07-04 | MSC2913 | - | Jul 4, 01:30 UTC | Jul 4, 05:10 UTC | 3h 40m |
| 2026-07-03 | MSC2912 | - | Jul 3, 14:15 UTC | Jul 3, 23:50 UTC | 9h 35m |
| 2026-07-03 | MSC2969 | - | Jul 3, 03:05 UTC | Jul 3, 12:40 UTC | 9h 35m |
| 2026-07-02 | MSC2971 | - | Jul 2, 11:50 UTC | Jul 3, 01:50 UTC | 14h 0m |
| 2026-07-01 | MSC2970 | DUS → HAM | Jul 1, 16:55 UTC | Jul 2, 10:05 UTC | 17h 10m |
| 2026-07-01 | MSC2919 | CGN → DUS | Jul 1, 03:25 UTC | Jul 1, 14:50 UTC | 11h 25m |
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 .