sensors Mode-S transponder
01025C
ICAO 24-bit transponder address · allocated to Egypt
Currently assigned to SU-BVK · AIRBUS A-320neo
- Hex
- 01025C
- Octal
- 00201134
- Decimal
- 66,140
- Country
- EG
- Tail
- SU-BVK
- Type
- A20N
- Flights observed
- 243
- Distinct callsigns
- 20
- Country
- EG
- Last broadcast
- Jul 26, 22:05 UTC
Current position
Country allocation
The ICAO 24-bit address 01025C 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 |
|---|---|---|---|
| MSC901 | - | 18 | 2026-07-08 |
| MSC882 | - | 18 | 2026-07-09 |
| MSC881 | - | 17 | 2026-06-23 |
| MSC884 | - | 12 | 2026-06-28 |
| MSC925 | - | 10 | 2026-07-07 |
| MSC905 | Air Cairo | 9 | 2026-07-06 |
| MSC907 | Air Cairo | 7 | 2026-06-08 |
| MSC883 | Air Cairo | 7 | 2026-06-03 |
| MSC993 | - | 6 | 2026-06-29 |
| MSC937 | - | 6 | 2026-05-18 |
| MSC934 | Air Cairo | 6 | 2026-06-19 |
| MSC926 | - | 6 | 2026-07-07 |
| MSC902 | - | 6 | 2026-06-21 |
| MSC917 | Air Cairo | 5 | 2026-06-02 |
| MSC885 | Air Cairo | 5 | 2026-06-08 |
| MSC814 | - | 5 | 2026-07-09 |
| MSC813 | - | 5 | 2026-07-09 |
| MSC810 | Air Cairo | 5 | 2026-07-26 |
| MSC809 | Air Cairo | 5 | 2026-07-26 |
| MSC933 | Air Cairo | 4 | 2026-06-17 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | MSC810 | NAP → SSH | Jul 26, 20:40 UTC | Jul 26, 22:05 UTC | 1h 25m |
| 2026-07-26 | MSC809 | SSH → NAP | Jul 26, 11:55 UTC | Jul 26, 18:40 UTC | 6h 45m |
| 2026-07-25 | MSC819 | SSH → NAP | Jul 25, 15:05 UTC | Jul 26, 09:35 UTC | 18h 31m |
| 2026-07-25 | MSC3104 | MAD → SSH | Jul 25, 14:10 UTC | Jul 26, 09:35 UTC | 19h 26m |
| 2026-07-25 | MSC3103 | SSH → MAD | Jul 25, 07:25 UTC | Jul 25, 11:20 UTC | 3h 55m |
| 2026-07-25 | MSC1103 | - | Jul 25, 05:10 UTC | Jul 25, 05:20 UTC | 10m |
| 2026-07-24 | MSC2973 | LEJ → RMF | Jul 24, 18:45 UTC | Jul 24, 22:05 UTC | 3h 20m |
| 2026-07-24 | MSC2972 | RMF → LEJ | Jul 24, 04:55 UTC | Jul 24, 17:10 UTC | 12h 15m |
| 2026-07-23 | MSC2975 | LEJ → HRG | Jul 23, 13:45 UTC | Jul 24, 03:25 UTC | 13h 40m |
| 2026-07-23 | MSC2974 | HRG → LEJ | Jul 23, 02:20 UTC | Jul 23, 12:35 UTC | 10h 15m |
| 2026-07-22 | MSC2932 | HRG → HAJ | Jul 22, 14:25 UTC | Jul 23, 01:00 UTC | 10h 35m |
| 2026-07-21 | MSC2921 | ZRH → HRG | Jul 21, 17:25 UTC | Jul 22, 12:55 UTC | 19h 30m |
| 2026-07-21 | MSC2920 | HRG → ZRH | Jul 21, 02:50 UTC | Jul 21, 15:35 UTC | 12h 45m |
| 2026-07-20 | MSC2968 | HRG → PAD | Jul 20, 14:35 UTC | Jul 21, 01:45 UTC | 11h 10m |
| 2026-07-20 | MSC2913 | CGN → HRG | Jul 20, 01:30 UTC | Jul 20, 13:10 UTC | 11h 40m |
| 2026-07-19 | MSC2916 | RMF → CGN | Jul 19, 12:55 UTC | Jul 19, 23:50 UTC | 10h 55m |
| 2026-07-18 | MSC2998 | RMF → MUC | Jul 18, 18:30 UTC | Jul 19, 10:50 UTC | 16h 20m |
| 2026-07-18 | MSC2922 | RMF → ZRH | Jul 18, 13:20 UTC | Jul 18, 17:00 UTC | 3h 40m |
| 2026-07-17 | MSC2922 | RMF → ZRH | Jul 17, 19:05 UTC | Jul 18, 17:00 UTC | 21h 56m |
| 2026-07-17 | MSC2922 | RMF → ZRH | Jul 17, 17:05 UTC | Jul 18, 17:00 UTC | 23h 56m |
| 2026-07-17 | MSC2999 | - | Jul 17, 16:55 UTC | Jul 18, 15:00 UTC | 22h 6m |
| 2026-07-17 | MSC2998 | - | Jul 17, 12:30 UTC | Jul 17, 15:44 UTC | 3h 15m |
| 2026-07-17 | MSC3701 | - | Jul 17, 00:45 UTC | Jul 17, 08:10 UTC | 7h 25m |
| 2026-07-16 | MSC1042 | - | Jul 16, 22:49 UTC | Jul 16, 22:59 UTC | 10m |
| 2026-07-16 | MSC602 | - | Jul 16, 14:40 UTC | Jul 16, 18:05 UTC | 3h 25m |
| 2026-07-16 | MSC601 | - | Jul 16, 08:35 UTC | Jul 16, 12:55 UTC | 4h 20m |
| 2026-07-15 | MSC3998 | - | Jul 15, 08:30 UTC | Jul 15, 11:10 UTC | 2h 40m |
| 2026-07-15 | MSC3997 | - | Jul 15, 03:10 UTC | Jul 15, 05:10 UTC | 2h 0m |
| 2026-07-13 | MSC3118 | - | Jul 13, 09:25 UTC | Jul 13, 13:30 UTC | 4h 5m |
| 2026-07-13 | MSC3117 | - | Jul 13, 03:01 UTC | Jul 13, 07:45 UTC | 4h 45m |
| 2026-07-12 | MSC3612 | - | Jul 12, 18:55 UTC | Jul 13, 01:10 UTC | 6h 15m |
| 2026-07-12 | MSC3611 | - | Jul 12, 13:45 UTC | Jul 12, 17:10 UTC | 3h 25m |
| 2026-07-12 | MSC3608 | - | Jul 12, 06:55 UTC | Jul 12, 10:25 UTC | 3h 30m |
| 2026-07-11 | MSC3607 | BCN → WAW | Jul 11, 12:50 UTC | Jul 12, 04:55 UTC | 16h 5m |
| 2026-07-11 | MSC3103 | - | Jul 11, 07:00 UTC | Jul 11, 10:50 UTC | 3h 50m |
| 2026-07-11 | MSC1115 | - | Jul 11, 03:20 UTC | Jul 11, 03:50 UTC | 30m |
| 2026-07-10 | MSC810 | - | Jul 10, 21:45 UTC | Jul 10, 22:25 UTC | 40m |
| 2026-07-10 | MSC810 | - | Jul 10, 19:50 UTC | Jul 10, 21:40 UTC | 1h 50m |
| 2026-07-10 | MSC809 | - | Jul 10, 15:20 UTC | Jul 10, 18:00 UTC | 2h 40m |
| 2026-07-09 | MSC882 | - | Jul 9, 22:55 UTC | Jul 10, 11:45 UTC | 12h 50m |
| 2026-07-09 | MSC814 | - | Jul 9, 10:20 UTC | Jul 9, 12:30 UTC | 2h 10m |
| 2026-07-09 | MSC813 | - | Jul 9, 05:50 UTC | Jul 9, 08:30 UTC | 2h 40m |
| 2026-07-08 | MSC901 | - | Jul 8, 11:50 UTC | Jul 8, 22:50 UTC | 11h 0m |
| 2026-07-07 | MSC926 | - | Jul 7, 19:30 UTC | Jul 7, 22:55 UTC | 3h 25m |
| 2026-07-07 | MSC925 | - | Jul 7, 13:30 UTC | Jul 7, 17:35 UTC | 4h 5m |
| 2026-07-06 | MSC905 | SSH → KUF | Jul 6, 13:50 UTC | Jul 7, 00:35 UTC | 10h 45m |
| 2026-07-06 | MSC905 | SSH → KUF | Jul 6, 03:05 UTC | Jul 7, 00:35 UTC | 21h 30m |
| 2026-07-06 | MSC905 | SSH → KUF | Jul 6, 01:40 UTC | Jul 7, 00:35 UTC | 22h 55m |
| 2026-07-05 | MSC811 | - | Jul 5, 14:15 UTC | Jul 5, 21:15 UTC | 7h 0m |
| 2026-07-05 | MSC814 | - | Jul 5, 12:25 UTC | Jul 5, 13:55 UTC | 1h 30m |
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-BVK page for operator, model, and routing details .