sensors Mode-S transponder
01024E
ICAO 24-bit transponder address · allocated to Egypt
Currently assigned to SU-BUP · AIRBUS A-320neo
- Hex
- 01024E
- Octal
- 00201116
- Decimal
- 66,126
- Country
- EG
- Tail
- SU-BUP
- Type
- A20N
- Flights observed
- 157
- Distinct callsigns
- 20
- Country
- EG
- Last broadcast
- 49m ago
Current position
Country allocation
The ICAO 24-bit address 01024E 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 |
|---|---|---|---|
| MSC2960 | - | 10 | 2026-06-15 |
| MSC2980 | Air Cairo | 9 | 2026-06-07 |
| MSC2950 | Air Cairo | 8 | 2026-06-06 |
| MSC2990 | - | 7 | 2026-07-02 |
| MSC2912 | - | 6 | 2026-07-10 |
| MSC3905 | - | 5 | 2026-05-24 |
| MSC3615 | - | 5 | 2026-04-23 |
| MSC2981 | - | 5 | 2026-06-28 |
| MSC2933 | Air Cairo | 5 | 2026-05-06 |
| MSC2911 | - | 5 | 2026-07-05 |
| MSC2908 | Air Cairo | 5 | 2026-06-07 |
| MSC3616 | - | 4 | 2026-07-13 |
| MSC3601 | - | 4 | 2026-07-09 |
| MSC2991 | - | 4 | 2026-07-03 |
| MSC2932 | Air Cairo | 4 | 2026-05-05 |
| MSC2913 | - | 4 | 2026-07-12 |
| MSC2910 | - | 4 | 2026-07-05 |
| MSC2909 | Air Cairo | 4 | 2026-06-08 |
| MSC3901 | Air Cairo | 3 | 2026-05-31 |
| MSC2970 | Air Cairo | 3 | 2026-04-18 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | MSC2972 | - | Jul 14, 07:00 UTC | Jul 14, 07:30 UTC | 30m |
| 2026-07-13 | MSC3616 | - | Jul 13, 19:05 UTC | Jul 13, 22:25 UTC | 3h 20m |
| 2026-07-13 | MSC2921 | ZRH → WRO | Jul 13, 07:10 UTC | Jul 13, 17:45 UTC | 10h 35m |
| 2026-07-12 | MSC2920 | STR → ZRH | Jul 12, 14:35 UTC | Jul 13, 05:40 UTC | 15h 5m |
| 2026-07-12 | MSC2913 | CGN → STR | Jul 12, 01:10 UTC | Jul 12, 13:15 UTC | 12h 5m |
| 2026-07-11 | MSC2961 | BER → CGN | Jul 11, 13:45 UTC | Jul 11, 23:40 UTC | 9h 55m |
| 2026-07-11 | MSC2913 | CGN → BER | Jul 11, 01:25 UTC | Jul 11, 12:20 UTC | 10h 55m |
| 2026-07-10 | MSC2912 | - | Jul 10, 13:35 UTC | Jul 10, 23:35 UTC | 10h 1m |
| 2026-07-09 | MSC3602 | - | Jul 9, 19:15 UTC | Jul 10, 12:20 UTC | 17h 5m |
| 2026-07-09 | MSC3601 | - | Jul 9, 14:00 UTC | Jul 9, 17:40 UTC | 3h 40m |
| 2026-07-08 | MSC3601 | - | Jul 8, 20:30 UTC | Jul 9, 17:40 UTC | 21h 10m |
| 2026-07-06 | MSC806 | - | Jul 6, 16:55 UTC | Jul 6, 19:55 UTC | 3h 0m |
| 2026-07-06 | MSC805 | - | Jul 6, 11:30 UTC | Jul 6, 15:00 UTC | 3h 30m |
| 2026-07-05 | MSC2911 | - | Jul 5, 20:25 UTC | Jul 5, 21:05 UTC | 40m |
| 2026-07-05 | MSC2911 | - | Jul 5, 17:35 UTC | Jul 5, 20:20 UTC | 2h 45m |
| 2026-07-05 | MSC2910 | LEJ → BSL | Jul 5, 06:10 UTC | Jul 5, 16:25 UTC | 10h 15m |
| 2026-07-04 | MSC554 | PRG → LEJ | Jul 4, 18:05 UTC | Jul 5, 04:35 UTC | 10h 30m |
| 2026-07-04 | MSC553 | BEG → PRG | Jul 4, 08:20 UTC | Jul 4, 16:45 UTC | 8h 25m |
| 2026-07-03 | MSC552 | BTS → HRG | Jul 3, 18:45 UTC | Jul 4, 03:05 UTC | 8h 20m |
| 2026-07-03 | MSC2991 | VIE → BTS | Jul 3, 07:50 UTC | Jul 3, 17:30 UTC | 9h 40m |
| 2026-07-02 | MSC2991 | VIE → VIE | Jul 2, 13:55 UTC | Jul 3, 06:25 UTC | 16h 30m |
| 2026-07-02 | MSC2990 | - | Jul 2, 09:20 UTC | Jul 2, 12:10 UTC | 2h 50m |
| 2026-07-01 | MSC2990 | - | Jul 1, 13:35 UTC | Jul 2, 12:10 UTC | 22h 35m |
| 2026-07-01 | MSC2911 | - | Jul 1, 11:45 UTC | Jul 2, 11:30 UTC | 23h 45m |
| 2026-06-30 | MSC2910 | - | Jun 30, 13:35 UTC | Jul 1, 09:30 UTC | 19h 55m |
| 2026-06-30 | MSC2910 | - | Jun 30, 12:45 UTC | Jul 1, 09:30 UTC | 20h 45m |
| 2026-06-30 | MSC3805 | - | Jun 30, 08:50 UTC | Jun 30, 11:25 UTC | 2h 35m |
| 2026-06-28 | MSC2981 | - | Jun 28, 16:09 UTC | Jun 28, 20:14 UTC | 4h 5m |
| 2026-06-28 | MSC2919 | - | Jun 28, 03:09 UTC | Jun 28, 13:29 UTC | 10h 20m |
| 2026-06-27 | MSC2918 | MUC → CGN | Jun 27, 14:54 UTC | Jun 28, 01:44 UTC | 10h 50m |
| 2026-06-27 | MSC2935 | HAJ → MUC | Jun 27, 02:25 UTC | Jun 27, 12:39 UTC | 10h 15m |
| 2026-06-26 | MSC2934 | STR → HAJ | Jun 26, 13:40 UTC | Jun 27, 00:14 UTC | 10h 35m |
| 2026-06-25 | MSC3602 | - | Jun 25, 19:09 UTC | Jun 26, 12:14 UTC | 17h 5m |
| 2026-06-25 | MSC3601 | - | Jun 25, 14:09 UTC | Jun 25, 17:49 UTC | 3h 40m |
| 2026-06-24 | MSC3601 | - | Jun 24, 17:50 UTC | Jun 25, 17:30 UTC | 23h 40m |
| 2026-06-24 | MSC2931 | MUC → HRG | Jun 24, 15:35 UTC | Jun 25, 15:29 UTC | 23h 55m |
| 2026-06-24 | MSC2931 | MUC → HRG | Jun 24, 14:45 UTC | Jun 24, 18:05 UTC | 3h 20m |
| 2026-06-24 | MSC2930 | - | Jun 24, 09:45 UTC | Jun 24, 13:00 UTC | 3h 15m |
| 2026-06-23 | MSC2991 | - | Jun 23, 06:19 UTC | Jun 23, 09:20 UTC | 3h 0m |
| 2026-06-23 | MSC2990 | - | Jun 23, 01:25 UTC | Jun 23, 04:39 UTC | 3h 15m |
| 2026-06-21 | MSC2911 | BSL → HRG | Jun 21, 18:10 UTC | Jun 21, 21:54 UTC | 3h 45m |
| 2026-06-21 | MSC2975 | LEJ → BSL | Jun 21, 06:35 UTC | Jun 21, 16:49 UTC | 10h 15m |
| 2026-06-20 | MSC2974 | VIE → LEJ | Jun 20, 18:45 UTC | Jun 21, 04:39 UTC | 9h 55m |
| 2026-06-20 | MSC2990 | - | Jun 20, 07:44 UTC | Jun 20, 17:04 UTC | 9h 20m |
| 2026-06-19 | MSC2910 | HRG → BSL | Jun 19, 18:25 UTC | Jun 20, 06:05 UTC | 11h 40m |
| 2026-06-19 | MSC3557 | - | Jun 19, 13:54 UTC | Jun 19, 16:59 UTC | 3h 5m |
| 2026-06-18 | MSC3702 | - | Jun 18, 23:50 UTC | Jun 19, 07:59 UTC | 8h 9m |
| 2026-06-18 | MSC2913 | - | Jun 18, 01:30 UTC | Jun 18, 05:10 UTC | 3h 40m |
| 2026-06-17 | MSC2912 | VIE → CGN | Jun 17, 08:30 UTC | Jun 18, 00:25 UTC | 15h 55m |
| 2026-06-17 | MSC2990 | - | Jun 17, 04:00 UTC | Jun 17, 06:35 UTC | 2h 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-BUP page for operator, model, and routing details .