sensors Mode-S transponder
01015D
ICAO 24-bit transponder address · allocated to Egypt
Currently assigned to SU-GDU · AIRBUS A-330-300
- Hex
- 01015D
- Octal
- 00200535
- Decimal
- 65,885
- Country
- EG
- Tail
- SU-GDU
- Type
- A333
- Flights observed
- 112
- Distinct callsigns
- 20
- Country
- EG
- Last broadcast
- 11h ago
Last known position
Country allocation
The ICAO 24-bit address 01015D 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 |
|---|---|---|---|
| MSR727 | Egyptair | 68 | 2026-05-03 |
| MSR728 | Egyptair | 14 | 2026-05-03 |
| MSR935 | Egyptair | 2 | 2026-05-24 |
| MSR840 | Egyptair | 2 | 2026-05-18 |
| MSR694 | Egyptair | 2 | 2026-05-25 |
| MSR672 | Egyptair | 2 | 2026-05-29 |
| MSR652 | Egyptair | 2 | 2026-05-25 |
| MSR642 | Egyptair | 2 | 2026-05-16 |
| MSR1728 | Egyptair | 2 | 2026-04-16 |
| MSR966 | Egyptair | 1 | 2026-05-23 |
| MSR936 | Egyptair | 1 | 2026-05-24 |
| MSR914 | Egyptair | 1 | 2026-05-26 |
| MSR696 | Egyptair | 1 | 2026-05-16 |
| MSR680 | Egyptair | 1 | 2026-05-15 |
| MSR679 | Egyptair | 1 | 2026-05-15 |
| MSR675 | Egyptair | 1 | 2026-05-24 |
| MSR651 | Egyptair | 1 | 2026-04-15 |
| MSR646 | - | 1 | 2026-05-11 |
| MSR6090 | - | 1 | 2026-05-21 |
| MSR6082 | - | 1 | 2026-05-21 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | MSR672 | JED → CAI | May 29, 16:55 UTC | May 29, 17:15 UTC | 20m |
| 2026-05-26 | MSR914 | CAI → AUH | May 26, 08:39 UTC | May 26, 17:50 UTC | 9h 10m |
| 2026-05-25 | MSR694 | MED → CAI | May 25, 23:54 UTC | May 26, 03:45 UTC | 3h 50m |
| 2026-05-25 | MSR652 | RUH → CAI | May 25, 06:40 UTC | May 25, 12:25 UTC | 5h 45m |
| 2026-05-24 | MSR675 | CAI → MED | May 24, 20:35 UTC | May 24, 21:00 UTC | 25m |
| 2026-05-24 | MSR936 | DOH → CAI | May 24, 14:05 UTC | May 24, 14:30 UTC | 25m |
| 2026-05-24 | MSR935 | CAI → DOH | May 24, 09:30 UTC | May 24, 10:15 UTC | 45m |
| 2026-05-23 | MSR966 | CAI → SHJ | May 23, 19:15 UTC | May 24, 04:45 UTC | 9h 30m |
| 2026-05-23 | MSR935 | CAI → DOH | May 23, 07:40 UTC | May 23, 07:55 UTC | 15m |
| 2026-05-21 | MSR6090 | - | May 21, 17:35 UTC | May 21, 21:00 UTC | 3h 25m |
| 2026-05-21 | MSR6082 | - | May 21, 14:40 UTC | May 21, 14:50 UTC | 10m |
| 2026-05-21 | MSR6078 | MED → CAI | May 21, 04:25 UTC | May 21, 08:05 UTC | 3h 40m |
| 2026-05-20 | MSR6072 | - | May 20, 13:00 UTC | May 20, 16:30 UTC | 3h 30m |
| 2026-05-20 | MSR6068 | MED → CAI | May 20, 09:10 UTC | May 20, 09:25 UTC | 15m |
| 2026-05-19 | MSR6058 | - | May 19, 03:15 UTC | May 19, 16:05 UTC | 12h 50m |
| 2026-05-18 | MSR840 | JNB → CAI | May 18, 19:50 UTC | May 19, 16:05 UTC | 20h 15m |
| 2026-05-16 | MSR642 | JED → CAI | May 16, 19:45 UTC | May 16, 20:05 UTC | 20m |
| 2026-05-16 | MSR696 | MED → CAI | May 16, 09:45 UTC | May 16, 10:01 UTC | 15m |
| 2026-05-15 | MSR642 | JED → CAI | May 15, 20:05 UTC | May 15, 20:20 UTC | 15m |
| 2026-05-15 | MSR680 | MED → HBE | May 15, 10:55 UTC | May 15, 11:05 UTC | 10m |
| 2026-05-15 | MSR679 | HBE → MED | May 15, 07:05 UTC | May 15, 07:15 UTC | 10m |
| 2026-05-15 | MSR694 | MED → CAI | May 15, 04:00 UTC | May 15, 04:15 UTC | 15m |
| 2026-05-13 | MSR840 | JNB → CAI | May 13, 19:45 UTC | May 14, 03:25 UTC | 7h 40m |
| 2026-05-12 | MSR672 | JED → CAI | May 12, 09:35 UTC | May 12, 17:20 UTC | 7h 45m |
| 2026-05-11 | MSR6008 | MED → CAI | May 11, 13:45 UTC | May 11, 14:00 UTC | 15m |
| 2026-05-11 | MSR646 | - | May 11, 06:00 UTC | May 11, 06:15 UTC | 15m |
| 2026-05-03 | MSR728 | DME → CAI | May 3, 23:15 UTC | May 4, 03:05 UTC | 3h 50m |
| 2026-05-03 | MSR727 | CAI → DME | May 3, 20:10 UTC | May 3, 20:20 UTC | 10m |
| 2026-05-03 | MSR727 | CAI → DME | May 3, 01:20 UTC | May 3, 19:34 UTC | 18h 14m |
| 2026-05-03 | MSR727 | CAI → DME | May 3, 00:55 UTC | May 3, 19:34 UTC | 18h 39m |
| 2026-05-02 | MSR727 | CAI → DME | May 2, 15:10 UTC | May 2, 19:30 UTC | 4h 20m |
| 2026-05-01 | MSR727 | CAI → DME | May 1, 15:10 UTC | May 2, 02:55 UTC | 11h 45m |
| 2026-05-01 | MSR727 | CAI → DME | May 1, 01:20 UTC | May 2, 01:15 UTC | 23h 55m |
| 2026-04-30 | MSR727 | CAI → DME | Apr 30, 23:20 UTC | May 1, 19:45 UTC | 20h 25m |
| 2026-04-30 | MSR727 | CAI → DME | Apr 30, 23:05 UTC | May 1, 19:45 UTC | 20h 40m |
| 2026-04-30 | MSR727 | CAI → DME | Apr 30, 19:20 UTC | May 1, 19:15 UTC | 23h 55m |
| 2026-04-30 | MSR727 | CAI → DME | Apr 30, 17:20 UTC | May 1, 17:15 UTC | 23h 55m |
| 2026-04-30 | MSR727 | CAI → DME | Apr 30, 15:25 UTC | May 1, 15:15 UTC | 23h 50m |
| 2026-04-30 | MSR727 | CAI → DME | Apr 30, 03:20 UTC | May 1, 02:55 UTC | 23h 35m |
| 2026-04-30 | MSR727 | CAI → DME | Apr 30, 01:45 UTC | May 1, 01:15 UTC | 23h 30m |
| 2026-04-29 | MSR727 | CAI → DME | Apr 29, 19:20 UTC | Apr 30, 19:15 UTC | 23h 55m |
| 2026-04-29 | MSR727 | CAI → DME | Apr 29, 17:20 UTC | Apr 30, 17:15 UTC | 23h 55m |
| 2026-04-29 | MSR727 | CAI → DME | Apr 29, 15:45 UTC | Apr 30, 03:40 UTC | 11h 54m |
| 2026-04-28 | MSR727 | CAI → DME | Apr 28, 16:20 UTC | Apr 29, 03:40 UTC | 11h 20m |
| 2026-04-28 | MSR727 | CAI → DME | Apr 28, 03:20 UTC | Apr 29, 03:15 UTC | 23h 55m |
| 2026-04-28 | MSR727 | CAI → DME | Apr 28, 01:20 UTC | Apr 29, 01:15 UTC | 23h 55m |
| 2026-04-28 | MSR727 | CAI → DME | Apr 28, 00:50 UTC | Apr 28, 20:45 UTC | 19h 55m |
| 2026-04-27 | MSR727 | CAI → DME | Apr 27, 19:20 UTC | Apr 28, 19:15 UTC | 23h 55m |
| 2026-04-27 | MSR727 | CAI → DME | Apr 27, 17:20 UTC | Apr 28, 17:15 UTC | 23h 55m |
| 2026-04-27 | MSR727 | CAI → DME | Apr 27, 15:35 UTC | Apr 28, 03:40 UTC | 12h 5m |
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-GDU page for operator, model, and routing details .