sensors Mode-S transponder
010266
ICAO 24-bit transponder address · allocated to Egypt
Currently assigned to SU-BVO · AIRBUS A-320neo
- Hex
- 010266
- Octal
- 00201146
- Decimal
- 66,150
- Country
- EG
- Tail
- SU-BVO
- Type
- A20N
- Flights observed
- 208
- Distinct callsigns
- 20
- Country
- EG
- Last broadcast
- 1h ago
Last known position
Country allocation
The ICAO 24-bit address 010266 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 |
|---|---|---|---|
| MSC2976 | Air Cairo | 12 | 2026-05-24 |
| MSC2977 | Air Cairo | 9 | 2026-05-25 |
| MSC2932 | - | 9 | 2026-07-11 |
| MSC2939 | - | 8 | 2026-07-01 |
| MSC2982 | - | 6 | 2026-07-02 |
| MSC2960 | - | 6 | 2026-06-13 |
| MSC2933 | - | 6 | 2026-07-12 |
| MSC2913 | - | 6 | 2026-07-09 |
| MSC553 | Air Cairo | 5 | 2026-06-20 |
| MSC3557 | - | 5 | 2026-05-29 |
| MSC2992 | Air Cairo | 5 | 2026-05-20 |
| MSC2983 | Air Cairo | 5 | 2026-07-02 |
| MSC2952 | Air Cairo | 5 | 2026-05-23 |
| MSC2938 | Air Cairo | 5 | 2026-05-22 |
| MSC2912 | - | 5 | 2026-07-08 |
| MSC2980 | Air Cairo | 4 | 2026-06-09 |
| MSC2974 | - | 4 | 2026-07-10 |
| MSC2950 | Air Cairo | 4 | 2026-06-13 |
| MSC2941 | Air Cairo | 4 | 2026-05-26 |
| MSC2940 | Air Cairo | 4 | 2026-05-21 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | MSC2931 | MUC → HRG | Jul 13, 14:25 UTC | Jul 14, 09:30 UTC | 19h 5m |
| 2026-07-13 | MSC2909 | ERF → MUC | Jul 13, 02:20 UTC | Jul 13, 13:05 UTC | 10h 45m |
| 2026-07-12 | MSC2908 | - | Jul 12, 05:35 UTC | Jul 13, 01:10 UTC | 19h 35m |
| 2026-07-12 | MSC2908 | - | Jul 12, 03:35 UTC | Jul 13, 01:10 UTC | 21h 35m |
| 2026-07-12 | MSC2933 | HAJ → ERF | Jul 12, 02:01 UTC | Jul 13, 01:10 UTC | 23h 10m |
| 2026-07-11 | MSC2932 | MUC → HAJ | Jul 11, 14:35 UTC | Jul 12, 00:25 UTC | 9h 50m |
| 2026-07-10 | MSC2930 | - | Jul 10, 17:35 UTC | Jul 11, 12:40 UTC | 19h 5m |
| 2026-07-10 | MSC2930 | - | Jul 10, 15:35 UTC | Jul 11, 12:40 UTC | 21h 5m |
| 2026-07-10 | MSC2975 | LEJ → MUC | Jul 10, 14:35 UTC | Jul 11, 12:40 UTC | 22h 5m |
| 2026-07-10 | MSC2974 | - | Jul 10, 02:15 UTC | Jul 10, 13:00 UTC | 10h 45m |
| 2026-07-09 | MSC2932 | VIE → HAJ | Jul 9, 13:30 UTC | Jul 10, 00:55 UTC | 11h 25m |
| 2026-07-09 | MSC2913 | CGN → VIE | Jul 9, 01:35 UTC | Jul 9, 12:05 UTC | 10h 30m |
| 2026-07-08 | MSC2912 | - | Jul 8, 20:20 UTC | Jul 9, 00:15 UTC | 3h 55m |
| 2026-07-03 | MSC2999 | MUC → RMF | Jul 3, 16:20 UTC | Jul 3, 22:30 UTC | 6h 10m |
| 2026-07-03 | MSC2987 | NUE → MUC | Jul 3, 02:30 UTC | Jul 3, 14:25 UTC | 11h 55m |
| 2026-07-02 | MSC2986 | - | Jul 2, 22:10 UTC | Jul 3, 00:50 UTC | 2h 40m |
| 2026-07-02 | MSC2983 | DUS → RMF | Jul 2, 14:30 UTC | Jul 2, 18:25 UTC | 3h 55m |
| 2026-07-02 | MSC2982 | CGN → DUS | Jul 2, 01:40 UTC | Jul 2, 12:35 UTC | 10h 55m |
| 2026-07-01 | MSC2916 | - | Jul 1, 05:35 UTC | Jul 1, 23:55 UTC | 18h 20m |
| 2026-07-01 | MSC2916 | - | Jul 1, 03:35 UTC | Jul 1, 23:55 UTC | 20h 20m |
| 2026-07-01 | MSC2939 | HAJ → CGN | Jul 1, 02:15 UTC | Jul 1, 23:55 UTC | 21h 40m |
| 2026-07-01 | MSC2939 | HAJ → HAJ | Jul 1, 02:05 UTC | Jul 1, 02:10 UTC | 5m |
| 2026-06-30 | MSC2932 | BER → HAJ | Jun 30, 13:40 UTC | Jul 1, 00:40 UTC | 11h 0m |
| 2026-06-30 | MSC2913 | CGN → BER | Jun 30, 01:50 UTC | Jun 30, 12:00 UTC | 10h 10m |
| 2026-06-29 | MSC2991 | VIE → CGN | Jun 29, 13:30 UTC | Jun 29, 23:29 UTC | 10h 0m |
| 2026-06-29 | MSC2990 | - | Jun 29, 09:14 UTC | Jun 29, 12:00 UTC | 2h 45m |
| 2026-06-28 | MSC2990 | - | Jun 28, 15:34 UTC | Jun 29, 12:00 UTC | 20h 25m |
| 2026-06-28 | MSC2931 | MUC → HRG | Jun 28, 14:25 UTC | Jun 29, 12:00 UTC | 21h 35m |
| 2026-06-27 | MSC2991 | VIE → MUC | Jun 27, 18:29 UTC | Jun 28, 12:35 UTC | 18h 5m |
| 2026-06-27 | MSC2911 | - | Jun 27, 07:39 UTC | Jun 27, 16:55 UTC | 9h 15m |
| 2026-06-26 | MSC2910 | - | Jun 26, 18:09 UTC | Jun 27, 05:44 UTC | 11h 35m |
| 2026-06-26 | MSC551 | SSH → BTS | Jun 26, 08:00 UTC | Jun 26, 16:49 UTC | 8h 50m |
| 2026-06-25 | MSC2921 | ZRH → VIE | Jun 25, 18:59 UTC | Jun 26, 06:19 UTC | 11h 20m |
| 2026-06-25 | MSC2920 | - | Jun 25, 07:54 UTC | Jun 25, 17:20 UTC | 9h 25m |
| 2026-06-24 | MSC2995 | VIE → OMR | Jun 24, 18:20 UTC | Jun 25, 06:40 UTC | 12h 20m |
| 2026-06-24 | MSC2994 | - | Jun 24, 06:29 UTC | Jun 24, 16:54 UTC | 10h 25m |
| 2026-06-23 | MSC2931 | MUC → HRG | Jun 23, 14:39 UTC | Jun 24, 04:30 UTC | 13h 50m |
| 2026-06-23 | MSC2969 | PAD → MUC | Jun 23, 03:04 UTC | Jun 23, 13:05 UTC | 10h 0m |
| 2026-06-22 | MSC2968 | BER → PAD | Jun 22, 14:05 UTC | Jun 23, 01:59 UTC | 11h 55m |
| 2026-06-22 | MSC2913 | CGN → BER | Jun 22, 02:00 UTC | Jun 22, 12:30 UTC | 10h 30m |
| 2026-06-21 | MSC2912 | VIE → CGN | Jun 21, 13:29 UTC | Jun 21, 23:50 UTC | 10h 20m |
| 2026-06-20 | MSC554 | PRG → HRG | Jun 20, 17:59 UTC | Jun 21, 11:59 UTC | 18h 0m |
| 2026-06-20 | MSC553 | RMF → BTS | Jun 20, 13:04 UTC | Jun 20, 16:05 UTC | 3h 0m |
| 2026-06-20 | MSC996 | - | Jun 20, 06:14 UTC | Jun 20, 09:05 UTC | 2h 50m |
| 2026-06-19 | MSC552 | BTS → HRG | Jun 19, 18:14 UTC | Jun 20, 04:24 UTC | 10h 10m |
| 2026-06-19 | MSC551 | SSH → BTS | Jun 19, 07:49 UTC | Jun 19, 16:55 UTC | 9h 5m |
| 2026-06-18 | MSC2990 | - | Jun 18, 21:35 UTC | Jun 19, 06:29 UTC | 8h 54m |
| 2026-06-18 | MSC3609 | - | Jun 18, 07:55 UTC | Jun 18, 20:20 UTC | 12h 25m |
| 2026-06-17 | MSC2975 | LEJ → HRG | Jun 17, 14:50 UTC | Jun 18, 06:20 UTC | 15h 30m |
| 2026-06-17 | MSC2933 | HAJ → LEJ | Jun 17, 02:10 UTC | Jun 17, 12:55 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-BVO page for operator, model, and routing details .