sensors Mode-S transponder
01025B
ICAO 24-bit transponder address · allocated to Egypt
Currently assigned to SU-BVJ · AIRBUS A-320neo
- Hex
- 01025B
- Octal
- 00201133
- Decimal
- 66,139
- Country
- EG
- Tail
- SU-BVJ
- Type
- A20N
- Flights observed
- 122
- Distinct callsigns
- 20
- Country
- EG
- Last broadcast
- 6h ago
Last known position
Country allocation
The ICAO 24-bit address 01025B 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 |
|---|---|---|---|
| MSC884 | Air Cairo | 15 | 2026-05-05 |
| MSC882 | Air Cairo | 9 | 2026-05-22 |
| MSC883 | Air Cairo | 8 | 2026-05-19 |
| MSC886 | Air Cairo | 7 | 2026-05-11 |
| MSC881 | Air Cairo | 7 | 2026-06-02 |
| MSC885 | Air Cairo | 6 | 2026-05-25 |
| MSC815 | Air Cairo | 5 | 2026-05-23 |
| MSC933 | Air Cairo | 4 | 2026-06-03 |
| MSC913 | - | 4 | 2026-05-30 |
| MSC904 | Air Cairo | 4 | 2026-06-01 |
| MSC901 | Air Cairo | 4 | 2026-05-27 |
| MSC3701 | - | 4 | 2026-06-01 |
| MSC907 | Air Cairo | 3 | 2026-05-14 |
| MSC903 | Air Cairo | 3 | 2026-05-30 |
| MSC181 | - | 3 | 2026-05-30 |
| MSC937 | - | 2 | 2026-05-15 |
| MSC917 | Air Cairo | 2 | 2026-05-22 |
| MSC910 | Air Cairo | 2 | 2026-05-23 |
| MSC821 | Air Cairo | 2 | 2026-05-02 |
| MSC810 | Air Cairo | 2 | 2026-05-29 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-04 | MSC934 | SVO → SSH | Jun 4, 01:25 UTC | Jun 4, 01:55 UTC | 30m |
| 2026-06-03 | MSC933 | SSH → SVO | Jun 3, 18:55 UTC | Jun 3, 23:25 UTC | 4h 30m |
| 2026-06-02 | MSC881 | SSH → ALA | Jun 2, 23:00 UTC | Jun 3, 12:15 UTC | 13h 15m |
| 2026-06-02 | MSC881 | SSH → ALA | Jun 2, 03:25 UTC | Jun 3, 01:35 UTC | 22h 10m |
| 2026-06-02 | MSC3702 | - | Jun 2, 01:35 UTC | Jun 3, 00:45 UTC | 23h 10m |
| 2026-06-01 | MSC3701 | - | Jun 1, 20:50 UTC | Jun 2, 04:30 UTC | 7h 40m |
| 2026-06-01 | MSC3701 | - | Jun 1, 02:50 UTC | Jun 2, 02:20 UTC | 23h 30m |
| 2026-06-01 | MSC904 | SVO → SSH | Jun 1, 01:05 UTC | Jun 1, 23:25 UTC | 22h 20m |
| 2026-05-31 | MSC904 | SVO → SSH | May 31, 23:35 UTC | May 31, 23:55 UTC | 20m |
| 2026-05-30 | MSC913 | - | May 30, 22:50 UTC | May 31, 18:45 UTC | 19h 55m |
| 2026-05-30 | MSC903 | SSH → SVO | May 30, 21:50 UTC | May 31, 18:45 UTC | 20h 55m |
| 2026-05-30 | MSC903 | SSH → SVO | May 30, 14:50 UTC | May 31, 09:55 UTC | 19h 5m |
| 2026-05-30 | MSC3110 | - | May 30, 12:50 UTC | May 31, 09:55 UTC | 21h 5m |
| 2026-05-30 | MSC3109 | - | May 30, 06:05 UTC | May 30, 10:20 UTC | 4h 15m |
| 2026-05-30 | MSC181 | - | May 30, 04:00 UTC | May 30, 04:10 UTC | 10m |
| 2026-05-29 | MSC810 | NAP → SSH | May 29, 19:00 UTC | May 29, 22:25 UTC | 3h 25m |
| 2026-05-28 | MSC809 | SSH → NAP | May 28, 22:50 UTC | May 29, 17:55 UTC | 19h 5m |
| 2026-05-27 | MSC902 | LED → SSH | May 27, 18:00 UTC | May 27, 22:40 UTC | 4h 40m |
| 2026-05-27 | MSC901 | SSH → LED | May 27, 11:30 UTC | May 27, 16:20 UTC | 4h 50m |
| 2026-05-25 | MSC885 | SSH → AKX | May 25, 22:55 UTC | May 26, 09:09 UTC | 10h 15m |
| 2026-05-24 | MSC908 | KZN → SSH | May 24, 20:40 UTC | May 25, 11:30 UTC | 14h 50m |
| 2026-05-24 | MSC816 | BLQ → SSH | May 24, 11:00 UTC | May 24, 19:10 UTC | 8h 10m |
| 2026-05-23 | MSC815 | SSH → BLQ | May 23, 20:15 UTC | May 24, 09:50 UTC | 13h 35m |
| 2026-05-23 | MSC815 | SSH → BLQ | May 23, 11:15 UTC | May 24, 09:50 UTC | 22h 35m |
| 2026-05-23 | MSC910 | UFA → SSH | May 23, 04:00 UTC | May 23, 22:35 UTC | 18h 36m |
| 2026-05-22 | MSC918 | VOG → SSH | May 22, 20:50 UTC | May 23, 20:45 UTC | 23h 55m |
| 2026-05-22 | MSC917 | SSH → VOG | May 22, 18:25 UTC | May 23, 12:10 UTC | 17h 44m |
| 2026-05-22 | MSC917 | SSH → VOG | May 22, 11:10 UTC | May 23, 05:45 UTC | 18h 35m |
| 2026-05-22 | MSC882 | ALA → SSH | May 22, 09:30 UTC | May 23, 05:45 UTC | 20h 14m |
| 2026-05-22 | MSC882 | ALA → SSH | May 22, 00:50 UTC | May 22, 22:30 UTC | 21h 40m |
| 2026-05-21 | MSC882 | ALA → SSH | May 21, 23:05 UTC | May 22, 22:30 UTC | 23h 25m |
| 2026-05-21 | MSC180 | - | May 21, 20:55 UTC | May 21, 21:10 UTC | 15m |
| 2026-05-21 | MSC181 | - | May 21, 03:45 UTC | May 21, 03:55 UTC | 10m |
| 2026-05-20 | MSC901 | SSH → LED | May 20, 11:25 UTC | May 20, 23:05 UTC | 11h 40m |
| 2026-05-19 | MSC883 | SSH → NQZ | May 19, 18:05 UTC | May 20, 06:25 UTC | 12h 21m |
| 2026-05-18 | MSC3701 | - | May 18, 20:40 UTC | May 19, 05:55 UTC | 9h 15m |
| 2026-05-18 | MSC3701 | - | May 18, 04:51 UTC | May 19, 04:35 UTC | 23h 44m |
| 2026-05-18 | MSC904 | SVO → SSH | May 18, 03:15 UTC | May 19, 02:35 UTC | 23h 19m |
| 2026-05-17 | MSC904 | SVO → SSH | May 17, 20:50 UTC | May 18, 20:45 UTC | 23h 54m |
| 2026-05-17 | MSC913 | - | May 17, 11:45 UTC | May 18, 05:55 UTC | 18h 10m |
| 2026-05-17 | MSC913 | - | May 17, 00:50 UTC | May 17, 21:45 UTC | 20h 55m |
| 2026-05-16 | MSC913 | - | May 16, 22:50 UTC | May 17, 21:45 UTC | 22h 55m |
| 2026-05-16 | MSC903 | SSH → SVO | May 16, 21:45 UTC | May 17, 18:45 UTC | 21h 0m |
| 2026-05-15 | MSC937 | - | May 15, 18:35 UTC | May 16, 05:25 UTC | 10h 50m |
| 2026-05-14 | MSC882 | ALA → SSH | May 14, 22:35 UTC | May 15, 11:20 UTC | 12h 45m |
| 2026-05-14 | MSC881 | SSH → ALA | May 14, 11:20 UTC | May 15, 10:45 UTC | 23h 25m |
| 2026-05-14 | MSC881 | SSH → ALA | May 14, 10:10 UTC | May 15, 08:45 UTC | 22h 35m |
| 2026-05-14 | MSC881 | SSH → ALA | May 14, 05:15 UTC | May 15, 01:15 UTC | 20h 0m |
| 2026-05-14 | MSC881 | SSH → ALA | May 14, 02:50 UTC | May 15, 01:15 UTC | 22h 25m |
| 2026-05-14 | MSC907 | SSH → KZN | May 14, 01:20 UTC | May 15, 00:45 UTC | 23h 25m |
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-BVJ page for operator, model, and routing details .