sensors Mode-S transponder
010264
ICAO 24-bit transponder address · allocated to Egypt
Currently assigned to SU-BVM · AIRBUS A-320neo
- Hex
- 010264
- Octal
- 00201144
- Decimal
- 66,148
- Country
- EG
- Tail
- SU-BVM
- Type
- A20N
- Flights observed
- 220
- Distinct callsigns
- 20
- Country
- EG
- Last broadcast
- 1h ago
Last known position
Country allocation
The ICAO 24-bit address 010264 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 | - | 13 | 2026-06-17 |
| MSC2930 | - | 12 | 2026-07-06 |
| MSC2980 | - | 11 | 2026-07-14 |
| MSC2932 | - | 11 | 2026-07-12 |
| MSC2981 | - | 9 | 2026-07-13 |
| MSC2998 | Air Cairo | 8 | 2026-05-18 |
| MSC553 | - | 7 | 2026-06-27 |
| MSC2961 | Air Cairo | 7 | 2026-05-03 |
| MSC2951 | - | 7 | 2026-06-29 |
| MSC2912 | Air Cairo | 7 | 2026-06-14 |
| MSC554 | - | 6 | 2026-06-27 |
| MSC2974 | Air Cairo | 6 | 2026-04-30 |
| MSC2916 | Air Cairo | 6 | 2026-05-20 |
| MSC2913 | - | 6 | 2026-06-16 |
| MSC2950 | Air Cairo | 5 | 2026-05-25 |
| MSC2982 | Air Cairo | 4 | 2026-05-21 |
| MSC2933 | - | 4 | 2026-07-13 |
| MSC2931 | - | 4 | 2026-04-20 |
| MSC2918 | - | 4 | 2026-07-07 |
| MSC2908 | - | 4 | 2026-07-05 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | MSC2980 | - | Jul 14, 03:15 UTC | Jul 14, 13:00 UTC | 9h 45m |
| 2026-07-13 | MSC2968 | - | Jul 13, 21:50 UTC | Jul 14, 02:10 UTC | 4h 20m |
| 2026-07-13 | MSC2981 | - | Jul 13, 15:25 UTC | Jul 13, 19:20 UTC | 3h 55m |
| 2026-07-13 | MSC2933 | HAJ → DUS | Jul 13, 02:15 UTC | Jul 13, 14:10 UTC | 11h 55m |
| 2026-07-12 | MSC2932 | MUC → HAJ | Jul 12, 14:35 UTC | Jul 13, 01:05 UTC | 10h 30m |
| 2026-07-11 | MSC2991 | VIE → MUC | Jul 11, 18:20 UTC | Jul 12, 12:45 UTC | 18h 25m |
| 2026-07-11 | MSC2911 | - | Jul 11, 07:40 UTC | Jul 11, 17:00 UTC | 9h 20m |
| 2026-07-10 | MSC3622 | BUD → BSL | Jul 10, 14:15 UTC | Jul 11, 05:55 UTC | 15h 40m |
| 2026-07-10 | MSC3621 | - | Jul 10, 02:50 UTC | Jul 10, 12:45 UTC | 9h 55m |
| 2026-07-09 | MSC2968 | - | Jul 9, 15:25 UTC | Jul 10, 01:50 UTC | 10h 25m |
| 2026-07-09 | MSC2980 | CGN → DUS | Jul 9, 03:00 UTC | Jul 9, 13:30 UTC | 10h 30m |
| 2026-07-08 | MSC2981 | - | Jul 8, 15:20 UTC | Jul 9, 01:30 UTC | 10h 10m |
| 2026-07-08 | MSC2980 | CGN → DUS | Jul 8, 02:40 UTC | Jul 8, 13:50 UTC | 11h 10m |
| 2026-07-07 | MSC2918 | - | Jul 7, 15:05 UTC | Jul 8, 01:25 UTC | 10h 20m |
| 2026-07-07 | MSC2980 | - | Jul 7, 03:05 UTC | Jul 7, 13:35 UTC | 10h 30m |
| 2026-07-06 | MSC2968 | MUC → PAD | Jul 6, 14:25 UTC | Jul 7, 02:05 UTC | 11h 40m |
| 2026-07-06 | MSC2930 | ERF → MUC | Jul 6, 02:25 UTC | Jul 6, 13:05 UTC | 10h 40m |
| 2026-07-05 | MSC2908 | - | Jul 5, 18:40 UTC | Jul 6, 01:10 UTC | 6h 30m |
| 2026-07-05 | MSC2981 | - | Jul 5, 15:10 UTC | Jul 5, 18:05 UTC | 2h 55m |
| 2026-07-05 | MSC2919 | - | Jul 5, 03:10 UTC | Jul 5, 13:40 UTC | 10h 30m |
| 2026-07-04 | MSC2918 | - | Jul 4, 22:15 UTC | Jul 5, 01:40 UTC | 3h 25m |
| 2026-07-04 | MSC2981 | - | Jul 4, 15:30 UTC | Jul 4, 19:20 UTC | 3h 50m |
| 2026-07-04 | MSC2935 | HAJ → DUS | Jul 4, 02:20 UTC | Jul 4, 13:40 UTC | 11h 20m |
| 2026-07-03 | MSC2934 | - | Jul 3, 13:35 UTC | Jul 4, 00:35 UTC | 11h 0m |
| 2026-07-02 | MSC3602 | - | Jul 2, 19:10 UTC | Jul 3, 12:15 UTC | 17h 5m |
| 2026-07-02 | MSC3601 | - | Jul 2, 08:00 UTC | Jul 2, 17:40 UTC | 9h 40m |
| 2026-07-01 | MSC2995 | VIE → OMR | Jul 1, 19:05 UTC | Jul 2, 06:41 UTC | 11h 36m |
| 2026-07-01 | MSC2991 | VIE → VIE | Jul 1, 08:15 UTC | Jul 1, 17:05 UTC | 8h 50m |
| 2026-06-30 | MSC2981 | DUS → VIE | Jun 30, 15:45 UTC | Jul 1, 06:40 UTC | 14h 55m |
| 2026-06-30 | MSC2969 | - | Jun 30, 03:05 UTC | Jun 30, 13:35 UTC | 10h 30m |
| 2026-06-29 | MSC2951 | STR → PAD | Jun 29, 15:45 UTC | Jun 30, 01:35 UTC | 9h 51m |
| 2026-06-29 | MSC2933 | HAJ → STR | Jun 29, 02:09 UTC | Jun 29, 13:09 UTC | 11h 0m |
| 2026-06-28 | MSC2932 | - | Jun 28, 20:54 UTC | Jun 29, 00:49 UTC | 3h 55m |
| 2026-06-27 | MSC554 | - | Jun 27, 21:10 UTC | Jun 28, 20:54 UTC | 23h 45m |
| 2026-06-27 | MSC554 | - | Jun 27, 17:44 UTC | Jun 27, 21:15 UTC | 3h 30m |
| 2026-06-27 | MSC553 | - | Jun 27, 05:59 UTC | Jun 27, 16:14 UTC | 10h 15m |
| 2026-06-26 | MSC995 | - | Jun 26, 17:50 UTC | Jun 27, 04:05 UTC | 10h 15m |
| 2026-06-20 | MSC3778 | CDG → LXR | Jun 20, 17:14 UTC | Jun 20, 21:25 UTC | 4h 10m |
| 2026-06-20 | MSC3777 | LXR → CDG | Jun 20, 02:40 UTC | Jun 20, 15:39 UTC | 13h 0m |
| 2026-06-19 | MSC2932 | MUC → HAJ | Jun 19, 14:34 UTC | Jun 20, 00:49 UTC | 10h 15m |
| 2026-06-18 | MSC2930 | - | Jun 18, 17:05 UTC | Jun 19, 12:29 UTC | 19h 24m |
| 2026-06-18 | MSC2981 | DUS → HRG | Jun 18, 15:10 UTC | Jun 19, 12:29 UTC | 21h 19m |
| 2026-06-18 | MSC2919 | CGN → DUS | Jun 18, 02:55 UTC | Jun 18, 13:35 UTC | 10h 40m |
| 2026-06-17 | MSC2918 | BER → CGN | Jun 17, 14:00 UTC | Jun 18, 01:25 UTC | 11h 25m |
| 2026-06-17 | MSC2960 | - | Jun 17, 08:50 UTC | Jun 17, 12:35 UTC | 3h 45m |
| 2026-06-16 | MSC2981 | DUS → HRG | Jun 16, 15:05 UTC | Jun 16, 19:10 UTC | 4h 5m |
| 2026-06-16 | MSC2980 | - | Jun 16, 01:50 UTC | Jun 16, 13:34 UTC | 11h 45m |
| 2026-06-16 | MSC2913 | - | Jun 16, 01:30 UTC | Jun 16, 01:45 UTC | 15m |
| 2026-06-15 | MSC2991 | VIE → HRG | Jun 15, 13:30 UTC | Jun 16, 00:00 UTC | 10h 30m |
| 2026-06-15 | MSC2913 | CGN → VIE | Jun 15, 01:40 UTC | Jun 15, 12:15 UTC | 10h 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-BVM page for operator, model, and routing details .