sensors Mode-S transponder
01027D
ICAO 24-bit transponder address · allocated to Egypt
Currently assigned to SU-GGB · BOEING 737-800
- Hex
- 01027D
- Octal
- 00201175
- Decimal
- 66,173
- Country
- EG
- Tail
- SU-GGB
- Type
- B738
- Flights observed
- 75
- Distinct callsigns
- 20
- Country
- EG
- Last broadcast
- 2h ago
Last known position
Country allocation
The ICAO 24-bit address 01027D 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 |
|---|---|---|---|
| MSR020 | Egyptair | 13 | 2026-05-06 |
| MSR2753 | Egyptair | 8 | 2026-05-30 |
| MSR021 | Egyptair | 8 | 2026-05-07 |
| MSR726 | Egyptair | 5 | 2026-05-28 |
| MSR2754 | Egyptair | 4 | 2026-05-25 |
| MSR914 | Egyptair | 3 | 2026-05-10 |
| MSR725 | Egyptair | 3 | 2026-05-28 |
| MSR704 | - | 3 | 2026-04-15 |
| MSR080 | Egyptair | 3 | 2026-05-24 |
| MSR767 | Egyptair | 2 | 2026-04-26 |
| MSR703 | Egyptair | 2 | 2026-04-15 |
| MSR694 | Egyptair | 2 | 2026-05-21 |
| MSR2768 | Egyptair | 2 | 2026-05-23 |
| MSR2767 | Egyptair | 2 | 2026-05-22 |
| MSR936 | Egyptair | 1 | 2026-05-13 |
| MSR915 | - | 1 | 2026-04-17 |
| MSR788 | - | 1 | 2026-04-18 |
| MSR787 | Egyptair | 1 | 2026-04-18 |
| MSR768 | Egyptair | 1 | 2026-04-26 |
| MSR720 | Egyptair | 1 | 2026-04-29 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-30 | MSR2753 | CAI → MAD | May 30, 06:30 UTC | May 30, 09:15 UTC | 2h 45m |
| 2026-05-28 | MSR726 | BRU → CAI | May 28, 14:55 UTC | May 28, 18:35 UTC | 3h 40m |
| 2026-05-28 | MSR725 | CAI → BRU | May 28, 09:00 UTC | May 28, 13:30 UTC | 4h 30m |
| 2026-05-27 | MSR241 | HRG → CAI | May 27, 07:40 UTC | May 27, 07:50 UTC | 10m |
| 2026-05-25 | MSR2754 | MAD → LXR | May 25, 12:25 UTC | May 26, 03:45 UTC | 15h 19m |
| 2026-05-25 | MSR2753 | CAI → MAD | May 25, 07:25 UTC | May 25, 10:40 UTC | 3h 15m |
| 2026-05-24 | MSR080 | CAI → ASW | May 24, 21:25 UTC | May 24, 21:35 UTC | 10m |
| 2026-05-24 | MSR660 | JED → CAI | May 24, 03:25 UTC | May 24, 07:50 UTC | 4h 25m |
| 2026-05-23 | MSR2768 | BCN → LXR | May 23, 12:15 UTC | May 23, 14:50 UTC | 2h 35m |
| 2026-05-22 | MSR2767 | CAI → BCN | May 22, 21:50 UTC | May 23, 10:30 UTC | 12h 39m |
| 2026-05-21 | MSR694 | MED → CAI | May 21, 00:05 UTC | May 21, 04:10 UTC | 4h 5m |
| 2026-05-20 | MSR049 | HRG → CAI | May 20, 20:25 UTC | May 20, 20:35 UTC | 10m |
| 2026-05-19 | MSR678 | MED → CAI | May 19, 15:00 UTC | May 19, 19:00 UTC | 4h 0m |
| 2026-05-19 | MSR651 | CAI → RUH | May 19, 06:45 UTC | May 19, 12:20 UTC | 5h 35m |
| 2026-05-18 | MSR2754 | MAD → LXR | May 18, 13:35 UTC | May 18, 16:30 UTC | 2h 55m |
| 2026-05-18 | MSR2753 | CAI → MAD | May 18, 07:00 UTC | May 18, 11:45 UTC | 4h 45m |
| 2026-05-17 | MSR2753 | CAI → MAD | May 17, 16:40 UTC | May 18, 11:45 UTC | 19h 5m |
| 2026-05-16 | MSR633 | - | May 16, 15:55 UTC | May 16, 20:20 UTC | 4h 25m |
| 2026-05-15 | MSR726 | BRU → CAI | May 15, 17:20 UTC | May 16, 12:01 UTC | 18h 41m |
| 2026-05-15 | MSR726 | BRU → CAI | May 15, 15:20 UTC | May 16, 12:01 UTC | 20h 41m |
| 2026-05-15 | MSR726 | BRU → CAI | May 15, 14:55 UTC | May 16, 12:01 UTC | 21h 6m |
| 2026-05-15 | MSR725 | CAI → BRU | May 15, 08:55 UTC | May 15, 13:10 UTC | 4h 15m |
| 2026-05-13 | MSR936 | DOH → CAI | May 13, 11:25 UTC | May 13, 14:40 UTC | 3h 15m |
| 2026-05-11 | MSR726 | BRU → CAI | May 11, 15:00 UTC | May 11, 18:20 UTC | 3h 20m |
| 2026-05-11 | MSR725 | CAI → BRU | May 11, 08:55 UTC | May 11, 13:20 UTC | 4h 25m |
| 2026-05-10 | MSR694 | MED → CAI | May 10, 23:29 UTC | May 11, 02:45 UTC | 3h 15m |
| 2026-05-10 | MSR914 | CAI → AUH | May 10, 11:05 UTC | May 10, 17:05 UTC | 6h 0m |
| 2026-05-09 | MSR688 | DMM → CAI | May 9, 20:00 UTC | May 9, 20:20 UTC | 20m |
| 2026-05-09 | MSR652 | RUH → CAI | May 9, 06:40 UTC | May 9, 12:10 UTC | 5h 30m |
| 2026-05-08 | MSR080 | CAI → ASW | May 8, 20:40 UTC | May 8, 20:50 UTC | 10m |
| 2026-05-07 | MSR080 | CAI → ASW | May 7, 21:35 UTC | May 7, 21:45 UTC | 10m |
| 2026-05-07 | MSR021 | SSH → CAI | May 7, 03:15 UTC | May 7, 03:25 UTC | 10m |
| 2026-05-06 | MSR020 | CAI → SSH | May 6, 21:50 UTC | May 6, 22:05 UTC | 15m |
| 2026-05-01 | MSR021 | SSH → CAI | May 1, 03:30 UTC | May 1, 03:40 UTC | 10m |
| 2026-04-30 | MSR020 | CAI → SSH | Apr 30, 21:55 UTC | Apr 30, 22:10 UTC | 15m |
| 2026-04-30 | MSR021 | SSH → CAI | Apr 30, 03:20 UTC | Apr 30, 03:45 UTC | 25m |
| 2026-04-29 | MSR020 | CAI → SSH | Apr 29, 22:05 UTC | Apr 29, 22:25 UTC | 20m |
| 2026-04-29 | MSR720 | AMM → CAI | Apr 29, 07:10 UTC | Apr 29, 07:50 UTC | 40m |
| 2026-04-29 | MSR719 | CAI → AMM | Apr 29, 05:09 UTC | Apr 29, 05:45 UTC | 35m |
| 2026-04-28 | MSR021 | SSH → CAI | Apr 28, 03:10 UTC | Apr 28, 03:30 UTC | 20m |
| 2026-04-27 | MSR2754 | MAD → LXR | Apr 27, 13:05 UTC | Apr 27, 16:15 UTC | 3h 10m |
| 2026-04-27 | MSR2753 | CAI → MAD | Apr 27, 06:40 UTC | Apr 27, 11:20 UTC | 4h 40m |
| 2026-04-26 | MSR768 | BCN → CAI | Apr 26, 15:10 UTC | Apr 26, 18:30 UTC | 3h 20m |
| 2026-04-26 | MSR767 | CAI → BCN | Apr 26, 09:40 UTC | Apr 26, 13:15 UTC | 3h 35m |
| 2026-04-25 | MSR767 | CAI → BCN | Apr 25, 13:20 UTC | Apr 26, 13:15 UTC | 23h 55m |
| 2026-04-25 | MSR2768 | BCN → LXR | Apr 25, 11:35 UTC | Apr 26, 11:15 UTC | 23h 40m |
| 2026-04-25 | MSR2767 | CAI → BCN | Apr 25, 06:10 UTC | Apr 25, 10:05 UTC | 3h 55m |
| 2026-04-25 | MSR021 | SSH → CAI | Apr 25, 03:05 UTC | Apr 25, 03:20 UTC | 15m |
| 2026-04-24 | MSR020 | CAI → SSH | Apr 24, 21:45 UTC | Apr 24, 22:00 UTC | 15m |
| 2026-04-23 | MSR020 | CAI → SSH | Apr 23, 21:55 UTC | Apr 23, 22:10 UTC | 15m |
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-GGB page for operator, model, and routing details .