sensors Mode-S transponder
0100A7
ICAO 24-bit transponder address · allocated to Egypt
Currently assigned to SU-GCJ · AIRBUS A-330-200
- Hex
- 0100A7
- Octal
- 00200247
- Decimal
- 65,703
- Country
- EG
- Tail
- SU-GCJ
- Type
- A332
- Flights observed
- 48
- Distinct callsigns
- 20
- Country
- EG
- Last broadcast
- 2d ago
Last known position
Country allocation
The ICAO 24-bit address 0100A7 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 |
|---|---|---|---|
| MSR517 | Egyptair | 6 | 2026-05-27 |
| MSR518 | Egyptair | 5 | 2026-05-27 |
| MSR502 | Egyptair | 5 | 2026-05-10 |
| MSR503 | Egyptair | 4 | 2026-04-30 |
| MSR543 | Egyptair | 3 | 2026-05-23 |
| MSR542 | Egyptair | 3 | 2026-05-22 |
| MSR510 | Egyptair | 3 | 2026-05-02 |
| MSR521 | Egyptair | 2 | 2026-05-21 |
| MSR520 | Egyptair | 2 | 2026-05-21 |
| MSR509 | Egyptair | 2 | 2026-05-02 |
| MSR507 | Egyptair | 2 | 2026-05-11 |
| MSR5061 | Egyptair | 2 | 2026-05-17 |
| MSR5060 | Egyptair | 2 | 2026-05-17 |
| MSR5567 | Egyptair | 1 | 2026-05-03 |
| MSR5550 | Egyptair | 1 | 2026-05-03 |
| MSR5529 | Egyptair | 1 | 2026-05-03 |
| MSR533 | Egyptair | 1 | 2026-05-16 |
| MSR532 | Egyptair | 1 | 2026-05-16 |
| MSR511 | Egyptair | 1 | 2026-05-02 |
| MSR508 | Egyptair | 1 | 2026-05-11 |
Recent flights last 48
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-27 | MSR518 | BOM → CAI | May 27, 18:00 UTC | May 27, 23:20 UTC | 5h 20m |
| 2026-05-27 | MSR517 | CAI → BOM | May 27, 09:20 UTC | May 27, 14:55 UTC | 5h 35m |
| 2026-05-23 | MSR543 | IST → CAI | May 23, 03:50 UTC | May 23, 05:15 UTC | 1h 25m |
| 2026-05-22 | MSR542 | CAI → IST | May 22, 20:05 UTC | May 22, 21:35 UTC | 1h 30m |
| 2026-05-21 | MSR521 | OST → CAI | May 21, 13:45 UTC | May 21, 17:30 UTC | 3h 45m |
| 2026-05-21 | MSR520 | CAI → OST | May 21, 07:05 UTC | May 21, 11:10 UTC | 4h 5m |
| 2026-05-20 | MSR543 | IST → CAI | May 20, 00:10 UTC | May 20, 01:45 UTC | 1h 35m |
| 2026-05-19 | MSR542 | CAI → IST | May 19, 20:10 UTC | May 19, 21:45 UTC | 1h 35m |
| 2026-05-17 | MSR5061 | HHN → CAI | May 17, 13:45 UTC | May 17, 17:01 UTC | 3h 15m |
| 2026-05-17 | MSR5060 | CAI → HHN | May 17, 05:55 UTC | May 17, 09:40 UTC | 3h 45m |
| 2026-05-16 | MSR533 | MXP → CAI | May 16, 21:10 UTC | May 16, 23:55 UTC | 2h 45m |
| 2026-05-16 | MSR532 | CAI → MXP | May 16, 03:05 UTC | May 16, 19:25 UTC | 16h 21m |
| 2026-05-14 | MSR521 | OST → CAI | May 14, 22:45 UTC | May 15, 02:10 UTC | 3h 25m |
| 2026-05-14 | MSR520 | CAI → OST | May 14, 15:10 UTC | May 14, 19:20 UTC | 4h 10m |
| 2026-05-11 | MSR508 | BKK → CAI | May 11, 18:20 UTC | May 11, 22:35 UTC | 4h 14m |
| 2026-05-11 | MSR507 | CAI → BKK | May 11, 07:05 UTC | May 11, 15:35 UTC | 8h 30m |
| 2026-05-10 | MSR5061 | HHN → CAI | May 10, 23:50 UTC | May 11, 03:10 UTC | 3h 20m |
| 2026-05-10 | MSR5060 | CAI → HHN | May 10, 17:30 UTC | May 10, 21:04 UTC | 3h 35m |
| 2026-05-10 | MSR502 | CAI → DWC | May 10, 04:15 UTC | May 10, 14:04 UTC | 9h 50m |
| 2026-05-03 | MSR5529 | OST → CAI | May 3, 18:14 UTC | May 3, 21:50 UTC | 3h 35m |
| 2026-05-03 | MSR5567 | MXP → MJI | May 3, 13:25 UTC | May 3, 16:25 UTC | 3h 0m |
| 2026-05-03 | MSR5550 | CAI → MJI | May 3, 08:35 UTC | May 3, 10:45 UTC | 2h 10m |
| 2026-05-02 | MSR511 | BKK → CAI | May 2, 21:10 UTC | May 3, 06:25 UTC | 9h 14m |
| 2026-05-02 | MSR510 | HKG → BKK | May 2, 19:10 UTC | May 2, 19:35 UTC | 25m |
| 2026-05-02 | MSR510 | HKG → BKK | May 2, 17:15 UTC | May 2, 17:25 UTC | 10m |
| 2026-05-02 | MSR509 | CAI → HKG | May 2, 04:50 UTC | May 2, 12:05 UTC | 7h 15m |
| 2026-05-01 | MSR543 | IST → CAI | May 1, 23:00 UTC | May 2, 00:30 UTC | 1h 30m |
| 2026-05-01 | MSR542 | CAI → IST | May 1, 19:30 UTC | May 1, 21:00 UTC | 1h 30m |
| 2026-04-30 | MSR503 | DWC → CAI | Apr 30, 11:20 UTC | Apr 30, 15:15 UTC | 3h 55m |
| 2026-04-30 | MSR502 | CAI → DWC | Apr 30, 04:20 UTC | Apr 30, 07:35 UTC | 3h 15m |
| 2026-04-26 | MSR503 | DWC → CAI | Apr 26, 13:10 UTC | Apr 26, 16:45 UTC | 3h 35m |
| 2026-04-26 | MSR502 | CAI → DWC | Apr 26, 06:55 UTC | Apr 26, 10:00 UTC | 3h 5m |
| 2026-04-25 | MSR518 | BOM → CAI | Apr 25, 17:25 UTC | Apr 25, 22:55 UTC | 5h 30m |
| 2026-04-25 | MSR517 | CAI → BOM | Apr 25, 09:25 UTC | Apr 25, 14:45 UTC | 5h 20m |
| 2026-04-24 | MSR503 | - | Apr 24, 13:30 UTC | Apr 24, 16:55 UTC | 3h 25m |
| 2026-04-24 | MSR502 | CAI → DWC | Apr 24, 07:20 UTC | Apr 24, 10:25 UTC | 3h 5m |
| 2026-04-22 | MSR503 | - | Apr 22, 13:40 UTC | Apr 22, 17:30 UTC | 3h 50m |
| 2026-04-22 | MSR502 | CAI → DWC | Apr 22, 09:50 UTC | Apr 22, 10:55 UTC | 1h 5m |
| 2026-04-21 | MSR507 | - | Apr 21, 09:00 UTC | Apr 21, 14:40 UTC | 5h 40m |
| 2026-04-21 | MSR517 | CAI → BOM | Apr 21, 01:05 UTC | Apr 21, 06:15 UTC | 5h 10m |
| 2026-04-20 | MSR517 | CAI → BOM | Apr 20, 00:20 UTC | Apr 20, 11:40 UTC | 11h 20m |
| 2026-04-16 | MSR518 | BOM → CAI | Apr 16, 23:20 UTC | Apr 17, 00:20 UTC | 1h 0m |
| 2026-04-16 | MSR510 | - | Apr 16, 13:20 UTC | Apr 16, 13:35 UTC | 15m |
| 2026-04-15 | MSR509 | - | Apr 15, 17:05 UTC | Apr 15, 17:55 UTC | 50m |
| 2026-04-15 | MSR517 | - | Apr 15, 03:20 UTC | Apr 15, 04:20 UTC | 1h 0m |
| 2026-04-15 | MSR517 | - | Apr 15, 01:15 UTC | Apr 15, 01:25 UTC | 10m |
| 2026-04-13 | MSR518 | BOM → CAI | Apr 13, 09:35 UTC | Apr 13, 09:45 UTC | 10m |
| 2026-04-13 | MSR518 | BOM → CAI | Apr 13, 06:10 UTC | Apr 13, 07:25 UTC | 1h 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-GCJ page for operator, model, and routing details .