sensors Mode-S transponder
010265
ICAO 24-bit transponder address · allocated to Egypt
Currently assigned to SU-BVN · AIRBUS A-320neo
- Hex
- 010265
- Octal
- 00201145
- Decimal
- 66,149
- Country
- EG
- Tail
- SU-BVN
- Type
- A20N
- Flights observed
- 219
- Distinct callsigns
- 20
- Country
- EG
- Last broadcast
- 3h ago
Current position
Country allocation
The ICAO 24-bit address 010265 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 | - | 18 | 2026-07-12 |
| MSC2916 | - | 11 | 2026-06-24 |
| MSC2998 | - | 10 | 2026-06-22 |
| MSC2933 | - | 8 | 2026-07-06 |
| MSC2912 | - | 8 | 2026-07-07 |
| MSC2974 | Air Cairo | 7 | 2026-04-23 |
| MSC2940 | - | 7 | 2026-06-25 |
| MSC2938 | - | 7 | 2026-06-26 |
| MSC2932 | - | 7 | 2026-07-10 |
| MSC2986 | - | 6 | 2026-07-13 |
| MSC2982 | - | 6 | 2026-06-25 |
| MSC2977 | - | 6 | 2026-06-21 |
| MSC2934 | Air Cairo | 6 | 2026-05-14 |
| MSC2983 | Air Cairo | 5 | 2026-06-25 |
| MSC2975 | - | 5 | 2026-04-17 |
| MSC2960 | Air Cairo | 5 | 2026-05-20 |
| MSC2939 | - | 5 | 2026-07-11 |
| MSC2980 | Air Cairo | 4 | 2026-05-15 |
| MSC2935 | Air Cairo | 4 | 2026-05-05 |
| MSC2930 | - | 4 | 2026-07-05 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | MSC2987 | NUE → FRA | Jul 13, 23:45 UTC | Jul 14, 11:40 UTC | 11h 55m |
| 2026-07-13 | MSC2986 | LEJ → NUE | Jul 13, 11:35 UTC | Jul 13, 22:25 UTC | 10h 50m |
| 2026-07-12 | MSC2976 | - | Jul 12, 15:20 UTC | Jul 13, 09:55 UTC | 18h 35m |
| 2026-07-12 | MSC2976 | - | Jul 12, 13:20 UTC | Jul 13, 09:55 UTC | 20h 35m |
| 2026-07-12 | MSC2976 | - | Jul 12, 13:10 UTC | Jul 13, 09:55 UTC | 20h 45m |
| 2026-07-11 | MSC2976 | - | Jul 11, 17:20 UTC | Jul 12, 11:40 UTC | 18h 20m |
| 2026-07-11 | MSC2976 | STR → LEJ | Jul 11, 16:20 UTC | Jul 12, 11:40 UTC | 19h 20m |
| 2026-07-11 | MSC2939 | HAJ → STR | Jul 11, 02:20 UTC | Jul 11, 14:15 UTC | 11h 55m |
| 2026-07-10 | MSC2932 | BER → HAJ | Jul 10, 13:25 UTC | Jul 11, 00:35 UTC | 11h 10m |
| 2026-07-09 | MSC3618 | - | Jul 9, 17:30 UTC | Jul 10, 12:00 UTC | 18h 30m |
| 2026-07-09 | MSC3617 | - | Jul 9, 06:25 UTC | Jul 9, 16:25 UTC | 10h 0m |
| 2026-07-08 | MSC3613 | - | Jul 8, 12:45 UTC | Jul 9, 05:10 UTC | 16h 25m |
| 2026-07-08 | MSC2913 | CGN → BSL | Jul 8, 01:35 UTC | Jul 8, 11:15 UTC | 9h 40m |
| 2026-07-07 | MSC2912 | - | Jul 7, 19:45 UTC | Jul 8, 00:10 UTC | 4h 25m |
| 2026-07-07 | MSC2912 | - | Jul 7, 03:20 UTC | Jul 8, 00:10 UTC | 20h 50m |
| 2026-07-07 | MSC2912 | CGN → CGN | Jul 7, 01:30 UTC | Jul 8, 00:10 UTC | 22h 40m |
| 2026-07-06 | MSC2912 | VIE → CGN | Jul 6, 13:35 UTC | Jul 6, 23:50 UTC | 10h 15m |
| 2026-07-06 | MSC2933 | HAJ → VIE | Jul 6, 02:20 UTC | Jul 6, 12:00 UTC | 9h 40m |
| 2026-07-05 | MSC2932 | MUC → HAJ | Jul 5, 14:30 UTC | Jul 6, 00:50 UTC | 10h 20m |
| 2026-07-05 | MSC2930 | - | Jul 5, 10:10 UTC | Jul 5, 13:00 UTC | 2h 50m |
| 2026-07-04 | MSC2930 | - | Jul 4, 13:20 UTC | Jul 5, 13:00 UTC | 23h 40m |
| 2026-07-04 | MSC3116 | - | Jul 4, 12:25 UTC | Jul 5, 11:15 UTC | 22h 50m |
| 2026-07-04 | MSC3115 | - | Jul 4, 05:05 UTC | Jul 4, 09:25 UTC | 4h 20m |
| 2026-07-03 | MSC3112 | - | Jul 3, 11:20 UTC | Jul 3, 15:00 UTC | 3h 40m |
| 2026-07-03 | MSC3111 | - | Jul 3, 05:20 UTC | Jul 3, 09:40 UTC | 4h 20m |
| 2026-06-29 | MSC232 | MJI → CAI | Jun 29, 14:09 UTC | Jun 29, 23:39 UTC | 9h 30m |
| 2026-06-29 | MSC231 | CAI → MJI | Jun 29, 11:29 UTC | Jun 29, 12:09 UTC | 40m |
| 2026-06-29 | MSC444 | - | Jun 29, 07:44 UTC | Jun 29, 08:04 UTC | 20m |
| 2026-06-29 | MSC443 | - | Jun 29, 02:25 UTC | Jun 29, 02:39 UTC | 15m |
| 2026-06-28 | MSC804 | MXP → CAI | Jun 28, 21:20 UTC | Jun 29, 00:49 UTC | 3h 30m |
| 2026-06-28 | MSC803 | - | Jun 28, 15:44 UTC | Jun 28, 19:09 UTC | 3h 25m |
| 2026-06-28 | MSC806 | - | Jun 28, 10:35 UTC | Jun 28, 13:49 UTC | 3h 15m |
| 2026-06-28 | MSC805 | - | Jun 28, 05:20 UTC | Jun 28, 08:44 UTC | 3h 25m |
| 2026-06-28 | MSC171 | - | Jun 28, 02:34 UTC | Jun 28, 03:00 UTC | 25m |
| 2026-06-27 | MSC2951 | - | Jun 27, 16:04 UTC | Jun 27, 19:45 UTC | 3h 40m |
| 2026-06-27 | MSC2933 | HAJ → STR | Jun 27, 02:14 UTC | Jun 27, 14:09 UTC | 11h 55m |
| 2026-06-26 | MSC2938 | FRA → HAJ | Jun 26, 13:45 UTC | Jun 27, 00:34 UTC | 10h 50m |
| 2026-06-25 | MSC2940 | - | Jun 25, 17:20 UTC | Jun 26, 11:34 UTC | 18h 15m |
| 2026-06-25 | MSC2940 | - | Jun 25, 15:20 UTC | Jun 26, 11:34 UTC | 20h 15m |
| 2026-06-25 | MSC2983 | DUS → RMF | Jun 25, 14:29 UTC | Jun 26, 11:34 UTC | 21h 5m |
| 2026-06-25 | MSC2982 | CGN → DUS | Jun 25, 01:24 UTC | Jun 25, 12:40 UTC | 11h 15m |
| 2026-06-24 | MSC2916 | - | Jun 24, 05:20 UTC | Jun 24, 23:40 UTC | 18h 20m |
| 2026-06-24 | MSC2916 | - | Jun 24, 03:19 UTC | Jun 24, 23:40 UTC | 20h 20m |
| 2026-06-24 | MSC2939 | HAJ → CGN | Jun 24, 02:05 UTC | Jun 24, 23:40 UTC | 21h 35m |
| 2026-06-23 | MSC2938 | MUC → HAJ | Jun 23, 14:39 UTC | Jun 24, 00:44 UTC | 10h 5m |
| 2026-06-22 | MSC2998 | - | Jun 22, 17:40 UTC | Jun 23, 12:45 UTC | 19h 5m |
| 2026-06-22 | MSC2998 | - | Jun 22, 15:20 UTC | Jun 23, 12:45 UTC | 21h 25m |
| 2026-06-22 | MSC2983 | DUS → RMF | Jun 22, 14:14 UTC | Jun 23, 12:45 UTC | 22h 30m |
| 2026-06-22 | MSC2982 | - | Jun 22, 01:29 UTC | Jun 22, 12:34 UTC | 11h 5m |
| 2026-06-21 | MSC2977 | LEJ → CGN | Jun 21, 13:20 UTC | Jun 21, 23:55 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-BVN page for operator, model, and routing details .