sensors Mode-S transponder
010237
ICAO 24-bit transponder address · allocated to Egypt
Currently assigned to SU-NML · AIRBUS A-320
- Hex
- 010237
- Octal
- 00201067
- Decimal
- 66,103
- Country
- EG
- Tail
- SU-NML
- Type
- A320
- Flights observed
- 255
- Distinct callsigns
- 20
- Country
- EG
- Last broadcast
- 4h ago
Last known position
Country allocation
The ICAO 24-bit address 010237 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 |
|---|---|---|---|
| NMA603 | - | 16 | 2026-07-08 |
| NMA606 | Nesma Airlines | 15 | 2026-06-24 |
| NMA601 | - | 13 | 2026-06-22 |
| NMA616 | Nesma Airlines | 12 | 2026-07-01 |
| NMA600 | - | 12 | 2026-06-30 |
| NMA604 | - | 11 | 2026-07-03 |
| NMA607 | - | 10 | 2026-06-24 |
| NMA690 | Nesma Airlines | 7 | 2026-05-26 |
| NMA642 | - | 7 | 2026-07-06 |
| NMA631 | Nesma Airlines | 7 | 2026-06-03 |
| NMA618 | - | 7 | 2026-07-05 |
| NMA444 | - | 7 | 2026-07-02 |
| NMA611 | - | 6 | 2026-06-28 |
| NMA609 | - | 6 | 2026-07-03 |
| NMA621 | Nesma Airlines | 5 | 2026-06-06 |
| NMA605 | - | 5 | 2026-07-05 |
| NMA617 | - | 4 | 2026-06-18 |
| NMA5002 | Nesma Airlines | 4 | 2026-04-24 |
| NMA5001 | Nesma Airlines | 4 | 2026-04-24 |
| NMA2273 | Nesma Airlines | 4 | 2026-07-07 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | NMA658 | - | Jul 13, 12:50 UTC | Jul 13, 23:35 UTC | 10h 45m |
| 2026-07-13 | NMA1471 | - | Jul 13, 08:55 UTC | Jul 13, 10:05 UTC | 1h 10m |
| 2026-07-13 | NMA1470 | - | Jul 13, 04:30 UTC | Jul 13, 06:20 UTC | 1h 50m |
| 2026-07-12 | NMA647 | - | Jul 12, 13:01 UTC | Jul 13, 00:25 UTC | 11h 25m |
| 2026-07-11 | NMA646 | SSH → VKO | Jul 11, 13:50 UTC | Jul 12, 13:45 UTC | 23h 55m |
| 2026-07-10 | NMA614 | - | Jul 10, 22:00 UTC | Jul 11, 14:15 UTC | 16h 15m |
| 2026-07-10 | NMA5271 | TSR → HRG | Jul 10, 10:20 UTC | Jul 11, 00:20 UTC | 14h 0m |
| 2026-07-10 | NMA5270 | - | Jul 10, 01:10 UTC | Jul 10, 08:55 UTC | 7h 45m |
| 2026-07-09 | NMA4190 | HRG → SKP | Jul 9, 04:20 UTC | Jul 9, 23:45 UTC | 19h 25m |
| 2026-07-08 | NMA603 | - | Jul 8, 21:50 UTC | Jul 9, 21:45 UTC | 23h 55m |
| 2026-07-08 | NMA3271 | BAY → HRG | Jul 8, 09:50 UTC | Jul 9, 06:20 UTC | 20h 30m |
| 2026-07-08 | NMA3271 | BAY → HRG | Jul 8, 09:30 UTC | Jul 9, 06:20 UTC | 20h 50m |
| 2026-07-08 | NMA3270 | - | Jul 8, 00:30 UTC | Jul 8, 08:10 UTC | 7h 40m |
| 2026-07-07 | NMA2190 | - | Jul 7, 21:45 UTC | Jul 7, 23:05 UTC | 1h 20m |
| 2026-07-07 | NMA2273 | CRA → HRG | Jul 7, 15:35 UTC | Jul 7, 21:40 UTC | 6h 5m |
| 2026-07-06 | NMA619 | - | Jul 6, 19:50 UTC | Jul 7, 13:50 UTC | 18h 0m |
| 2026-07-06 | NMA642 | - | Jul 6, 18:05 UTC | Jul 7, 13:50 UTC | 19h 45m |
| 2026-07-05 | NMA618 | - | Jul 5, 21:55 UTC | Jul 6, 09:05 UTC | 11h 10m |
| 2026-07-05 | NMA605 | - | Jul 5, 05:50 UTC | Jul 6, 00:05 UTC | 18h 15m |
| 2026-07-05 | NMA605 | - | Jul 5, 03:50 UTC | Jul 6, 00:05 UTC | 20h 15m |
| 2026-07-05 | NMA605 | - | Jul 5, 03:35 UTC | Jul 6, 00:05 UTC | 20h 30m |
| 2026-07-04 | NMA605 | - | Jul 4, 20:50 UTC | Jul 5, 07:45 UTC | 10h 55m |
| 2026-07-04 | NMA605 | - | Jul 4, 06:10 UTC | Jul 5, 05:45 UTC | 23h 35m |
| 2026-07-03 | NMA604 | - | Jul 3, 22:30 UTC | Jul 4, 21:45 UTC | 23h 15m |
| 2026-07-03 | NMA609 | - | Jul 3, 15:30 UTC | Jul 4, 06:35 UTC | 15h 5m |
| 2026-07-03 | NMA609 | - | Jul 3, 09:50 UTC | Jul 4, 06:35 UTC | 20h 45m |
| 2026-07-03 | NMA609 | - | Jul 3, 07:50 UTC | Jul 4, 06:35 UTC | 22h 45m |
| 2026-07-03 | NMA608 | - | Jul 3, 06:15 UTC | Jul 3, 23:00 UTC | 16h 45m |
| 2026-07-02 | NMA444 | - | Jul 2, 16:20 UTC | Jul 3, 02:15 UTC | 9h 55m |
| 2026-07-02 | NMA444 | - | Jul 2, 05:50 UTC | Jul 3, 02:15 UTC | 20h 25m |
| 2026-07-02 | NMA444 | - | Jul 2, 03:50 UTC | Jul 3, 02:15 UTC | 22h 25m |
| 2026-07-01 | NMA444 | - | Jul 1, 21:50 UTC | Jul 2, 18:35 UTC | 20h 45m |
| 2026-07-01 | NMA616 | SSH → VKO | Jul 1, 19:50 UTC | Jul 2, 18:35 UTC | 22h 45m |
| 2026-07-01 | NMA616 | SSH → VKO | Jul 1, 18:35 UTC | Jul 2, 17:20 UTC | 22h 45m |
| 2026-07-01 | NMA616 | SSH → VKO | Jul 1, 07:50 UTC | Jul 2, 05:55 UTC | 22h 5m |
| 2026-07-01 | NMA616 | SSH → VKO | Jul 1, 06:55 UTC | Jul 2, 05:45 UTC | 22h 50m |
| 2026-07-01 | NMA616 | SSH → VKO | Jul 1, 01:50 UTC | Jul 1, 22:40 UTC | 20h 50m |
| 2026-06-30 | NMA616 | SSH → VKO | Jun 30, 23:50 UTC | Jul 1, 22:40 UTC | 22h 50m |
| 2026-06-30 | NMA600 | - | Jun 30, 22:20 UTC | Jul 1, 19:45 UTC | 21h 25m |
| 2026-06-30 | NMA674 | HRG → MRV | Jun 30, 08:15 UTC | Jun 30, 19:55 UTC | 11h 40m |
| 2026-06-29 | NMA674 | HRG → MRV | Jun 29, 21:50 UTC | Jun 30, 19:55 UTC | 22h 6m |
| 2026-06-29 | NMA604 | - | Jun 29, 19:49 UTC | Jun 30, 19:45 UTC | 23h 56m |
| 2026-06-29 | NMA604 | - | Jun 29, 19:24 UTC | Jun 30, 15:20 UTC | 19h 56m |
| 2026-06-29 | NMA604 | - | Jun 29, 03:49 UTC | Jun 29, 23:29 UTC | 19h 40m |
| 2026-06-29 | NMA604 | - | Jun 29, 02:50 UTC | Jun 29, 23:29 UTC | 20h 40m |
| 2026-06-28 | NMA611 | - | Jun 28, 20:34 UTC | Jun 29, 19:44 UTC | 23h 10m |
| 2026-06-28 | NMA611 | - | Jun 28, 13:00 UTC | Jun 29, 06:05 UTC | 17h 5m |
| 2026-06-27 | NMA7310 | - | Jun 27, 19:24 UTC | Jun 28, 11:35 UTC | 16h 10m |
| 2026-06-27 | NMA603 | - | Jun 27, 01:49 UTC | Jun 27, 21:40 UTC | 19h 50m |
| 2026-06-26 | NMA603 | - | Jun 26, 10:44 UTC | Jun 27, 06:05 UTC | 19h 20m |
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-NML page for operator, model, and routing details .