sensors Mode-S transponder
010280
ICAO 24-bit transponder address · allocated to Egypt
Currently assigned to SU-NMF · AIRBUS A-320
- Hex
- 010280
- Octal
- 00201200
- Decimal
- 66,176
- Country
- EG
- Tail
- SU-NMF
- Type
- A320
- Flights observed
- 326
- Distinct callsigns
- 20
- Country
- EG
- Last broadcast
- Jul 26, 22:00 UTC
Current position
Country allocation
The ICAO 24-bit address 010280 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 |
|---|---|---|---|
| NMA601 | - | 28 | 2026-07-20 |
| NMA603 | - | 24 | 2026-07-07 |
| NMA621 | - | 21 | 2026-07-19 |
| NMA619 | - | 18 | 2026-06-27 |
| NMA605 | - | 17 | 2026-07-12 |
| NMA617 | Nesma Airlines | 16 | 2026-07-22 |
| NMA606 | - | 13 | 2026-07-01 |
| NMA611 | Nesma Airlines | 11 | 2026-05-19 |
| NMA610 | Nesma Airlines | 10 | 2026-05-26 |
| NMA607 | Nesma Airlines | 10 | 2026-07-17 |
| NMA616 | Nesma Airlines | 9 | 2026-06-10 |
| NMA645 | Nesma Airlines | 8 | 2026-06-23 |
| NMA623 | - | 8 | 2026-05-15 |
| NMA618 | Nesma Airlines | 8 | 2026-06-13 |
| NMA600 | Nesma Airlines | 8 | 2026-07-19 |
| NMA491 | - | 8 | 2026-07-26 |
| NMA643 | Nesma Airlines | 6 | 2026-07-23 |
| NMA615 | Nesma Airlines | 6 | 2026-07-24 |
| NMA690 | Nesma Airlines | 5 | 2026-06-09 |
| NMA620 | - | 5 | 2026-06-25 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | NMA491 | - | Jul 26, 00:50 UTC | Jul 26, 22:00 UTC | 21h 11m |
| 2026-07-25 | NMA491 | - | Jul 25, 15:45 UTC | Jul 26, 03:50 UTC | 12h 5m |
| 2026-07-24 | NMA490 | - | Jul 24, 22:30 UTC | Jul 25, 17:50 UTC | 19h 20m |
| 2026-07-24 | NMA451 | JED → ATZ | Jul 24, 16:05 UTC | Jul 25, 16:00 UTC | 23h 55m |
| 2026-07-24 | NMA450 | ATZ → JED | Jul 24, 06:05 UTC | Jul 25, 00:30 UTC | 18h 25m |
| 2026-07-24 | NMA615 | VKO → HRG | Jul 24, 04:20 UTC | Jul 25, 00:30 UTC | 20h 10m |
| 2026-07-23 | NMA615 | VKO → HRG | Jul 23, 22:05 UTC | Jul 24, 16:05 UTC | 18h 0m |
| 2026-07-23 | NMA615 | VKO → HRG | Jul 23, 20:05 UTC | Jul 24, 16:05 UTC | 20h 0m |
| 2026-07-23 | NMA615 | VKO → HRG | Jul 23, 16:05 UTC | Jul 24, 16:00 UTC | 23h 55m |
| 2026-07-23 | NMA615 | VKO → HRG | Jul 23, 14:05 UTC | Jul 24, 14:00 UTC | 23h 55m |
| 2026-07-23 | NMA643 | VKO → SSH | Jul 23, 12:40 UTC | Jul 24, 07:35 UTC | 18h 55m |
| 2026-07-23 | NMA643 | VKO → SSH | Jul 23, 06:05 UTC | Jul 24, 06:00 UTC | 23h 55m |
| 2026-07-23 | NMA614 | HRG → VKO | Jul 23, 04:35 UTC | Jul 23, 22:10 UTC | 17h 35m |
| 2026-07-22 | NMA617 | VKO → SSH | Jul 22, 13:20 UTC | Jul 23, 00:45 UTC | 11h 25m |
| 2026-07-21 | NMA2271 | - | Jul 21, 10:40 UTC | Jul 22, 01:45 UTC | 15h 5m |
| 2026-07-21 | NMA2270 | - | Jul 21, 06:35 UTC | Jul 21, 09:15 UTC | 2h 40m |
| 2026-07-20 | NMA2270 | - | Jul 20, 12:05 UTC | Jul 21, 09:15 UTC | 21h 9m |
| 2026-07-20 | NMA2270 | - | Jul 20, 10:05 UTC | Jul 21, 09:15 UTC | 23h 10m |
| 2026-07-20 | NMA601 | - | Jul 20, 08:35 UTC | Jul 21, 08:00 UTC | 23h 25m |
| 2026-07-19 | NMA600 | HRG → VKO | Jul 19, 21:05 UTC | Jul 20, 12:20 UTC | 15h 15m |
| 2026-07-19 | NMA600 | HRG → VKO | Jul 19, 16:05 UTC | Jul 20, 12:20 UTC | 20h 15m |
| 2026-07-19 | NMA600 | HRG → VKO | Jul 19, 14:05 UTC | Jul 20, 12:20 UTC | 22h 15m |
| 2026-07-19 | NMA600 | HRG → VKO | Jul 19, 13:00 UTC | Jul 20, 12:00 UTC | 23h 0m |
| 2026-07-19 | NMA600 | HRG → VKO | Jul 19, 07:00 UTC | Jul 20, 00:55 UTC | 17h 55m |
| 2026-07-19 | NMA600 | HRG → VKO | Jul 19, 05:20 UTC | Jul 20, 00:55 UTC | 19h 35m |
| 2026-07-19 | NMA621 | - | Jul 19, 00:05 UTC | Jul 20, 00:00 UTC | 23h 55m |
| 2026-07-18 | NMA621 | - | Jul 18, 22:05 UTC | Jul 19, 22:00 UTC | 23h 55m |
| 2026-07-18 | NMA617 | VKO → SSH | Jul 18, 21:10 UTC | Jul 19, 16:40 UTC | 19h 30m |
| 2026-07-18 | NMA617 | VKO → SSH | Jul 18, 16:15 UTC | Jul 19, 16:00 UTC | 23h 45m |
| 2026-07-18 | NMA617 | VKO → SSH | Jul 18, 14:25 UTC | Jul 19, 14:00 UTC | 23h 35m |
| 2026-07-18 | NMA617 | VKO → SSH | Jul 18, 08:05 UTC | Jul 19, 07:30 UTC | 23h 25m |
| 2026-07-18 | NMA617 | VKO → SSH | Jul 18, 06:05 UTC | Jul 19, 05:55 UTC | 23h 50m |
| 2026-07-18 | NMA617 | VKO → SSH | Jul 18, 05:20 UTC | Jul 19, 01:20 UTC | 20h 0m |
| 2026-07-17 | NMA607 | VKO → HRG | Jul 17, 22:35 UTC | Jul 18, 22:00 UTC | 23h 26m |
| 2026-07-17 | NMA607 | VKO → HRG | Jul 17, 20:55 UTC | Jul 18, 16:35 UTC | 19h 41m |
| 2026-07-17 | NMA607 | VKO → HRG | Jul 17, 16:04 UTC | Jul 18, 15:30 UTC | 23h 26m |
| 2026-07-16 | NMA601 | - | Jul 16, 19:55 UTC | Jul 17, 12:25 UTC | 16h 30m |
| 2026-07-16 | NMA601 | - | Jul 16, 16:05 UTC | Jul 17, 12:25 UTC | 20h 20m |
| 2026-07-16 | NMA601 | - | Jul 16, 14:35 UTC | Jul 17, 12:25 UTC | 21h 50m |
| 2026-07-16 | NMA601 | - | Jul 16, 12:05 UTC | Jul 17, 12:00 UTC | 23h 55m |
| 2026-07-16 | NMA601 | - | Jul 16, 10:04 UTC | Jul 17, 06:40 UTC | 20h 35m |
| 2026-07-16 | NMA601 | - | Jul 16, 09:45 UTC | Jul 17, 06:40 UTC | 20h 55m |
| 2026-07-16 | NMA601 | - | Jul 16, 06:05 UTC | Jul 17, 06:00 UTC | 23h 55m |
| 2026-07-16 | NMA491 | - | Jul 16, 04:15 UTC | Jul 17, 03:59 UTC | 23h 45m |
| 2026-07-15 | NMA491 | - | Jul 15, 22:05 UTC | Jul 16, 22:00 UTC | 23h 55m |
| 2026-07-15 | NMA491 | - | Jul 15, 20:05 UTC | Jul 16, 20:00 UTC | 23h 55m |
| 2026-07-15 | NMA056 | - | Jul 15, 16:20 UTC | Jul 15, 16:40 UTC | 20m |
| 2026-07-13 | NMA057 | - | Jul 13, 07:10 UTC | Jul 13, 07:20 UTC | 10m |
| 2026-07-12 | NMA605 | - | Jul 12, 04:05 UTC | Jul 12, 23:15 UTC | 19h 10m |
| 2026-07-12 | NMA605 | - | Jul 12, 03:45 UTC | Jul 12, 23:15 UTC | 19h 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-NMF page for operator, model, and routing details .