sensors Mode-S transponder
01022B
ICAO 24-bit transponder address · allocated to Egypt
Currently assigned to SU-BUJ · AIRBUS A-320
- Hex
- 01022B
- Octal
- 00201053
- Decimal
- 66,091
- Country
- EG
- Tail
- SU-BUJ
- Type
- A320
- Flights observed
- 101
- Distinct callsigns
- 20
- Country
- EG
- Last broadcast
- 3h ago
Last known position
Country allocation
The ICAO 24-bit address 01022B 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 |
|---|---|---|---|
| MSC913 | - | 15 | 2026-05-29 |
| MSC994 | Air Cairo | 8 | 2026-06-02 |
| MSC993 | Air Cairo | 6 | 2026-05-30 |
| MSC3701 | - | 6 | 2026-05-25 |
| MSC917 | Air Cairo | 4 | 2026-05-13 |
| MSC903 | Air Cairo | 4 | 2026-05-21 |
| MSC3705 | - | 4 | 2026-05-08 |
| MSC3451 | - | 4 | 2026-06-02 |
| MSC3450 | - | 3 | 2026-06-02 |
| MSC912 | Air Cairo | 2 | 2026-04-18 |
| MSC831 | Air Cairo | 2 | 2026-05-30 |
| MSC822 | Air Cairo | 2 | 2026-05-10 |
| MSC821 | Air Cairo | 2 | 2026-05-10 |
| MSC813 | Air Cairo | 2 | 2026-05-02 |
| MSC810 | Air Cairo | 2 | 2026-05-17 |
| MSC809 | Air Cairo | 2 | 2026-05-17 |
| MSC802 | Air Cairo | 2 | 2026-05-03 |
| MSC801 | Air Cairo | 2 | 2026-05-03 |
| MSC3706 | - | 2 | 2026-05-08 |
| MSC3623 | - | 2 | 2026-05-01 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-02 | MSC3451 | - | Jun 2, 15:15 UTC | Jun 2, 16:10 UTC | 55m |
| 2026-06-02 | MSC3450 | - | Jun 2, 13:15 UTC | Jun 2, 14:00 UTC | 45m |
| 2026-06-02 | MSC994 | EVN → SSH | Jun 2, 00:05 UTC | Jun 2, 05:40 UTC | 5h 35m |
| 2026-05-31 | MSC3451 | - | May 31, 19:30 UTC | May 31, 20:20 UTC | 50m |
| 2026-05-30 | MSC993 | SSH → EVN | May 30, 23:45 UTC | May 31, 18:15 UTC | 18h 30m |
| 2026-05-30 | MSC832 | BGY → SSH | May 30, 12:40 UTC | May 31, 00:55 UTC | 12h 15m |
| 2026-05-30 | MSC831 | SSH → BGY | May 30, 07:25 UTC | May 30, 11:10 UTC | 3h 45m |
| 2026-05-29 | MSC831 | SSH → BGY | May 29, 11:00 UTC | May 30, 10:45 UTC | 23h 45m |
| 2026-05-29 | MSC913 | - | May 29, 09:20 UTC | May 30, 08:45 UTC | 23h 25m |
| 2026-05-28 | MSC913 | - | May 28, 18:25 UTC | May 29, 12:00 UTC | 17h 35m |
| 2026-05-28 | MSC994 | EVN → SSH | May 28, 04:45 UTC | May 28, 07:05 UTC | 2h 20m |
| 2026-05-28 | MSC993 | SSH → EVN | May 28, 00:40 UTC | May 28, 02:35 UTC | 1h 55m |
| 2026-05-27 | MSC3461 | - | May 27, 14:25 UTC | May 27, 15:20 UTC | 55m |
| 2026-05-27 | MSC3460 | - | May 27, 12:10 UTC | May 27, 13:00 UTC | 50m |
| 2026-05-27 | MSC3451 | - | May 27, 06:25 UTC | May 27, 07:15 UTC | 51m |
| 2026-05-27 | MSC3450 | - | May 27, 03:54 UTC | May 27, 04:39 UTC | 45m |
| 2026-05-26 | MSC3451 | - | May 26, 14:45 UTC | May 26, 15:14 UTC | 30m |
| 2026-05-26 | MSC3450 | - | May 26, 12:05 UTC | May 26, 12:54 UTC | 50m |
| 2026-05-26 | MSC3461 | - | May 26, 09:19 UTC | May 26, 10:10 UTC | 50m |
| 2026-05-26 | MSC3460 | - | May 26, 06:39 UTC | May 26, 07:19 UTC | 40m |
| 2026-05-25 | MSC3701 | - | May 25, 20:55 UTC | May 26, 04:30 UTC | 7h 35m |
| 2026-05-25 | MSC182 | - | May 25, 18:55 UTC | May 25, 19:10 UTC | 15m |
| 2026-05-25 | MSC1405 | - | May 25, 12:50 UTC | May 25, 13:05 UTC | 15m |
| 2026-05-24 | MSC913 | - | May 24, 16:35 UTC | May 25, 07:15 UTC | 14h 40m |
| 2026-05-24 | MSC913 | - | May 24, 08:50 UTC | May 25, 07:15 UTC | 22h 25m |
| 2026-05-24 | MSC913 | - | May 24, 06:50 UTC | May 25, 06:45 UTC | 23h 55m |
| 2026-05-24 | MSC913 | - | May 24, 06:20 UTC | May 25, 04:45 UTC | 22h 25m |
| 2026-05-23 | MSC913 | - | May 23, 22:50 UTC | May 24, 21:00 UTC | 22h 10m |
| 2026-05-23 | MSC913 | - | May 23, 21:25 UTC | May 24, 20:45 UTC | 23h 20m |
| 2026-05-22 | MSC913 | - | May 22, 04:50 UTC | May 22, 23:55 UTC | 19h 5m |
| 2026-05-22 | MSC913 | - | May 22, 04:30 UTC | May 22, 23:55 UTC | 19h 25m |
| 2026-05-21 | MSC913 | - | May 21, 22:50 UTC | May 22, 22:45 UTC | 23h 55m |
| 2026-05-21 | MSC913 | - | May 21, 20:50 UTC | May 22, 20:45 UTC | 23h 55m |
| 2026-05-21 | MSC903 | SSH → SVO | May 21, 18:50 UTC | May 22, 14:30 UTC | 19h 40m |
| 2026-05-21 | MSC903 | SSH → SVO | May 21, 18:40 UTC | May 22, 14:30 UTC | 19h 50m |
| 2026-05-21 | MSC994 | EVN → SSH | May 21, 00:35 UTC | May 21, 14:25 UTC | 13h 50m |
| 2026-05-18 | MSC993 | SSH → EVN | May 18, 23:35 UTC | May 19, 05:30 UTC | 5h 55m |
| 2026-05-17 | MSC810 | NAP → SSH | May 17, 20:40 UTC | May 17, 23:05 UTC | 2h 25m |
| 2026-05-17 | MSC809 | SSH → NAP | May 17, 11:05 UTC | May 17, 19:15 UTC | 8h 10m |
| 2026-05-16 | MSC2951 | STR → HRG | May 16, 15:45 UTC | May 17, 10:00 UTC | 18h 15m |
| 2026-05-16 | MSC2950 | HRG → STR | May 16, 11:11 UTC | May 16, 14:41 UTC | 3h 30m |
| 2026-05-15 | MSC2950 | HRG → STR | May 15, 14:50 UTC | May 16, 14:41 UTC | 23h 51m |
| 2026-05-15 | MSC913 | - | May 15, 12:50 UTC | May 16, 12:45 UTC | 23h 55m |
| 2026-05-14 | MSC913 | - | May 14, 20:50 UTC | May 15, 14:55 UTC | 18h 4m |
| 2026-05-14 | MSC913 | - | May 14, 18:50 UTC | May 15, 14:55 UTC | 20h 4m |
| 2026-05-14 | MSC903 | SSH → SVO | May 14, 00:50 UTC | May 14, 23:55 UTC | 23h 5m |
| 2026-05-13 | MSC903 | SSH → SVO | May 13, 23:45 UTC | May 14, 22:45 UTC | 23h 0m |
| 2026-05-13 | MSC917 | SSH → VOG | May 13, 05:35 UTC | May 13, 05:50 UTC | 15m |
| 2026-05-12 | MSC917 | SSH → VOG | May 12, 20:30 UTC | May 12, 23:45 UTC | 3h 15m |
| 2026-05-12 | MSC994 | EVN → SSH | May 12, 03:25 UTC | May 12, 05:35 UTC | 2h 10m |
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-BUJ page for operator, model, and routing details .