sensors Mode-S transponder
010284
ICAO 24-bit transponder address · allocated to Egypt
Currently assigned to SU-NMK
- Hex
- 010284
- Octal
- 00201204
- Decimal
- 66,180
- Country
- EG
- Tail
- SU-NMK
- Type
- A320
- Flights observed
- 357
- Distinct callsigns
- 20
- Country
- EG
- Last broadcast
- Jul 26, 20:30 UTC
Last known position
Country allocation
The ICAO 24-bit address 010284 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 |
|---|---|---|---|
| NMA610 | - | 29 | 2026-07-05 |
| NMA690 | Nesma Airlines | 21 | 2026-07-25 |
| NMA602 | Nesma Airlines | 20 | 2026-07-23 |
| NMA611 | - | 19 | 2026-06-22 |
| NMA600 | Nesma Airlines | 18 | 2026-07-22 |
| NMA616 | Nesma Airlines | 17 | 2026-07-10 |
| NMA430 | Nesma Airlines | 17 | 2026-07-25 |
| NMA604 | - | 15 | 2026-06-25 |
| NMA431 | Nesma Airlines | 14 | 2026-07-22 |
| NMA691 | Nesma Airlines | 13 | 2026-07-25 |
| NMA603 | Nesma Airlines | 11 | 2026-07-24 |
| NMA618 | - | 10 | 2026-06-28 |
| NMA605 | - | 10 | 2026-06-25 |
| NMA607 | Nesma Airlines | 7 | 2026-05-20 |
| NMA601 | - | 7 | 2026-06-17 |
| NMA650 | - | 6 | 2026-07-07 |
| NMA619 | - | 6 | 2026-07-10 |
| NMA606 | - | 6 | 2026-06-26 |
| NMA622 | Nesma Airlines | 5 | 2026-05-21 |
| NMA617 | - | 5 | 2026-07-11 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-25 | NMA430 | HRG → SVX | Jul 25, 23:05 UTC | Jul 26, 20:30 UTC | 21h 26m |
| 2026-07-25 | NMA430 | HRG → SVX | Jul 25, 19:05 UTC | Jul 26, 19:00 UTC | 23h 56m |
| 2026-07-25 | NMA691 | LED → HRG | Jul 25, 16:45 UTC | Jul 26, 10:10 UTC | 17h 26m |
| 2026-07-25 | NMA691 | LED → HRG | Jul 25, 13:05 UTC | Jul 26, 10:10 UTC | 21h 6m |
| 2026-07-25 | NMA691 | LED → HRG | Jul 25, 11:05 UTC | Jul 26, 10:10 UTC | 23h 6m |
| 2026-07-25 | NMA690 | HRG → LED | Jul 25, 09:05 UTC | Jul 26, 08:10 UTC | 23h 6m |
| 2026-07-24 | NMA603 | VKO → HRG | Jul 24, 14:45 UTC | Jul 25, 01:35 UTC | 10h 50m |
| 2026-07-23 | NMA602 | HRG → VKO | Jul 23, 17:50 UTC | Jul 24, 17:00 UTC | 23h 10m |
| 2026-07-22 | NMA431 | SVX → HRG | Jul 22, 23:05 UTC | Jul 23, 17:05 UTC | 18h 0m |
| 2026-07-22 | NMA431 | SVX → HRG | Jul 22, 21:25 UTC | Jul 23, 17:05 UTC | 19h 40m |
| 2026-07-22 | NMA600 | HRG → VKO | Jul 22, 01:05 UTC | Jul 22, 23:35 UTC | 22h 30m |
| 2026-07-21 | NMA600 | HRG → VKO | Jul 21, 23:05 UTC | Jul 22, 22:15 UTC | 23h 10m |
| 2026-07-21 | NMA600 | HRG → VKO | Jul 21, 13:10 UTC | Jul 22, 02:35 UTC | 13h 25m |
| 2026-07-20 | NMA674 | HRG → MRV | Jul 20, 19:05 UTC | Jul 21, 19:00 UTC | 23h 54m |
| 2026-07-20 | NMA420 | - | Jul 20, 17:25 UTC | Jul 21, 14:15 UTC | 20h 49m |
| 2026-07-19 | NMA420 | - | Jul 19, 23:05 UTC | Jul 20, 19:45 UTC | 20h 40m |
| 2026-07-19 | NMA420 | - | Jul 19, 22:05 UTC | Jul 20, 19:45 UTC | 21h 40m |
| 2026-07-19 | NMA431 | - | Jul 19, 08:05 UTC | Jul 20, 00:05 UTC | 16h 0m |
| 2026-07-19 | NMA431 | - | Jul 19, 01:05 UTC | Jul 20, 00:05 UTC | 23h 0m |
| 2026-07-18 | NMA431 | - | Jul 18, 23:05 UTC | Jul 19, 22:10 UTC | 23h 5m |
| 2026-07-18 | NMA431 | - | Jul 18, 19:05 UTC | Jul 19, 15:45 UTC | 20h 40m |
| 2026-07-18 | NMA691 | - | Jul 18, 17:05 UTC | Jul 19, 15:45 UTC | 22h 40m |
| 2026-07-18 | NMA691 | - | Jul 18, 15:45 UTC | Jul 19, 14:25 UTC | 22h 40m |
| 2026-07-17 | NMA690 | HRG → LED | Jul 17, 19:30 UTC | Jul 18, 14:25 UTC | 18h 56m |
| 2026-07-17 | NMA492 | HRG → VKO | Jul 17, 01:05 UTC | Jul 17, 21:44 UTC | 20h 40m |
| 2026-07-16 | NMA492 | HRG → VKO | Jul 16, 23:59 UTC | Jul 17, 21:44 UTC | 21h 45m |
| 2026-07-16 | NMA444 | - | Jul 16, 07:50 UTC | Jul 17, 02:05 UTC | 18h 15m |
| 2026-07-16 | NMA431 | - | Jul 16, 06:25 UTC | Jul 16, 06:40 UTC | 15m |
| 2026-07-15 | NMA3270 | - | Jul 15, 06:30 UTC | Jul 15, 23:25 UTC | 16h 55m |
| 2026-07-15 | NMA3270 | - | Jul 15, 03:05 UTC | Jul 15, 23:25 UTC | 20h 20m |
| 2026-07-15 | NMA691 | - | Jul 15, 01:10 UTC | Jul 15, 23:25 UTC | 22h 15m |
| 2026-07-14 | NMA691 | - | Jul 14, 19:05 UTC | Jul 15, 13:30 UTC | 18h 24m |
| 2026-07-14 | NMA690 | - | Jul 14, 17:05 UTC | Jul 15, 13:30 UTC | 20h 24m |
| 2026-07-14 | NMA690 | - | Jul 14, 16:50 UTC | Jul 15, 13:30 UTC | 20h 39m |
| 2026-07-14 | NMA681 | VKO → SSH | Jul 14, 13:05 UTC | Jul 14, 14:10 UTC | 1h 5m |
| 2026-07-14 | NMA680 | - | Jul 14, 08:45 UTC | Jul 14, 09:55 UTC | 1h 10m |
| 2026-07-13 | NMA642 | - | Jul 13, 18:25 UTC | Jul 14, 08:40 UTC | 14h 15m |
| 2026-07-12 | NMA643 | - | Jul 12, 22:15 UTC | Jul 13, 08:45 UTC | 10h 30m |
| 2026-07-12 | NMA476 | - | Jul 12, 05:01 UTC | Jul 12, 22:10 UTC | 17h 10m |
| 2026-07-12 | NMA476 | - | Jul 12, 01:05 UTC | Jul 12, 22:10 UTC | 21h 5m |
| 2026-07-11 | NMA617 | - | Jul 11, 23:05 UTC | Jul 12, 22:10 UTC | 23h 5m |
| 2026-07-11 | NMA617 | - | Jul 11, 21:50 UTC | Jul 12, 13:15 UTC | 15h 25m |
| 2026-07-11 | NMA617 | - | Jul 11, 15:05 UTC | Jul 12, 13:15 UTC | 22h 10m |
| 2026-07-11 | NMA617 | - | Jul 11, 14:40 UTC | Jul 12, 13:01 UTC | 22h 20m |
| 2026-07-11 | NMA617 | - | Jul 11, 01:05 UTC | Jul 12, 01:00 UTC | 23h 55m |
| 2026-07-10 | NMA616 | SSH → VKO | Jul 10, 23:20 UTC | Jul 11, 23:00 UTC | 23h 40m |
| 2026-07-10 | NMA421 | - | Jul 10, 15:40 UTC | Jul 11, 15:00 UTC | 23h 20m |
| 2026-07-10 | NMA619 | - | Jul 10, 07:05 UTC | Jul 11, 01:25 UTC | 18h 20m |
| 2026-07-10 | NMA619 | - | Jul 10, 05:30 UTC | Jul 11, 01:25 UTC | 19h 55m |
| 2026-07-09 | NMA619 | - | Jul 9, 22:20 UTC | Jul 10, 16:15 UTC | 17h 55m |
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-NMK page for operator, model, and routing details .