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