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
- 112
- Distinct callsigns
- 20
- Country
- EG
- Last broadcast
- 2h ago
Last known 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 |
|---|---|---|---|
| MSC882 | Air Cairo | 15 | 2026-05-27 |
| MSC901 | Air Cairo | 11 | 2026-05-25 |
| MSC881 | Air Cairo | 10 | 2026-05-26 |
| MSC937 | - | 6 | 2026-05-18 |
| MSC934 | Air Cairo | 5 | 2026-05-28 |
| MSC925 | Air Cairo | 5 | 2026-05-05 |
| MSC907 | Air Cairo | 5 | 2026-05-07 |
| MSC883 | Air Cairo | 5 | 2026-05-28 |
| MSC993 | Air Cairo | 4 | 2026-05-04 |
| MSC926 | Air Cairo | 4 | 2026-05-05 |
| MSC905 | Air Cairo | 3 | 2026-05-29 |
| MSC902 | Air Cairo | 3 | 2026-05-25 |
| MSC933 | Air Cairo | 2 | 2026-05-20 |
| MSC908 | Air Cairo | 2 | 2026-05-17 |
| MSC887 | - | 2 | 2026-05-23 |
| MSC886 | - | 2 | 2026-04-14 |
| MSC884 | Air Cairo | 2 | 2026-04-16 |
| MSC822 | Air Cairo | 2 | 2026-04-26 |
| MSC819 | Air Cairo | 2 | 2026-05-17 |
| MSC810 | Air Cairo | 2 | 2026-05-03 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | MSC905 | SSH → KUF | May 29, 04:20 UTC | May 29, 23:00 UTC | 18h 40m |
| 2026-05-28 | MSC905 | SSH → KUF | May 28, 19:05 UTC | May 29, 16:35 UTC | 21h 30m |
| 2026-05-28 | MSC905 | SSH → KUF | May 28, 18:15 UTC | May 29, 16:35 UTC | 22h 21m |
| 2026-05-28 | MSC883 | SSH → NQZ | May 28, 07:05 UTC | May 29, 06:35 UTC | 23h 30m |
| 2026-05-28 | MSC934 | SVO → SSH | May 28, 05:05 UTC | May 29, 05:00 UTC | 23h 55m |
| 2026-05-28 | MSC934 | SVO → SSH | May 28, 04:45 UTC | May 28, 20:45 UTC | 16h 0m |
| 2026-05-28 | MSC934 | SVO → SSH | May 28, 03:15 UTC | May 28, 03:40 UTC | 25m |
| 2026-05-27 | MSC882 | ALA → SSH | May 27, 09:05 UTC | May 27, 23:10 UTC | 14h 5m |
| 2026-05-27 | MSC882 | ALA → SSH | May 27, 01:05 UTC | May 27, 23:10 UTC | 22h 5m |
| 2026-05-26 | MSC881 | SSH → ALA | May 26, 23:05 UTC | May 27, 23:00 UTC | 23h 56m |
| 2026-05-26 | MSC881 | SSH → ALA | May 26, 22:54 UTC | May 27, 21:00 UTC | 22h 5m |
| 2026-05-26 | MSC881 | SSH → ALA | May 26, 07:05 UTC | May 27, 01:34 UTC | 18h 30m |
| 2026-05-25 | MSC902 | LED → SSH | May 25, 23:04 UTC | May 26, 22:59 UTC | 23h 55m |
| 2026-05-25 | MSC901 | SSH → LED | May 25, 20:30 UTC | May 26, 07:49 UTC | 11h 20m |
| 2026-05-24 | MSC902 | LED → SSH | May 24, 21:05 UTC | May 25, 20:59 UTC | 23h 55m |
| 2026-05-24 | MSC901 | SSH → LED | May 24, 05:25 UTC | May 24, 21:45 UTC | 16h 20m |
| 2026-05-23 | MSC901 | SSH → LED | May 23, 21:15 UTC | May 24, 21:00 UTC | 23h 45m |
| 2026-05-23 | MSC901 | SSH → LED | May 23, 19:45 UTC | May 24, 19:00 UTC | 23h 15m |
| 2026-05-23 | MSC887 | - | May 23, 11:05 UTC | May 24, 08:15 UTC | 21h 10m |
| 2026-05-23 | MSC887 | - | May 23, 09:05 UTC | May 24, 08:15 UTC | 23h 10m |
| 2026-05-23 | MSC882 | ALA → SSH | May 23, 08:55 UTC | May 24, 06:10 UTC | 21h 16m |
| 2026-05-22 | MSC882 | ALA → SSH | May 22, 23:05 UTC | May 23, 22:15 UTC | 23h 10m |
| 2026-05-22 | MSC882 | ALA → SSH | May 22, 22:40 UTC | May 23, 20:45 UTC | 22h 5m |
| 2026-05-22 | MSC882 | ALA → SSH | May 22, 15:05 UTC | May 23, 11:45 UTC | 20h 39m |
| 2026-05-22 | MSC882 | ALA → SSH | May 22, 14:30 UTC | May 23, 11:45 UTC | 21h 14m |
| 2026-05-22 | MSC3450 | - | May 22, 11:55 UTC | May 22, 12:40 UTC | 45m |
| 2026-05-22 | MSC3706 | - | May 22, 07:35 UTC | May 22, 10:15 UTC | 2h 40m |
| 2026-05-22 | MSC3705 | - | May 22, 03:25 UTC | May 22, 06:15 UTC | 2h 50m |
| 2026-05-21 | MSC910 | UFA → SSH | May 21, 13:10 UTC | May 21, 23:50 UTC | 10h 40m |
| 2026-05-21 | MSC934 | SVO → SSH | May 21, 05:55 UTC | May 21, 09:20 UTC | 3h 25m |
| 2026-05-21 | MSC934 | SVO → SSH | May 21, 04:30 UTC | May 21, 04:50 UTC | 20m |
| 2026-05-20 | MSC933 | SSH → SVO | May 20, 09:00 UTC | May 21, 00:25 UTC | 15h 25m |
| 2026-05-20 | MSC933 | SSH → SVO | May 20, 01:05 UTC | May 21, 00:25 UTC | 23h 21m |
| 2026-05-19 | MSC882 | ALA → SSH | May 19, 23:05 UTC | May 20, 23:00 UTC | 23h 56m |
| 2026-05-19 | MSC881 | SSH → ALA | May 19, 22:55 UTC | May 20, 21:00 UTC | 22h 6m |
| 2026-05-18 | MSC937 | - | May 18, 11:05 UTC | May 19, 05:40 UTC | 18h 34m |
| 2026-05-18 | MSC937 | - | May 18, 09:05 UTC | May 19, 05:40 UTC | 20h 34m |
| 2026-05-18 | MSC937 | - | May 18, 08:55 UTC | May 19, 05:40 UTC | 20h 44m |
| 2026-05-18 | MSC937 | - | May 18, 01:05 UTC | May 18, 22:15 UTC | 21h 9m |
| 2026-05-18 | MSC937 | - | May 18, 00:25 UTC | May 18, 22:15 UTC | 21h 49m |
| 2026-05-17 | MSC937 | - | May 17, 21:05 UTC | May 18, 21:00 UTC | 23h 54m |
| 2026-05-17 | MSC908 | KZN → SSH | May 17, 20:30 UTC | May 18, 19:00 UTC | 22h 29m |
| 2026-05-17 | MSC811 | SSH → CTA | May 17, 11:15 UTC | May 17, 19:10 UTC | 7h 55m |
| 2026-05-17 | MSC819 | SSH → NAP | May 17, 04:10 UTC | May 17, 09:25 UTC | 5h 15m |
| 2026-05-16 | MSC806 | MXP → CAI | May 16, 19:20 UTC | May 16, 22:05 UTC | 2h 45m |
| 2026-05-16 | MSC805 | CAI → MXP | May 16, 13:51 UTC | May 16, 17:55 UTC | 4h 5m |
| 2026-05-16 | MSC502 | SHJ → CAI | May 16, 09:31 UTC | May 16, 09:51 UTC | 20m |
| 2026-05-15 | MSC804 | MXP → CAI | May 15, 17:40 UTC | May 16, 04:20 UTC | 10h 40m |
| 2026-05-15 | MSC803 | CAI → MXP | May 15, 12:10 UTC | May 15, 16:15 UTC | 4h 4m |
| 2026-05-15 | MSC501 | CAI → SHJ | May 15, 01:50 UTC | May 15, 10:10 UTC | 8h 20m |
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 .