sensors Mode-S transponder
01023C
ICAO 24-bit transponder address · allocated to Egypt
Currently assigned to SU-BUT · AIRBUS A-320neo
- Hex
- 01023C
- Octal
- 00201074
- Decimal
- 66,108
- Country
- EG
- Tail
- SU-BUT
- Type
- A20N
- Flights observed
- 193
- Distinct callsigns
- 20
- Country
- EG
- Last broadcast
- 16h ago
Last known position
Country allocation
The ICAO 24-bit address 01023C 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 |
|---|---|---|---|
| MSC2980 | - | 13 | 2026-06-19 |
| MSC2974 | - | 10 | 2026-06-28 |
| MSC2991 | - | 8 | 2026-06-30 |
| MSC2981 | - | 7 | 2026-06-26 |
| MSC2960 | - | 7 | 2026-07-13 |
| MSC2933 | - | 7 | 2026-07-11 |
| MSC2932 | - | 7 | 2026-06-17 |
| MSC2975 | - | 5 | 2026-06-29 |
| MSC2961 | - | 5 | 2026-07-13 |
| MSC2950 | Air Cairo | 5 | 2026-05-30 |
| MSC2990 | Air Cairo | 4 | 2026-05-21 |
| MSC2921 | Air Cairo | 4 | 2026-06-09 |
| MSC2920 | Air Cairo | 4 | 2026-04-28 |
| MSC3902 | - | 3 | 2026-06-28 |
| MSC3901 | Air Cairo | 3 | 2026-06-28 |
| MSC388 | Air Cairo | 3 | 2026-04-24 |
| MSC3701 | - | 3 | 2026-05-10 |
| MSC3062 | - | 3 | 2026-05-16 |
| MSC2992 | - | 3 | 2026-07-08 |
| MSC2976 | - | 3 | 2026-07-08 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | MSC171 | - | Jul 13, 19:55 UTC | Jul 13, 20:15 UTC | 20m |
| 2026-07-13 | MSC2961 | - | Jul 13, 13:40 UTC | Jul 13, 17:25 UTC | 3h 45m |
| 2026-07-13 | MSC2960 | NUE → BER | Jul 13, 01:45 UTC | Jul 13, 12:15 UTC | 10h 30m |
| 2026-07-12 | MSC2964 | BER → NUE | Jul 12, 13:40 UTC | Jul 13, 00:20 UTC | 10h 40m |
| 2026-07-11 | MSC2960 | - | Jul 11, 17:05 UTC | Jul 12, 12:15 UTC | 19h 10m |
| 2026-07-11 | MSC2960 | - | Jul 11, 16:05 UTC | Jul 12, 12:15 UTC | 20h 10m |
| 2026-07-11 | MSC2933 | HAJ → STR | Jul 11, 02:15 UTC | Jul 11, 14:10 UTC | 11h 55m |
| 2026-07-10 | MSC2938 | FRA → HAJ | Jul 10, 13:30 UTC | Jul 11, 00:30 UTC | 11h 0m |
| 2026-07-09 | MSC2940 | STR → FRA | Jul 9, 17:35 UTC | Jul 10, 11:40 UTC | 18h 5m |
| 2026-07-09 | MSC2952 | RMF → STR | Jul 9, 05:35 UTC | Jul 9, 15:45 UTC | 10h 10m |
| 2026-07-08 | MSC2976 | VIE → LEJ | Jul 8, 16:10 UTC | Jul 9, 03:50 UTC | 11h 40m |
| 2026-07-08 | MSC2992 | - | Jul 8, 11:45 UTC | Jul 8, 14:45 UTC | 3h 0m |
| 2026-07-07 | MSC2992 | - | Jul 7, 17:15 UTC | Jul 8, 14:45 UTC | 21h 30m |
| 2026-07-07 | MSC2992 | - | Jul 7, 15:05 UTC | Jul 8, 14:45 UTC | 23h 40m |
| 2026-07-07 | MSC2999 | MUC → RMF | Jul 7, 14:30 UTC | Jul 8, 13:00 UTC | 22h 30m |
| 2026-07-07 | MSC2987 | NUE → MUC | Jul 7, 00:20 UTC | Jul 7, 12:40 UTC | 12h 20m |
| 2026-07-06 | MSC2977 | LEJ → NUE | Jul 6, 11:30 UTC | Jul 6, 23:10 UTC | 11h 40m |
| 2026-07-05 | MSC2976 | - | Jul 5, 15:05 UTC | Jul 6, 09:55 UTC | 18h 50m |
| 2026-07-05 | MSC2976 | - | Jul 5, 12:55 UTC | Jul 6, 09:55 UTC | 21h 0m |
| 2026-07-04 | MSC2923 | ZRH → MUC | Jul 4, 18:20 UTC | Jul 5, 11:10 UTC | 16h 50m |
| 2026-07-04 | MSC2993 | VIE → ZRH | Jul 4, 06:35 UTC | Jul 4, 16:40 UTC | 10h 5m |
| 2026-07-03 | MSC3558 | BTS → VIE | Jul 3, 18:40 UTC | Jul 4, 05:10 UTC | 10h 30m |
| 2026-07-03 | MSC3557 | - | Jul 3, 14:40 UTC | Jul 3, 17:05 UTC | 2h 25m |
| 2026-07-02 | MSC3557 | - | Jul 2, 19:05 UTC | Jul 3, 17:05 UTC | 22h 0m |
| 2026-07-02 | MSC3618 | - | Jul 2, 17:20 UTC | Jul 3, 17:00 UTC | 23h 40m |
| 2026-07-02 | MSC3614 | - | Jul 2, 06:41 UTC | Jul 2, 16:10 UTC | 9h 29m |
| 2026-07-01 | MSC554 | PRG → POZ | Jul 1, 19:00 UTC | Jul 2, 05:00 UTC | 10h 0m |
| 2026-07-01 | MSC553 | - | Jul 1, 05:55 UTC | Jul 1, 16:55 UTC | 11h 0m |
| 2026-06-30 | MSC995 | - | Jun 30, 09:05 UTC | Jul 1, 04:20 UTC | 19h 15m |
| 2026-06-30 | MSC2991 | - | Jun 30, 07:05 UTC | Jul 1, 04:20 UTC | 21h 15m |
| 2026-06-30 | MSC2991 | - | Jun 30, 06:25 UTC | Jul 1, 04:20 UTC | 21h 55m |
| 2026-06-29 | MSC2975 | LEJ → VIE | Jun 29, 18:14 UTC | Jun 30, 04:35 UTC | 10h 21m |
| 2026-06-28 | MSC2974 | - | Jun 28, 21:04 UTC | Jun 29, 16:44 UTC | 19h 40m |
| 2026-06-28 | MSC2974 | - | Jun 28, 19:04 UTC | Jun 29, 16:44 UTC | 21h 40m |
| 2026-06-28 | MSC3902 | - | Jun 28, 17:44 UTC | Jun 29, 16:44 UTC | 23h 0m |
| 2026-06-28 | MSC3901 | AAR → AAR | Jun 28, 15:44 UTC | Jun 28, 16:00 UTC | 15m |
| 2026-06-28 | MSC2969 | - | Jun 28, 03:09 UTC | Jun 28, 13:59 UTC | 10h 50m |
| 2026-06-27 | MSC2975 | LEJ → PAD | Jun 27, 15:10 UTC | Jun 28, 02:05 UTC | 10h 55m |
| 2026-06-26 | MSC2974 | - | Jun 26, 19:04 UTC | Jun 27, 13:40 UTC | 18h 35m |
| 2026-06-26 | MSC2974 | - | Jun 26, 17:04 UTC | Jun 27, 13:40 UTC | 20h 35m |
| 2026-06-26 | MSC2981 | - | Jun 26, 16:30 UTC | Jun 27, 13:40 UTC | 21h 10m |
| 2026-06-26 | MSC2935 | HAJ → DUS | Jun 26, 02:00 UTC | Jun 26, 13:30 UTC | 11h 30m |
| 2026-06-25 | MSC2934 | VIE → HAJ | Jun 25, 13:24 UTC | Jun 26, 00:24 UTC | 11h 0m |
| 2026-06-25 | MSC2913 | - | Jun 25, 01:19 UTC | Jun 25, 11:54 UTC | 10h 35m |
| 2026-06-24 | MSC2912 | - | Jun 24, 07:30 UTC | Jun 24, 23:45 UTC | 16h 15m |
| 2026-06-24 | MSC3997 | - | Jun 24, 03:15 UTC | Jun 24, 04:59 UTC | 1h 45m |
| 2026-06-22 | MSC2931 | MUC → HRG | Jun 22, 14:34 UTC | Jun 22, 17:50 UTC | 3h 15m |
| 2026-06-22 | MSC2930 | - | Jun 22, 02:34 UTC | Jun 22, 12:54 UTC | 10h 20m |
| 2026-06-21 | MSC2908 | MUC → ERF | Jun 21, 16:19 UTC | Jun 22, 01:35 UTC | 9h 15m |
| 2026-06-21 | MSC2969 | - | Jun 21, 03:05 UTC | Jun 21, 13:50 UTC | 10h 45m |
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-BUT page for operator, model, and routing details .