sensors Mode-S transponder
01013D
ICAO 24-bit transponder address · allocated to Egypt
Currently assigned to SU-GDO · BOEING 777-300ER
- Hex
- 01013D
- Octal
- 00200475
- Decimal
- 65,853
- Country
- EG
- Tail
- SU-GDO
- Type
- B77W
- Flights observed
- 95
- Distinct callsigns
- 15
- Country
- EG
- Last broadcast
- 1h ago
Last known position
Country allocation
The ICAO 24-bit address 01013D 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 15 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| MSR959 | Egyptair | 25 | 2026-05-25 |
| MSR958 | Egyptair | 17 | 2026-05-22 |
| MSR777 | Egyptair | 15 | 2026-05-28 |
| MSR778 | Egyptair | 13 | 2026-05-28 |
| MSR985 | Egyptair | 5 | 2026-05-06 |
| MSR986 | Egyptair | 4 | 2026-05-06 |
| MSR785 | Egyptair | 4 | 2026-04-26 |
| MSR996 | Egyptair | 2 | 2026-05-29 |
| MSR995 | Egyptair | 2 | 2026-05-29 |
| MSR953 | Egyptair | 2 | 2026-05-01 |
| MSR678 | Egyptair | 2 | 2026-05-21 |
| MSR954 | Egyptair | 1 | 2026-05-01 |
| MSR800 | Egyptair | 1 | 2026-05-22 |
| MSR799 | Egyptair | 1 | 2026-05-22 |
| MSR786 | Egyptair | 1 | 2026-04-26 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | MSR996 | YYZ → CAI | May 29, 17:05 UTC | May 30, 03:15 UTC | 10h 10m |
| 2026-05-29 | MSR995 | CAI → YYZ | May 29, 00:25 UTC | May 29, 11:15 UTC | 10h 50m |
| 2026-05-28 | MSR778 | LHR → CAI | May 28, 14:55 UTC | May 28, 18:45 UTC | 3h 50m |
| 2026-05-28 | MSR777 | CAI → LHR | May 28, 08:00 UTC | May 28, 12:35 UTC | 4h 35m |
| 2026-05-27 | MSR778 | LHR → CAI | May 27, 14:45 UTC | May 27, 18:40 UTC | 3h 55m |
| 2026-05-27 | MSR777 | CAI → LHR | May 27, 08:15 UTC | May 27, 12:25 UTC | 4h 10m |
| 2026-05-26 | MSR778 | LHR → CAI | May 26, 15:05 UTC | May 26, 19:05 UTC | 4h 0m |
| 2026-05-25 | MSR777 | CAI → LHR | May 25, 18:20 UTC | May 26, 12:24 UTC | 18h 5m |
| 2026-05-25 | MSR959 | CAN → CAI | May 25, 04:05 UTC | May 26, 02:00 UTC | 21h 55m |
| 2026-05-25 | MSR959 | CAN → CAI | May 25, 01:55 UTC | May 25, 23:45 UTC | 21h 50m |
| 2026-05-23 | MSR959 | CAN → CAI | May 23, 18:30 UTC | May 24, 02:15 UTC | 7h 45m |
| 2026-05-23 | MSR959 | CAN → CAI | May 23, 16:25 UTC | May 23, 16:35 UTC | 10m |
| 2026-05-22 | MSR958 | CAI → CAN | May 22, 22:10 UTC | May 23, 04:55 UTC | 6h 44m |
| 2026-05-22 | MSR800 | CDG → CAI | May 22, 14:40 UTC | May 22, 18:15 UTC | 3h 35m |
| 2026-05-22 | MSR799 | CAI → CDG | May 22, 08:30 UTC | May 22, 08:40 UTC | 10m |
| 2026-05-21 | MSR678 | MED → CAI | May 21, 11:10 UTC | May 21, 20:00 UTC | 8h 50m |
| 2026-05-18 | MSR959 | CAN → CAI | May 18, 16:00 UTC | May 18, 16:10 UTC | 10m |
| 2026-05-18 | MSR958 | CAI → CAN | May 18, 01:35 UTC | May 18, 04:25 UTC | 2h 50m |
| 2026-05-17 | MSR778 | LHR → CAI | May 17, 15:01 UTC | May 17, 18:50 UTC | 3h 50m |
| 2026-05-17 | MSR777 | CAI → LHR | May 17, 08:20 UTC | May 17, 12:55 UTC | 4h 35m |
| 2026-05-16 | MSR959 | CAN → CAI | May 16, 18:00 UTC | May 17, 01:50 UTC | 7h 50m |
| 2026-05-15 | MSR958 | CAI → CAN | May 15, 21:55 UTC | May 16, 04:25 UTC | 6h 30m |
| 2026-05-15 | MSR778 | LHR → CAI | May 15, 14:35 UTC | May 15, 18:15 UTC | 3h 39m |
| 2026-05-15 | MSR777 | CAI → LHR | May 15, 08:35 UTC | May 15, 12:40 UTC | 4h 5m |
| 2026-05-14 | MSR996 | YYZ → CAI | May 14, 17:10 UTC | May 15, 02:20 UTC | 9h 10m |
| 2026-05-14 | MSR995 | CAI → YYZ | May 14, 00:30 UTC | May 14, 11:30 UTC | 11h 0m |
| 2026-05-12 | MSR778 | LHR → CAI | May 12, 15:01 UTC | May 12, 18:30 UTC | 3h 30m |
| 2026-05-11 | MSR777 | CAI → LHR | May 11, 17:20 UTC | May 12, 13:05 UTC | 19h 45m |
| 2026-05-11 | MSR777 | CAI → LHR | May 11, 15:20 UTC | May 12, 13:05 UTC | 21h 46m |
| 2026-05-11 | MSR777 | CAI → LHR | May 11, 14:35 UTC | May 12, 13:05 UTC | 22h 31m |
| 2026-05-11 | MSR777 | CAI → LHR | May 11, 07:55 UTC | May 11, 12:20 UTC | 4h 25m |
| 2026-05-10 | MSR959 | CAN → CAI | May 10, 15:45 UTC | May 10, 21:35 UTC | 5h 50m |
| 2026-05-10 | MSR958 | CAI → CAN | May 10, 02:39 UTC | May 10, 09:45 UTC | 7h 5m |
| 2026-05-08 | MSR959 | CAN → CAI | May 8, 18:35 UTC | May 9, 02:50 UTC | 8h 15m |
| 2026-05-08 | MSR959 | CAN → CAI | May 8, 16:20 UTC | May 8, 16:30 UTC | 10m |
| 2026-05-07 | MSR958 | CAI → CAN | May 7, 21:50 UTC | May 8, 04:39 UTC | 6h 49m |
| 2026-05-07 | MSR778 | LHR → CAI | May 7, 15:20 UTC | May 7, 18:50 UTC | 3h 30m |
| 2026-05-06 | MSR986 | JFK → CAI | May 6, 18:45 UTC | May 7, 03:30 UTC | 8h 45m |
| 2026-05-06 | MSR985 | CAI → JFK | May 6, 05:10 UTC | May 6, 16:00 UTC | 10h 50m |
| 2026-05-05 | MSR985 | CAI → JFK | May 5, 19:20 UTC | May 6, 16:00 UTC | 20h 40m |
| 2026-05-05 | MSR985 | CAI → JFK | May 5, 18:15 UTC | May 6, 16:00 UTC | 21h 45m |
| 2026-05-05 | MSR958 | CAI → CAN | May 5, 03:25 UTC | May 5, 04:45 UTC | 1h 20m |
| 2026-05-04 | MSR778 | LHR → CAI | May 4, 14:55 UTC | May 4, 18:45 UTC | 3h 51m |
| 2026-05-03 | MSR986 | JFK → CAI | May 3, 17:20 UTC | May 4, 12:45 UTC | 19h 25m |
| 2026-05-03 | MSR986 | JFK → CAI | May 3, 17:10 UTC | May 4, 12:45 UTC | 19h 35m |
| 2026-05-03 | MSR985 | CAI → JFK | May 3, 03:25 UTC | May 3, 14:20 UTC | 10h 54m |
| 2026-05-02 | MSR778 | LHR → CAI | May 2, 14:40 UTC | May 2, 18:35 UTC | 3h 55m |
| 2026-05-02 | MSR777 | CAI → LHR | May 2, 08:40 UTC | May 2, 12:15 UTC | 3h 35m |
| 2026-05-01 | MSR954 | HGH → CAI | May 1, 07:25 UTC | May 2, 03:10 UTC | 19h 45m |
| 2026-05-01 | MSR953 | CAI → HGH | May 1, 03:45 UTC | May 2, 03:10 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-GDO page for operator, model, and routing details .