sensors Mode-S transponder
0101DD
ICAO 24-bit transponder address · allocated to Egypt
Currently assigned to SU-GET · BOEING 787-9 Dreamliner
- Hex
- 0101DD
- Octal
- 00200735
- Decimal
- 66,013
- Country
- EG
- Tail
- SU-GET
- Type
- B789
- Flights observed
- 131
- Distinct callsigns
- 20
- Country
- EG
- Last broadcast
- 44m ago
Last known position
Country allocation
The ICAO 24-bit address 0101DD 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 |
|---|---|---|---|
| MSR952 | - | 20 | 2026-07-12 |
| MSR954 | Egyptair | 19 | 2026-05-29 |
| MSR951 | - | 18 | 2026-07-12 |
| MSR953 | Egyptair | 15 | 2026-05-08 |
| MSR987 | Egyptair | 6 | 2026-06-10 |
| MSR955 | Egyptair | 6 | 2026-06-12 |
| MSR982 | - | 5 | 2026-07-07 |
| MSR981 | - | 5 | 2026-07-13 |
| MSR988 | Egyptair | 4 | 2026-06-10 |
| MSR956 | - | 4 | 2026-06-12 |
| MSR786 | Egyptair | 3 | 2026-06-07 |
| MSR785 | Egyptair | 3 | 2026-06-07 |
| MSR965 | Egyptair | 2 | 2026-05-31 |
| MSR964 | Egyptair | 2 | 2026-05-30 |
| MSR913 | - | 2 | 2026-07-11 |
| MSR3009 | - | 2 | 2026-07-08 |
| MSR996 | Egyptair | 1 | 2026-05-23 |
| MSR995 | Egyptair | 1 | 2026-05-23 |
| MSR986 | - | 1 | 2026-07-05 |
| MSR985 | - | 1 | 2026-07-05 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | MSR981 | - | Jul 13, 21:40 UTC | Jul 14, 08:45 UTC | 11h 5m |
| 2026-07-12 | MSR952 | - | Jul 12, 10:40 UTC | Jul 13, 03:55 UTC | 17h 15m |
| 2026-07-12 | MSR952 | - | Jul 12, 03:20 UTC | Jul 13, 03:15 UTC | 23h 55m |
| 2026-07-12 | MSR951 | - | Jul 12, 02:50 UTC | Jul 13, 01:15 UTC | 22h 25m |
| 2026-07-11 | MSR913 | - | Jul 11, 12:45 UTC | Jul 11, 15:20 UTC | 2h 35m |
| 2026-07-11 | MSR912 | - | Jul 11, 07:55 UTC | Jul 11, 10:50 UTC | 2h 55m |
| 2026-07-09 | MSR3010 | - | Jul 9, 21:40 UTC | Jul 10, 07:55 UTC | 10h 15m |
| 2026-07-08 | MSR3009 | - | Jul 8, 09:20 UTC | Jul 8, 20:35 UTC | 11h 15m |
| 2026-07-08 | MSR3009 | - | Jul 8, 09:05 UTC | Jul 8, 09:15 UTC | 10m |
| 2026-07-07 | MSR982 | - | Jul 7, 16:45 UTC | Jul 8, 02:35 UTC | 9h 50m |
| 2026-07-06 | MSR981 | - | Jul 6, 22:10 UTC | Jul 7, 09:15 UTC | 11h 5m |
| 2026-07-05 | MSR986 | - | Jul 5, 18:30 UTC | Jul 6, 03:45 UTC | 9h 15m |
| 2026-07-05 | MSR985 | - | Jul 5, 04:55 UTC | Jul 5, 15:05 UTC | 10h 10m |
| 2026-07-04 | MSR982 | - | Jul 4, 16:15 UTC | Jul 5, 01:45 UTC | 9h 30m |
| 2026-07-03 | MSR981 | - | Jul 3, 22:00 UTC | Jul 4, 09:25 UTC | 11h 25m |
| 2026-06-13 | MSR952 | PVG → CAI | Jun 13, 20:35 UTC | Jun 14, 03:40 UTC | 7h 5m |
| 2026-06-13 | MSR952 | PVG → CAI | Jun 13, 07:30 UTC | Jun 14, 03:40 UTC | 20h 10m |
| 2026-06-13 | MSR952 | PVG → CAI | Jun 13, 05:20 UTC | Jun 14, 03:40 UTC | 22h 20m |
| 2026-06-13 | MSR951 | - | Jun 13, 05:00 UTC | Jun 14, 01:30 UTC | 20h 30m |
| 2026-06-12 | MSR956 | - | Jun 12, 16:55 UTC | Jun 13, 02:25 UTC | 9h 30m |
| 2026-06-12 | MSR955 | CAI → PEK | Jun 12, 08:55 UTC | Jun 12, 09:15 UTC | 20m |
| 2026-06-12 | MSR955 | CAI → PEK | Jun 12, 00:45 UTC | Jun 12, 05:40 UTC | 4h 55m |
| 2026-06-10 | MSR988 | EWR → CAI | Jun 10, 17:25 UTC | Jun 11, 03:00 UTC | 9h 35m |
| 2026-06-10 | MSR987 | CAI → EWR | Jun 10, 03:40 UTC | Jun 10, 14:25 UTC | 10h 45m |
| 2026-06-09 | MSR982 | IAD → CAI | Jun 9, 16:45 UTC | Jun 10, 01:15 UTC | 8h 30m |
| 2026-06-09 | MSR982 | IAD → CAI | Jun 9, 15:35 UTC | Jun 9, 15:50 UTC | 15m |
| 2026-06-08 | MSR981 | CAI → IAD | Jun 8, 21:40 UTC | Jun 9, 08:35 UTC | 10h 55m |
| 2026-06-07 | MSR786 | FRA → CAI | Jun 7, 15:15 UTC | Jun 7, 18:40 UTC | 3h 25m |
| 2026-06-07 | MSR785 | CAI → FRA | Jun 7, 09:15 UTC | Jun 7, 12:50 UTC | 3h 35m |
| 2026-06-06 | MSR952 | PVG → CAI | Jun 6, 17:34 UTC | Jun 7, 03:35 UTC | 10h 0m |
| 2026-06-06 | MSR952 | PVG → CAI | Jun 6, 02:45 UTC | Jun 7, 01:15 UTC | 22h 30m |
| 2026-06-05 | MSR951 | CAI → PVG | Jun 5, 23:30 UTC | Jun 6, 21:50 UTC | 22h 20m |
| 2026-06-05 | MSR951 | CAI → PVG | Jun 5, 21:50 UTC | Jun 6, 17:54 UTC | 20h 5m |
| 2026-06-05 | MSR786 | FRA → CAI | Jun 5, 14:15 UTC | Jun 5, 17:25 UTC | 3h 10m |
| 2026-06-05 | MSR785 | CAI → FRA | Jun 5, 09:20 UTC | Jun 5, 12:15 UTC | 2h 55m |
| 2026-06-04 | MSR952 | PVG → CAI | Jun 4, 19:55 UTC | Jun 5, 03:30 UTC | 7h 35m |
| 2026-06-04 | MSR952 | PVG → CAI | Jun 4, 02:45 UTC | Jun 4, 23:25 UTC | 20h 40m |
| 2026-06-03 | MSR952 | PVG → CAI | Jun 3, 23:20 UTC | Jun 4, 23:15 UTC | 23h 55m |
| 2026-06-03 | MSR951 | CAI → PVG | Jun 3, 21:45 UTC | Jun 4, 21:00 UTC | 23h 15m |
| 2026-06-01 | MSR988 | EWR → CAI | Jun 1, 17:25 UTC | Jun 2, 02:55 UTC | 9h 30m |
| 2026-06-01 | MSR987 | CAI → EWR | Jun 1, 02:50 UTC | Jun 1, 13:55 UTC | 11h 5m |
| 2026-05-31 | MSR965 | NRT → CAI | May 31, 11:40 UTC | Jun 1, 00:50 UTC | 13h 10m |
| 2026-05-30 | MSR964 | CAI → NRT | May 30, 22:10 UTC | May 31, 08:50 UTC | 10h 40m |
| 2026-05-30 | MSR913 | DXB → CAI | May 30, 09:45 UTC | May 30, 15:55 UTC | 6h 10m |
| 2026-05-29 | MSR954 | HGH → CAI | May 29, 19:10 UTC | May 30, 03:00 UTC | 7h 50m |
| 2026-05-29 | MSR954 | HGH → CAI | May 29, 03:20 UTC | May 30, 03:00 UTC | 23h 40m |
| 2026-05-29 | MSR954 | HGH → CAI | May 29, 01:20 UTC | May 30, 00:40 UTC | 23h 20m |
| 2026-05-27 | MSR954 | HGH → CAI | May 27, 19:10 UTC | May 28, 02:50 UTC | 7h 40m |
| 2026-05-27 | MSR954 | HGH → CAI | May 27, 06:20 UTC | May 28, 02:50 UTC | 20h 30m |
| 2026-05-27 | MSR954 | HGH → CAI | May 27, 03:20 UTC | May 28, 02:50 UTC | 23h 30m |
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-GET page for operator, model, and routing details .