sensors Mode-S transponder
01027C
ICAO 24-bit transponder address · allocated to Egypt
Currently assigned to SU-NMZ · AIRBUS A-320
- Hex
- 01027C
- Octal
- 00201174
- Decimal
- 66,172
- Country
- EG
- Tail
- SU-NMZ
- Type
- A320
- Flights observed
- 271
- Distinct callsigns
- 20
- Country
- EG
- Last broadcast
- Jul 26, 23:00 UTC
Current position
Country allocation
The ICAO 24-bit address 01027C 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 |
|---|---|---|---|
| NMA646 | - | 32 | 2026-07-19 |
| NMA647 | - | 21 | 2026-07-16 |
| NMA690 | Nesma Airlines | 15 | 2026-07-21 |
| NMA658 | - | 14 | 2026-07-16 |
| NMA438 | Nesma Airlines | 13 | 2026-07-07 |
| NMA689 | Nesma Airlines | 11 | 2026-07-19 |
| NMA607 | Nesma Airlines | 10 | 2026-05-23 |
| NMA688 | - | 9 | 2026-07-01 |
| NMA618 | Nesma Airlines | 9 | 2026-06-06 |
| NMA691 | Nesma Airlines | 7 | 2026-05-20 |
| NMA678 | - | 7 | 2026-07-06 |
| NMA603 | Nesma Airlines | 7 | 2026-07-23 |
| NMA616 | Nesma Airlines | 6 | 2026-07-24 |
| NMA606 | Nesma Airlines | 6 | 2026-05-17 |
| NMA605 | Nesma Airlines | 6 | 2026-05-18 |
| NMA602 | Nesma Airlines | 6 | 2026-07-22 |
| NMA600 | Nesma Airlines | 6 | 2026-07-23 |
| NMA650 | Nesma Airlines | 5 | 2026-07-24 |
| NMA601 | Nesma Airlines | 5 | 2026-05-16 |
| NMA696 | Nesma Airlines | 4 | 2026-06-23 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-25 | NMA621 | AER → HRG | Jul 25, 23:05 UTC | Jul 26, 23:00 UTC | 23h 56m |
| 2026-07-25 | NMA621 | AER → HRG | Jul 25, 17:05 UTC | Jul 26, 16:55 UTC | 23h 51m |
| 2026-07-25 | NMA617 | VKO → SSH | Jul 25, 15:05 UTC | Jul 26, 15:00 UTC | 23h 56m |
| 2026-07-24 | NMA616 | SSH → VKO | Jul 24, 23:05 UTC | Jul 25, 17:15 UTC | 18h 10m |
| 2026-07-24 | NMA650 | HRG → KZN | Jul 24, 22:20 UTC | Jul 25, 17:15 UTC | 18h 55m |
| 2026-07-24 | NMA650 | HRG → KZN | Jul 24, 17:20 UTC | Jul 25, 17:00 UTC | 23h 40m |
| 2026-07-24 | NMA650 | HRG → KZN | Jul 24, 11:10 UTC | Jul 25, 00:30 UTC | 13h 20m |
| 2026-07-23 | NMA600 | HRG → VKO | Jul 23, 21:05 UTC | Jul 24, 17:55 UTC | 20h 50m |
| 2026-07-23 | NMA600 | HRG → VKO | Jul 23, 15:35 UTC | Jul 24, 13:00 UTC | 21h 25m |
| 2026-07-23 | NMA603 | VKO → HRG | Jul 23, 05:05 UTC | Jul 23, 23:20 UTC | 18h 15m |
| 2026-07-23 | NMA603 | VKO → HRG | Jul 23, 03:55 UTC | Jul 23, 23:20 UTC | 19h 25m |
| 2026-07-22 | NMA603 | VKO → HRG | Jul 22, 21:05 UTC | Jul 23, 16:25 UTC | 19h 20m |
| 2026-07-22 | NMA603 | VKO → HRG | Jul 22, 19:30 UTC | Jul 23, 16:25 UTC | 20h 55m |
| 2026-07-22 | NMA602 | HRG → VKO | Jul 22, 05:20 UTC | Jul 23, 05:00 UTC | 23h 40m |
| 2026-07-21 | NMA602 | HRG → VKO | Jul 21, 23:05 UTC | Jul 22, 21:30 UTC | 22h 25m |
| 2026-07-21 | NMA690 | HRG → LED | Jul 21, 21:05 UTC | Jul 22, 21:00 UTC | 23h 55m |
| 2026-07-21 | NMA690 | HRG → LED | Jul 21, 15:40 UTC | Jul 22, 05:25 UTC | 13h 45m |
| 2026-07-20 | NMA642 | - | Jul 20, 18:10 UTC | Jul 21, 12:10 UTC | 17h 59m |
| 2026-07-20 | NMA1471 | - | Jul 20, 06:25 UTC | Jul 20, 08:15 UTC | 1h 50m |
| 2026-07-19 | NMA646 | - | Jul 19, 13:30 UTC | Jul 20, 04:10 UTC | 14h 40m |
| 2026-07-19 | NMA689 | AER → SSH | Jul 19, 07:05 UTC | Jul 20, 04:10 UTC | 21h 5m |
| 2026-07-19 | NMA689 | AER → SSH | Jul 19, 06:55 UTC | Jul 20, 04:10 UTC | 21h 15m |
| 2026-07-19 | NMA689 | AER → SSH | Jul 19, 03:05 UTC | Jul 20, 03:00 UTC | 23h 55m |
| 2026-07-19 | NMA689 | AER → SSH | Jul 19, 02:55 UTC | Jul 19, 15:40 UTC | 12h 45m |
| 2026-07-18 | NMA648 | - | Jul 18, 09:05 UTC | Jul 19, 00:45 UTC | 15h 40m |
| 2026-07-17 | NMA646 | - | Jul 17, 13:29 UTC | Jul 18, 07:15 UTC | 17h 46m |
| 2026-07-16 | NMA646 | - | Jul 16, 19:14 UTC | Jul 17, 15:40 UTC | 20h 25m |
| 2026-07-16 | NMA658 | - | Jul 16, 09:20 UTC | Jul 16, 19:45 UTC | 10h 25m |
| 2026-07-16 | NMA647 | - | Jul 16, 03:25 UTC | Jul 16, 06:40 UTC | 3h 15m |
| 2026-07-16 | NMA646 | - | Jul 16, 00:15 UTC | Jul 16, 00:25 UTC | 10m |
| 2026-07-15 | NMA646 | - | Jul 15, 19:35 UTC | Jul 15, 21:50 UTC | 2h 15m |
| 2026-07-15 | NMA689 | - | Jul 15, 12:10 UTC | Jul 15, 14:00 UTC | 1h 50m |
| 2026-07-14 | NMA439 | - | Jul 14, 17:30 UTC | Jul 15, 09:25 UTC | 15h 54m |
| 2026-07-13 | NMA614 | - | Jul 13, 23:00 UTC | Jul 14, 11:20 UTC | 12h 20m |
| 2026-07-13 | NMA614 | - | Jul 13, 05:05 UTC | Jul 14, 01:20 UTC | 20h 15m |
| 2026-07-13 | NMA7191 | - | Jul 13, 03:20 UTC | Jul 14, 01:20 UTC | 22h 0m |
| 2026-07-12 | NMA615 | - | Jul 12, 10:45 UTC | Jul 13, 01:55 UTC | 15h 10m |
| 2026-07-11 | NMA615 | - | Jul 11, 21:05 UTC | Jul 12, 14:05 UTC | 17h 0m |
| 2026-07-11 | NMA647 | - | Jul 11, 09:20 UTC | Jul 11, 13:00 UTC | 3h 40m |
| 2026-07-11 | NMA647 | - | Jul 11, 08:25 UTC | Jul 11, 08:35 UTC | 10m |
| 2026-07-10 | NMA646 | SSH → VKO | Jul 10, 14:15 UTC | Jul 10, 16:25 UTC | 2h 10m |
| 2026-07-09 | NMA659 | - | Jul 9, 19:20 UTC | Jul 9, 19:30 UTC | 10m |
| 2026-07-09 | NMA647 | - | Jul 9, 01:50 UTC | Jul 9, 02:00 UTC | 10m |
| 2026-07-08 | NMA646 | SSH → VKO | Jul 8, 09:35 UTC | Jul 8, 21:40 UTC | 12h 5m |
| 2026-07-07 | NMA438 | SSH → SVX | Jul 7, 17:30 UTC | Jul 7, 19:05 UTC | 1h 35m |
| 2026-07-07 | NMA679 | - | Jul 7, 06:40 UTC | Jul 7, 17:25 UTC | 10h 45m |
| 2026-07-06 | NMA678 | - | Jul 6, 11:20 UTC | Jul 7, 04:05 UTC | 16h 45m |
| 2026-07-06 | NMA678 | - | Jul 6, 07:50 UTC | Jul 7, 04:05 UTC | 20h 15m |
| 2026-07-06 | NMA678 | - | Jul 6, 07:00 UTC | Jul 7, 04:05 UTC | 21h 5m |
| 2026-07-06 | NMA658 | - | Jul 6, 03:10 UTC | Jul 7, 03:00 UTC | 23h 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-NMZ page for operator, model, and routing details .