sensors Mode-S transponder
010236
ICAO 24-bit transponder address · allocated to Egypt
Currently assigned to SU-NMG · AIRBUS A-320
- Hex
- 010236
- Octal
- 00201066
- Decimal
- 66,102
- Country
- EG
- Tail
- SU-NMG
- Type
- A320
- Flights observed
- 92
- Distinct callsigns
- 20
- Country
- EG
- Last broadcast
- 1h ago
Last known position
Country allocation
The ICAO 24-bit address 010236 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 | 7 | 2026-05-25 |
| NMA601 | Nesma Airlines | 6 | 2026-05-27 |
| NMA1321 | Nesma Airlines | 6 | 2026-04-20 |
| NMA8002 | - | 5 | 2026-05-18 |
| NMA123 | Nesma Airlines | 5 | 2026-05-12 |
| NMA1320 | Nesma Airlines | 4 | 2026-04-20 |
| NMA8012 | - | 3 | 2026-05-15 |
| NMA8011 | - | 3 | 2026-05-15 |
| NMA8008 | - | 3 | 2026-05-09 |
| NMA8001 | - | 3 | 2026-05-18 |
| NMA611 | Nesma Airlines | 3 | 2026-05-24 |
| NMA301 | Nesma Airlines | 3 | 2026-05-20 |
| NMA300 | Nesma Airlines | 3 | 2026-05-20 |
| NMA171 | Nesma Airlines | 3 | 2026-05-21 |
| NMA444 | Nesma Airlines | 2 | 2026-05-28 |
| NMA430 | Nesma Airlines | 2 | 2026-05-27 |
| NMA173 | Nesma Airlines | 2 | 2026-05-20 |
| NMA161 | Nesma Airlines | 2 | 2026-04-21 |
| NMA160 | Nesma Airlines | 2 | 2026-05-22 |
| NMA1331 | Nesma Airlines | 2 | 2026-04-27 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | NMA690 | HRG → LED | May 29, 22:35 UTC | May 30, 09:30 UTC | 10h 55m |
| 2026-05-29 | NMA5271 | TSR → HRG | May 29, 11:05 UTC | May 29, 19:10 UTC | 8h 5m |
| 2026-05-28 | NMA5270 | HRG → TSR | May 28, 23:55 UTC | May 29, 09:40 UTC | 9h 45m |
| 2026-05-28 | NMA444 | HRG → KUF | May 28, 03:20 UTC | May 28, 19:25 UTC | 16h 5m |
| 2026-05-27 | NMA444 | HRG → KUF | May 27, 19:50 UTC | May 28, 19:25 UTC | 23h 35m |
| 2026-05-27 | NMA430 | HRG → SVX | May 27, 18:15 UTC | May 28, 17:30 UTC | 23h 15m |
| 2026-05-27 | NMA430 | HRG → SVX | May 27, 09:35 UTC | May 28, 03:45 UTC | 18h 10m |
| 2026-05-27 | NMA601 | VKO → HRG | May 27, 07:35 UTC | May 28, 03:45 UTC | 20h 10m |
| 2026-05-27 | NMA601 | VKO → HRG | May 27, 06:25 UTC | May 28, 03:45 UTC | 21h 20m |
| 2026-05-27 | NMA601 | VKO → HRG | May 27, 01:34 UTC | May 27, 20:25 UTC | 18h 50m |
| 2026-05-26 | NMA601 | VKO → HRG | May 26, 22:50 UTC | May 27, 20:25 UTC | 21h 35m |
| 2026-05-26 | NMA601 | VKO → HRG | May 26, 19:50 UTC | May 27, 18:45 UTC | 22h 56m |
| 2026-05-26 | NMA601 | VKO → HRG | May 26, 18:10 UTC | May 27, 10:35 UTC | 16h 25m |
| 2026-05-25 | NMA605 | VKO → HRG | May 25, 21:24 UTC | May 26, 15:05 UTC | 17h 40m |
| 2026-05-25 | NMA605 | VKO → HRG | May 25, 17:55 UTC | May 26, 15:05 UTC | 21h 10m |
| 2026-05-25 | NMA605 | VKO → HRG | May 25, 16:15 UTC | May 26, 15:05 UTC | 22h 49m |
| 2026-05-25 | NMA661 | GSV → HRG | May 25, 14:20 UTC | May 25, 14:30 UTC | 10m |
| 2026-05-24 | NMA611 | VKO → HRG | May 24, 18:55 UTC | May 25, 11:10 UTC | 16h 15m |
| 2026-05-24 | NMA611 | VKO → HRG | May 24, 09:35 UTC | May 25, 06:35 UTC | 21h 0m |
| 2026-05-24 | NMA611 | VKO → HRG | May 24, 07:35 UTC | May 25, 06:35 UTC | 23h 0m |
| 2026-05-24 | NMA605 | VKO → HRG | May 24, 06:50 UTC | May 25, 05:30 UTC | 22h 40m |
| 2026-05-24 | NMA605 | VKO → HRG | May 24, 00:40 UTC | May 24, 21:15 UTC | 20h 35m |
| 2026-05-23 | NMA605 | VKO → HRG | May 23, 23:00 UTC | May 24, 21:15 UTC | 22h 15m |
| 2026-05-23 | NMA605 | VKO → HRG | May 23, 19:35 UTC | May 24, 19:25 UTC | 23h 50m |
| 2026-05-23 | NMA6598 | MUC → HRG | May 23, 17:05 UTC | May 24, 10:10 UTC | 17h 5m |
| 2026-05-23 | NMA6597 | HRG → MUC | May 23, 04:35 UTC | May 23, 15:55 UTC | 11h 20m |
| 2026-05-22 | NMA602 | HRG → VKO | May 22, 19:10 UTC | May 23, 04:30 UTC | 9h 19m |
| 2026-05-22 | NMA330 | CAI → TIF | May 22, 09:10 UTC | May 22, 13:55 UTC | 4h 45m |
| 2026-05-22 | NMA160 | CAI → RUH | May 22, 00:05 UTC | May 22, 06:10 UTC | 6h 5m |
| 2026-05-21 | NMA171 | JED → CAI | May 21, 07:20 UTC | May 21, 14:35 UTC | 7h 15m |
| 2026-05-20 | NMA301 | CAI → MXP | May 20, 21:05 UTC | May 21, 00:00 UTC | 2h 55m |
| 2026-05-20 | NMA300 | CAI → MXP | May 20, 15:15 UTC | May 20, 18:50 UTC | 3h 35m |
| 2026-05-20 | NMA173 | JED → CAI | May 20, 11:55 UTC | May 20, 12:15 UTC | 20m |
| 2026-05-18 | NMA173 | JED → CAI | May 18, 20:35 UTC | May 19, 14:30 UTC | 17h 55m |
| 2026-05-18 | NMA8002 | - | May 18, 14:40 UTC | May 18, 17:50 UTC | 3h 10m |
| 2026-05-18 | NMA8002 | - | May 18, 12:35 UTC | May 18, 13:25 UTC | 50m |
| 2026-05-18 | NMA8001 | - | May 18, 06:10 UTC | May 18, 10:05 UTC | 3h 55m |
| 2026-05-17 | NMA171 | JED → CAI | May 17, 07:15 UTC | May 17, 07:30 UTC | 15m |
| 2026-05-16 | NMA8002 | - | May 16, 13:55 UTC | May 16, 16:50 UTC | 2h 55m |
| 2026-05-16 | NMA8001 | - | May 16, 07:35 UTC | May 16, 12:16 UTC | 4h 40m |
| 2026-05-15 | NMA152 | CAI → DMM | May 15, 21:20 UTC | May 16, 03:55 UTC | 6h 35m |
| 2026-05-15 | NMA8012 | - | May 15, 13:05 UTC | May 15, 15:55 UTC | 2h 49m |
| 2026-05-15 | NMA8011 | - | May 15, 05:50 UTC | May 15, 11:30 UTC | 5h 40m |
| 2026-05-14 | NMA160 | CAI → RUH | May 14, 00:20 UTC | May 14, 06:15 UTC | 5h 55m |
| 2026-05-12 | NMA123 | TUU → CAI | May 12, 22:35 UTC | May 12, 23:05 UTC | 30m |
| 2026-05-11 | NMA8002 | - | May 11, 13:35 UTC | May 11, 16:05 UTC | 2h 30m |
| 2026-05-11 | NMA8002 | - | May 11, 11:40 UTC | May 11, 12:25 UTC | 45m |
| 2026-05-11 | NMA8001 | - | May 11, 05:15 UTC | May 11, 10:15 UTC | 5h 0m |
| 2026-05-10 | NMA123 | TUU → CAI | May 10, 05:45 UTC | May 10, 13:44 UTC | 8h 0m |
| 2026-05-09 | NMA8008 | - | May 9, 17:35 UTC | May 10, 13:44 UTC | 20h 10m |
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-NMG page for operator, model, and routing details .