sensors Mode-S transponder
01025A
ICAO 24-bit transponder address · allocated to Egypt
Currently assigned to SU-NMR · AIRBUS A-320
- Hex
- 01025A
- Octal
- 00201132
- Decimal
- 66,138
- Country
- EG
- Tail
- SU-NMR
- Type
- A320
- Flights observed
- 241
- Distinct callsigns
- 20
- Country
- EG
- Last broadcast
- Jul 26, 22:30 UTC
Current position
Country allocation
The ICAO 24-bit address 01025A 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 | - | 18 | 2026-07-12 |
| NMA617 | - | 13 | 2026-06-27 |
| NMA611 | - | 13 | 2026-07-15 |
| NMA603 | Nesma Airlines | 13 | 2026-07-17 |
| NMA600 | - | 12 | 2026-06-25 |
| NMA602 | Nesma Airlines | 10 | 2026-06-10 |
| NMA621 | Nesma Airlines | 9 | 2026-06-28 |
| NMA615 | - | 9 | 2026-07-17 |
| NMA607 | - | 8 | 2026-06-20 |
| NMA690 | Nesma Airlines | 7 | 2026-06-05 |
| NMA679 | Nesma Airlines | 7 | 2026-07-21 |
| NMA610 | - | 7 | 2026-07-14 |
| NMA650 | - | 6 | 2026-06-26 |
| NMA647 | Nesma Airlines | 6 | 2026-07-24 |
| NMA638 | - | 6 | 2026-07-07 |
| NMA604 | Nesma Airlines | 6 | 2026-04-18 |
| NMA670 | - | 5 | 2026-07-09 |
| NMA614 | - | 5 | 2026-07-06 |
| NMA651 | Nesma Airlines | 4 | 2026-06-03 |
| NMA646 | - | 4 | 2026-07-26 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | NMA646 | - | Jul 26, 08:50 UTC | Jul 26, 22:30 UTC | 13h 40m |
| 2026-07-26 | NMA688 | SSH → AER | Jul 26, 02:45 UTC | Jul 26, 04:25 UTC | 1h 40m |
| 2026-07-25 | NMA649 | VKO → SSH | Jul 25, 07:10 UTC | Jul 25, 23:50 UTC | 16h 40m |
| 2026-07-25 | NMA649 | VKO → SSH | Jul 25, 02:35 UTC | Jul 25, 23:50 UTC | 21h 15m |
| 2026-07-25 | NMA649 | VKO → SSH | Jul 25, 02:25 UTC | Jul 25, 23:50 UTC | 21h 25m |
| 2026-07-24 | NMA647 | VKO → SSH | Jul 24, 13:10 UTC | Jul 25, 00:05 UTC | 10h 55m |
| 2026-07-23 | NMA646 | - | Jul 23, 20:35 UTC | Jul 24, 15:15 UTC | 18h 40m |
| 2026-07-23 | NMA646 | - | Jul 23, 19:15 UTC | Jul 24, 15:15 UTC | 20h 0m |
| 2026-07-23 | NMA659 | - | Jul 23, 17:15 UTC | Jul 24, 15:15 UTC | 22h 0m |
| 2026-07-23 | NMA647 | VKO → SSH | Jul 23, 03:40 UTC | Jul 23, 21:25 UTC | 17h 45m |
| 2026-07-22 | NMA647 | VKO → SSH | Jul 22, 20:50 UTC | Jul 23, 20:30 UTC | 23h 40m |
| 2026-07-22 | NMA647 | VKO → SSH | Jul 22, 19:20 UTC | Jul 23, 17:20 UTC | 22h 0m |
| 2026-07-22 | NMA647 | VKO → SSH | Jul 22, 13:00 UTC | Jul 23, 11:15 UTC | 22h 15m |
| 2026-07-22 | NMA647 | VKO → SSH | Jul 22, 12:20 UTC | Jul 23, 09:55 UTC | 21h 35m |
| 2026-07-22 | NMA646 | - | Jul 22, 03:05 UTC | Jul 22, 21:25 UTC | 18h 20m |
| 2026-07-21 | NMA689 | AER → SSH | Jul 21, 18:40 UTC | Jul 22, 13:50 UTC | 19h 10m |
| 2026-07-21 | NMA438 | SSH → SVX | Jul 21, 17:00 UTC | Jul 22, 13:50 UTC | 20h 50m |
| 2026-07-21 | NMA679 | MRV → SSH | Jul 21, 08:35 UTC | Jul 22, 04:00 UTC | 19h 25m |
| 2026-07-21 | NMA679 | MRV → SSH | Jul 21, 06:55 UTC | Jul 22, 04:00 UTC | 21h 5m |
| 2026-07-21 | NMA679 | MRV → SSH | Jul 21, 04:35 UTC | Jul 22, 04:00 UTC | 23h 25m |
| 2026-07-21 | NMA679 | MRV → SSH | Jul 21, 02:35 UTC | Jul 21, 19:05 UTC | 16h 30m |
| 2026-07-20 | NMA679 | MRV → SSH | Jul 20, 14:35 UTC | Jul 21, 09:35 UTC | 19h 0m |
| 2026-07-20 | NMA679 | MRV → SSH | Jul 20, 12:35 UTC | Jul 21, 09:35 UTC | 21h 0m |
| 2026-07-20 | NMA679 | MRV → SSH | Jul 20, 12:25 UTC | Jul 21, 09:35 UTC | 21h 10m |
| 2026-07-19 | NMA643 | VKO → SSH | Jul 19, 22:05 UTC | Jul 20, 10:05 UTC | 12h 0m |
| 2026-07-19 | NMA618 | SSH → VKO | Jul 19, 08:35 UTC | Jul 20, 08:30 UTC | 23h 55m |
| 2026-07-19 | NMA618 | SSH → VKO | Jul 19, 06:35 UTC | Jul 20, 06:30 UTC | 23h 55m |
| 2026-07-19 | NMA605 | VKO → HRG | Jul 19, 00:35 UTC | Jul 20, 00:30 UTC | 23h 55m |
| 2026-07-18 | NMA605 | VKO → HRG | Jul 18, 22:35 UTC | Jul 19, 22:30 UTC | 23h 55m |
| 2026-07-18 | NIA8602 | - | Jul 18, 15:10 UTC | Jul 19, 09:40 UTC | 18h 30m |
| 2026-07-17 | NIA8601 | - | Jul 17, 22:45 UTC | Jul 18, 13:20 UTC | 14h 36m |
| 2026-07-17 | NIA8601 | - | Jul 17, 16:34 UTC | Jul 18, 13:20 UTC | 20h 46m |
| 2026-07-17 | NIA8601 | - | Jul 17, 14:39 UTC | Jul 18, 13:20 UTC | 22h 41m |
| 2026-07-17 | NMA603 | VKO → HRG | Jul 17, 06:35 UTC | Jul 18, 01:39 UTC | 19h 5m |
| 2026-07-17 | NMA603 | VKO → HRG | Jul 17, 04:35 UTC | Jul 18, 01:39 UTC | 21h 5m |
| 2026-07-17 | NMA615 | - | Jul 17, 02:34 UTC | Jul 18, 01:39 UTC | 23h 5m |
| 2026-07-16 | NMA615 | - | Jul 16, 20:35 UTC | Jul 17, 16:44 UTC | 20h 10m |
| 2026-07-16 | NMA615 | - | Jul 16, 20:19 UTC | Jul 17, 16:44 UTC | 20h 25m |
| 2026-07-16 | NMA642 | - | Jul 16, 19:40 UTC | Jul 16, 20:09 UTC | 30m |
| 2026-07-16 | NMA643 | - | Jul 16, 11:54 UTC | Jul 16, 15:40 UTC | 3h 45m |
| 2026-07-15 | NMA479 | - | Jul 15, 14:00 UTC | Jul 16, 06:45 UTC | 16h 45m |
| 2026-07-15 | NMA479 | - | Jul 15, 04:35 UTC | Jul 16, 04:30 UTC | 23h 55m |
| 2026-07-15 | NMA611 | - | Jul 15, 02:35 UTC | Jul 16, 01:20 UTC | 22h 45m |
| 2026-07-15 | NMA611 | - | Jul 15, 02:05 UTC | Jul 16, 00:30 UTC | 22h 25m |
| 2026-07-14 | NMA610 | - | Jul 14, 23:15 UTC | Jul 14, 23:25 UTC | 10m |
| 2026-07-14 | NMA610 | - | Jul 14, 19:00 UTC | Jul 14, 21:15 UTC | 2h 15m |
| 2026-07-13 | NMA603 | - | Jul 13, 20:55 UTC | Jul 14, 14:50 UTC | 17h 55m |
| 2026-07-13 | NMA611 | - | Jul 13, 04:35 UTC | Jul 13, 23:10 UTC | 18h 35m |
| 2026-07-13 | NMA611 | - | Jul 13, 03:10 UTC | Jul 13, 23:10 UTC | 20h 0m |
| 2026-07-12 | NMA611 | - | Jul 12, 19:05 UTC | Jul 13, 06:20 UTC | 11h 15m |
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-NMR page for operator, model, and routing details .