sensors Mode-S transponder
010274
ICAO 24-bit transponder address · allocated to Egypt
Currently assigned to SU-NMH · AIRBUS A-320
- Hex
- 010274
- Octal
- 00201164
- Decimal
- 66,164
- Country
- EG
- Tail
- SU-NMH
- Type
- A320
- Flights observed
- 306
- Distinct callsigns
- 20
- Country
- EG
- Last broadcast
- Jul 26, 21:05 UTC
Last known position
Country allocation
The ICAO 24-bit address 010274 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 |
|---|---|---|---|
| NMA605 | Nesma Airlines | 23 | 2026-07-24 |
| NMA604 | Nesma Airlines | 23 | 2026-07-20 |
| NMA600 | - | 21 | 2026-07-17 |
| NMA491 | - | 17 | 2026-07-23 |
| NMA601 | Nesma Airlines | 14 | 2026-07-26 |
| NMA618 | - | 13 | 2026-07-02 |
| NMA690 | - | 12 | 2026-07-07 |
| NMA619 | Nesma Airlines | 11 | 2026-06-16 |
| NMA602 | - | 11 | 2026-07-03 |
| NMA616 | Nesma Airlines | 10 | 2026-06-03 |
| NMA603 | Nesma Airlines | 10 | 2026-05-28 |
| NMA606 | Nesma Airlines | 9 | 2026-06-17 |
| NMA617 | Nesma Airlines | 8 | 2026-06-04 |
| NMA607 | - | 7 | 2026-07-15 |
| NMA493 | Nesma Airlines | 7 | 2026-07-25 |
| NMA650 | Nesma Airlines | 6 | 2026-07-17 |
| NMA643 | Nesma Airlines | 6 | 2026-06-14 |
| NMA623 | - | 6 | 2026-05-25 |
| NMA444 | - | 6 | 2026-07-12 |
| NMA635 | Nesma Airlines | 5 | 2026-06-18 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | NMA601 | VKO → HRG | Jul 26, 04:10 UTC | Jul 26, 21:05 UTC | 16h 56m |
| 2026-07-25 | NMA601 | VKO → HRG | Jul 25, 21:30 UTC | Jul 26, 21:00 UTC | 23h 31m |
| 2026-07-25 | NMA601 | VKO → HRG | Jul 25, 19:55 UTC | Jul 26, 19:00 UTC | 23h 6m |
| 2026-07-25 | NMA493 | VKO → HRG | Jul 25, 05:05 UTC | Jul 26, 05:00 UTC | 23h 55m |
| 2026-07-25 | NMA493 | VKO → HRG | Jul 25, 03:30 UTC | Jul 25, 22:05 UTC | 18h 35m |
| 2026-07-24 | NMA493 | VKO → HRG | Jul 24, 21:20 UTC | Jul 25, 20:45 UTC | 23h 25m |
| 2026-07-24 | NMA493 | VKO → HRG | Jul 24, 19:45 UTC | Jul 25, 06:25 UTC | 10h 40m |
| 2026-07-24 | NMA605 | VKO → HRG | Jul 24, 05:05 UTC | Jul 25, 05:00 UTC | 23h 55m |
| 2026-07-24 | NMA605 | VKO → HRG | Jul 24, 03:45 UTC | Jul 24, 21:50 UTC | 18h 5m |
| 2026-07-23 | NMA605 | VKO → HRG | Jul 23, 19:10 UTC | Jul 24, 06:50 UTC | 11h 40m |
| 2026-07-23 | NMA605 | VKO → HRG | Jul 23, 07:05 UTC | Jul 24, 06:50 UTC | 23h 45m |
| 2026-07-23 | NMA491 | - | Jul 23, 05:05 UTC | Jul 24, 05:00 UTC | 23h 55m |
| 2026-07-22 | NMA491 | - | Jul 22, 21:05 UTC | Jul 23, 19:45 UTC | 22h 40m |
| 2026-07-22 | NMA491 | - | Jul 22, 20:00 UTC | Jul 23, 08:05 UTC | 12h 5m |
| 2026-07-22 | NMA490 | - | Jul 22, 01:05 UTC | Jul 22, 22:15 UTC | 21h 10m |
| 2026-07-21 | NMA611 | - | Jul 21, 23:05 UTC | Jul 22, 22:15 UTC | 23h 10m |
| 2026-07-21 | NMA611 | - | Jul 21, 22:45 UTC | Jul 22, 20:55 UTC | 22h 10m |
| 2026-07-21 | NMA610 | - | Jul 21, 14:30 UTC | Jul 22, 02:00 UTC | 11h 30m |
| 2026-07-20 | NMA604 | HRG → VKO | Jul 20, 21:50 UTC | Jul 21, 08:45 UTC | 10h 54m |
| 2026-07-20 | NMA604 | HRG → VKO | Jul 20, 07:05 UTC | Jul 21, 07:00 UTC | 23h 55m |
| 2026-07-20 | NMA604 | HRG → VKO | Jul 20, 05:05 UTC | Jul 21, 01:05 UTC | 19h 59m |
| 2026-07-20 | NMA604 | HRG → VKO | Jul 20, 04:10 UTC | Jul 21, 01:05 UTC | 20h 54m |
| 2026-07-19 | NMA611 | - | Jul 19, 19:25 UTC | Jul 20, 07:05 UTC | 11h 40m |
| 2026-07-19 | NMA601 | - | Jul 19, 05:05 UTC | Jul 20, 05:00 UTC | 23h 55m |
| 2026-07-19 | NMA601 | - | Jul 19, 03:15 UTC | Jul 19, 21:35 UTC | 18h 20m |
| 2026-07-18 | NMA601 | - | Jul 18, 19:45 UTC | Jul 19, 06:35 UTC | 10h 50m |
| 2026-07-18 | NMA601 | - | Jul 18, 09:05 UTC | Jul 19, 06:35 UTC | 21h 30m |
| 2026-07-17 | NMA600 | - | Jul 17, 23:05 UTC | Jul 18, 22:00 UTC | 22h 56m |
| 2026-07-17 | NMA650 | HRG → KZN | Jul 17, 22:20 UTC | Jul 18, 20:45 UTC | 22h 26m |
| 2026-07-17 | NMA650 | HRG → KZN | Jul 17, 16:00 UTC | Jul 18, 09:40 UTC | 17h 41m |
| 2026-07-17 | NMA660 | HRG → GSV | Jul 17, 08:45 UTC | Jul 17, 11:04 UTC | 2h 20m |
| 2026-07-16 | NMA604 | - | Jul 16, 18:50 UTC | Jul 17, 06:15 UTC | 11h 25m |
| 2026-07-16 | NMA801 | - | Jul 16, 12:40 UTC | Jul 16, 16:09 UTC | 3h 30m |
| 2026-07-15 | NMA607 | - | Jul 15, 22:25 UTC | Jul 16, 11:25 UTC | 13h 0m |
| 2026-07-15 | NMA607 | - | Jul 15, 15:05 UTC | Jul 16, 11:25 UTC | 20h 20m |
| 2026-07-15 | NMA607 | - | Jul 15, 14:25 UTC | Jul 16, 11:25 UTC | 21h 0m |
| 2026-07-15 | NMA601 | - | Jul 15, 07:50 UTC | Jul 15, 10:05 UTC | 2h 15m |
| 2026-07-15 | NMA601 | - | Jul 15, 05:35 UTC | Jul 15, 05:50 UTC | 15m |
| 2026-07-14 | NMA605 | - | Jul 14, 07:45 UTC | Jul 15, 01:25 UTC | 17h 39m |
| 2026-07-13 | NMA605 | - | Jul 13, 23:05 UTC | Jul 14, 20:35 UTC | 21h 30m |
| 2026-07-13 | NMA605 | - | Jul 13, 22:10 UTC | Jul 14, 20:35 UTC | 22h 25m |
| 2026-07-13 | NMA604 | - | Jul 13, 06:30 UTC | Jul 14, 00:15 UTC | 17h 45m |
| 2026-07-12 | NMA445 | - | Jul 12, 23:05 UTC | Jul 13, 23:00 UTC | 23h 55m |
| 2026-07-12 | NMA444 | - | Jul 12, 21:10 UTC | Jul 13, 07:25 UTC | 10h 15m |
| 2026-07-12 | NMA444 | - | Jul 12, 07:05 UTC | Jul 13, 07:01 UTC | 23h 55m |
| 2026-07-12 | NMA620 | - | Jul 12, 05:15 UTC | Jul 12, 23:25 UTC | 18h 10m |
| 2026-07-12 | NMA620 | - | Jul 12, 01:05 UTC | Jul 12, 23:25 UTC | 22h 20m |
| 2026-07-11 | NMA491 | - | Jul 11, 23:05 UTC | Jul 12, 23:00 UTC | 23h 55m |
| 2026-07-11 | NMA491 | - | Jul 11, 21:40 UTC | Jul 11, 21:50 UTC | 10m |
| 2026-07-10 | NMA490 | - | Jul 10, 23:50 UTC | Jul 11, 17:40 UTC | 17h 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-NMH page for operator, model, and routing details .