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
- 182
- Distinct callsigns
- 20
- Country
- EG
- Last broadcast
- 3h ago
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 | Nesma Airlines | 20 | 2026-05-17 |
| NMA616 | Nesma Airlines | 16 | 2026-05-27 |
| NMA602 | Nesma Airlines | 15 | 2026-05-13 |
| NMA611 | Nesma Airlines | 11 | 2026-05-18 |
| NMA603 | Nesma Airlines | 10 | 2026-05-12 |
| NMA600 | Nesma Airlines | 8 | 2026-05-19 |
| NMA607 | Nesma Airlines | 7 | 2026-05-20 |
| NMA430 | Nesma Airlines | 7 | 2026-05-16 |
| NMA604 | Nesma Airlines | 6 | 2026-05-09 |
| NMA622 | Nesma Airlines | 5 | 2026-05-21 |
| NMA606 | Nesma Airlines | 5 | 2026-05-04 |
| NMA605 | Nesma Airlines | 5 | 2026-05-01 |
| NMA441 | Nesma Airlines | 5 | 2026-04-29 |
| NMA650 | Nesma Airlines | 4 | 2026-05-15 |
| NMA660 | Nesma Airlines | 3 | 2026-05-15 |
| NMA643 | Nesma Airlines | 3 | 2026-04-13 |
| NMA620 | Nesma Airlines | 3 | 2026-04-26 |
| NMA6061 | - | 3 | 2026-04-17 |
| NMA4617 | Nesma Airlines | 3 | 2026-05-28 |
| NMA4064 | - | 3 | 2026-04-17 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-30 | NMA160 | CAI → RUH | May 30, 01:15 UTC | May 30, 01:40 UTC | 25m |
| 2026-05-29 | NMA164 | CAI → RUH | May 29, 16:50 UTC | May 29, 22:35 UTC | 5h 45m |
| 2026-05-29 | NMA331 | SAW → CAI | May 29, 12:35 UTC | May 29, 14:05 UTC | 1h 30m |
| 2026-05-29 | NMA330 | CAI → TIF | May 29, 09:25 UTC | May 29, 11:05 UTC | 1h 40m |
| 2026-05-28 | NMA4617 | WRO → HRG | May 28, 18:55 UTC | May 29, 00:30 UTC | 5h 35m |
| 2026-05-28 | NMA4616 | HRG → WRO | May 28, 02:40 UTC | May 28, 17:10 UTC | 14h 30m |
| 2026-05-27 | NMA616 | SSH → VKO | May 27, 23:00 UTC | May 27, 23:10 UTC | 10m |
| 2026-05-27 | NMA616 | SSH → VKO | May 27, 15:15 UTC | May 27, 20:45 UTC | 5h 30m |
| 2026-05-27 | NMA141 | - | May 27, 08:40 UTC | May 27, 13:05 UTC | 4h 25m |
| 2026-05-27 | NMA160 | CAI → RUH | May 27, 00:14 UTC | May 27, 06:15 UTC | 6h 0m |
| 2026-05-26 | NMA151 | DMM → CAI | May 26, 22:09 UTC | May 26, 22:35 UTC | 25m |
| 2026-05-26 | NMA150 | CAI → DMM | May 26, 16:24 UTC | May 26, 16:45 UTC | 20m |
| 2026-05-26 | NMA331 | SAW → CAI | May 26, 09:15 UTC | May 26, 14:05 UTC | 4h 50m |
| 2026-05-26 | NMA153 | DMM → CAI | May 26, 06:25 UTC | May 26, 06:44 UTC | 20m |
| 2026-05-25 | NMA7191 | SKP → HRG | May 25, 04:55 UTC | May 25, 17:15 UTC | 12h 20m |
| 2026-05-25 | NMA7190 | HRG → SKP | May 25, 01:55 UTC | May 25, 03:15 UTC | 1h 20m |
| 2026-05-24 | NMA143 | - | May 24, 15:40 UTC | May 24, 20:40 UTC | 5h 0m |
| 2026-05-24 | NMA123 | TUU → CAI | May 24, 10:50 UTC | May 24, 13:50 UTC | 3h 0m |
| 2026-05-24 | NMA171 | JED → CAI | May 24, 07:25 UTC | May 24, 07:40 UTC | 15m |
| 2026-05-24 | NMA170 | CAI → JED | May 24, 02:40 UTC | May 24, 02:50 UTC | 10m |
| 2026-05-21 | NMA623 | - | May 21, 21:05 UTC | May 22, 16:00 UTC | 18h 54m |
| 2026-05-21 | NMA622 | HRG → VKO | May 21, 19:05 UTC | May 22, 16:00 UTC | 20h 55m |
| 2026-05-21 | NMA622 | HRG → VKO | May 21, 18:55 UTC | May 22, 16:00 UTC | 21h 5m |
| 2026-05-21 | NMA622 | HRG → VKO | May 21, 13:05 UTC | May 22, 08:05 UTC | 19h 0m |
| 2026-05-21 | NMA622 | HRG → VKO | May 21, 11:05 UTC | May 22, 08:05 UTC | 21h 0m |
| 2026-05-21 | NMA622 | HRG → VKO | May 21, 10:50 UTC | May 22, 08:05 UTC | 21h 15m |
| 2026-05-20 | NMA607 | VKO → HRG | May 20, 14:40 UTC | May 21, 09:15 UTC | 18h 35m |
| 2026-05-20 | NMA607 | VKO → HRG | May 20, 07:05 UTC | May 21, 07:00 UTC | 23h 55m |
| 2026-05-20 | NMA601 | VKO → HRG | May 20, 05:05 UTC | May 21, 02:10 UTC | 21h 5m |
| 2026-05-19 | NMA601 | VKO → HRG | May 19, 23:05 UTC | May 20, 23:00 UTC | 23h 56m |
| 2026-05-19 | NMA600 | HRG → VKO | May 19, 21:05 UTC | May 20, 17:35 UTC | 20h 31m |
| 2026-05-19 | NMA600 | HRG → VKO | May 19, 20:45 UTC | May 20, 17:35 UTC | 20h 51m |
| 2026-05-19 | NMA600 | HRG → VKO | May 19, 13:05 UTC | May 20, 08:25 UTC | 19h 21m |
| 2026-05-19 | NMA600 | HRG → VKO | May 19, 11:50 UTC | May 20, 08:25 UTC | 20h 36m |
| 2026-05-18 | NMA421 | PEE → HRG | May 18, 15:55 UTC | May 19, 09:50 UTC | 17h 54m |
| 2026-05-18 | NMA611 | VKO → HRG | May 18, 05:05 UTC | May 19, 03:40 UTC | 22h 34m |
| 2026-05-18 | NMA611 | VKO → HRG | May 18, 03:30 UTC | May 19, 03:00 UTC | 23h 29m |
| 2026-05-17 | NMA611 | VKO → HRG | May 17, 17:05 UTC | May 18, 16:30 UTC | 23h 25m |
| 2026-05-17 | NMA610 | HRG → VKO | May 17, 14:05 UTC | May 18, 06:45 UTC | 16h 40m |
| 2026-05-17 | NMA610 | HRG → VKO | May 17, 07:05 UTC | May 18, 06:45 UTC | 23h 40m |
| 2026-05-17 | NMA610 | HRG → VKO | May 17, 05:05 UTC | May 18, 05:00 UTC | 23h 55m |
| 2026-05-17 | NMA610 | HRG → VKO | May 17, 03:45 UTC | May 17, 18:35 UTC | 14h 50m |
| 2026-05-16 | NMA430 | HRG → SVX | May 16, 03:50 UTC | May 16, 22:30 UTC | 18h 40m |
| 2026-05-16 | NMA430 | HRG → SVX | May 16, 01:35 UTC | May 16, 22:30 UTC | 20h 55m |
| 2026-05-15 | NMA430 | HRG → SVX | May 15, 23:35 UTC | May 16, 22:30 UTC | 22h 55m |
| 2026-05-15 | NMA650 | HRG → KZN | May 15, 16:30 UTC | May 16, 11:01 UTC | 18h 31m |
| 2026-05-15 | NMA650 | HRG → KZN | May 15, 09:05 UTC | May 16, 09:01 UTC | 23h 55m |
| 2026-05-15 | NMA660 | HRG → GSV | May 15, 07:15 UTC | May 16, 06:50 UTC | 23h 35m |
| 2026-05-14 | NMA660 | HRG → GSV | May 14, 21:05 UTC | May 15, 17:05 UTC | 19h 59m |
| 2026-05-14 | NMA4617 | WRO → HRG | May 14, 19:05 UTC | May 15, 17:05 UTC | 21h 59m |
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 .