sensors Mode-S transponder
010256
ICAO 24-bit transponder address · allocated to Egypt
Currently assigned to SU-TCM · AIRBUS A-321
- Hex
- 010256
- Octal
- 00201126
- Decimal
- 66,134
- Country
- EG
- Tail
- SU-TCM
- Type
- A321
- Flights observed
- 92
- Distinct callsigns
- 20
- Country
- EG
- Last broadcast
- 13h ago
Last known position
Country allocation
The ICAO 24-bit address 010256 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 |
|---|---|---|---|
| LMU667 | - | 9 | 2026-04-24 |
| LMU621 | - | 6 | 2026-05-26 |
| LMU662 | - | 5 | 2026-05-14 |
| LMU661 | AlMasria Universal Airlines | 5 | 2026-05-13 |
| LMU637 | - | 5 | 2026-04-25 |
| LMU625 | - | 5 | 2026-05-29 |
| LMU613 | AlMasria Universal Airlines | 5 | 2026-05-04 |
| LMU627 | AlMasria Universal Airlines | 4 | 2026-04-19 |
| LMU626 | - | 4 | 2026-05-27 |
| LMU671 | - | 3 | 2026-05-24 |
| LMU668 | - | 3 | 2026-04-22 |
| LMU651 | - | 3 | 2026-05-28 |
| LMU638 | - | 3 | 2026-04-26 |
| LMU628 | AlMasria Universal Airlines | 3 | 2026-04-20 |
| LMU703 | AlMasria Universal Airlines | 2 | 2026-05-16 |
| LMU695 | - | 2 | 2026-05-22 |
| LMU687 | - | 2 | 2026-04-13 |
| LMU676 | - | 2 | 2026-04-17 |
| LMU675 | - | 2 | 2026-04-16 |
| LMU658 | - | 2 | 2026-05-23 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | LMU625 | - | May 29, 14:30 UTC | May 29, 19:45 UTC | 5h 15m |
| 2026-05-28 | LMU651 | - | May 28, 20:50 UTC | May 28, 22:50 UTC | 2h 0m |
| 2026-05-27 | LMU626 | - | May 27, 07:35 UTC | May 28, 03:10 UTC | 19h 35m |
| 2026-05-27 | LMU626 | - | May 27, 05:35 UTC | May 28, 03:10 UTC | 21h 35m |
| 2026-05-27 | LMU626 | - | May 27, 05:29 UTC | May 28, 03:10 UTC | 21h 40m |
| 2026-05-27 | LMU626 | - | May 27, 01:34 UTC | May 28, 01:00 UTC | 23h 26m |
| 2026-05-26 | LMU625 | - | May 26, 21:34 UTC | May 27, 15:15 UTC | 17h 41m |
| 2026-05-26 | LMU621 | - | May 26, 04:35 UTC | May 26, 16:35 UTC | 12h 0m |
| 2026-05-25 | LMU621 | - | May 25, 13:50 UTC | May 26, 13:29 UTC | 23h 39m |
| 2026-05-25 | LMU621 | - | May 25, 12:15 UTC | May 26, 09:04 UTC | 20h 50m |
| 2026-05-24 | LMU671 | - | May 24, 16:20 UTC | May 25, 14:20 UTC | 22h 0m |
| 2026-05-24 | LMU619 | - | May 24, 14:45 UTC | May 25, 12:35 UTC | 21h 50m |
| 2026-05-23 | LMU658 | - | May 23, 23:50 UTC | May 24, 16:55 UTC | 17h 5m |
| 2026-05-23 | LMU658 | - | May 23, 17:35 UTC | May 24, 16:55 UTC | 23h 20m |
| 2026-05-23 | LMU657 | - | May 23, 15:35 UTC | May 24, 15:05 UTC | 23h 30m |
| 2026-05-23 | LMU657 | - | May 23, 14:40 UTC | May 24, 02:25 UTC | 11h 46m |
| 2026-05-22 | LMU625 | - | May 22, 20:40 UTC | May 23, 08:00 UTC | 11h 19m |
| 2026-05-22 | LMU695 | - | May 22, 00:15 UTC | May 22, 18:05 UTC | 17h 50m |
| 2026-05-19 | LMU697 | - | May 19, 20:55 UTC | May 20, 10:45 UTC | 13h 51m |
| 2026-05-19 | LMU621 | - | May 19, 05:10 UTC | May 19, 23:10 UTC | 18h 0m |
| 2026-05-18 | LMU621 | - | May 18, 16:00 UTC | May 19, 09:35 UTC | 17h 34m |
| 2026-05-18 | LMU621 | - | May 18, 14:20 UTC | May 19, 09:35 UTC | 19h 14m |
| 2026-05-17 | LMU651 | SSH → SSH | May 17, 17:35 UTC | May 18, 17:25 UTC | 23h 50m |
| 2026-05-17 | LMU649 | - | May 17, 15:55 UTC | May 18, 14:40 UTC | 22h 45m |
| 2026-05-17 | LMU704 | - | May 17, 05:55 UTC | May 17, 09:05 UTC | 3h 10m |
| 2026-05-16 | LMU703 | SSH → SSH | May 16, 20:55 UTC | May 17, 02:10 UTC | 5h 15m |
| 2026-05-16 | LMU611 | SSH → SSH | May 16, 05:00 UTC | May 16, 09:40 UTC | 4h 41m |
| 2026-05-15 | LMU671 | - | May 15, 13:40 UTC | May 16, 01:05 UTC | 11h 24m |
| 2026-05-14 | LMU641 | - | May 14, 07:40 UTC | May 15, 02:30 UTC | 18h 50m |
| 2026-05-14 | LMU662 | - | May 14, 05:05 UTC | May 15, 02:30 UTC | 21h 25m |
| 2026-05-13 | LMU661 | SSH → SVX | May 13, 20:45 UTC | May 14, 00:15 UTC | 3h 30m |
| 2026-05-12 | LMU615 | - | May 12, 18:00 UTC | May 13, 08:40 UTC | 14h 40m |
| 2026-05-11 | LMU671 | - | May 11, 06:40 UTC | May 11, 17:50 UTC | 11h 11m |
| 2026-05-10 | LMU662 | - | May 10, 15:15 UTC | May 11, 03:50 UTC | 12h 35m |
| 2026-05-10 | LMU662 | - | May 10, 02:00 UTC | May 10, 05:45 UTC | 3h 45m |
| 2026-05-09 | LMU661 | SSH → SVX | May 9, 17:05 UTC | May 9, 20:44 UTC | 3h 40m |
| 2026-05-09 | LMU652 | - | May 9, 03:20 UTC | May 9, 03:35 UTC | 15m |
| 2026-05-08 | LMU651 | SSH → SSH | May 8, 20:10 UTC | May 8, 22:55 UTC | 2h 45m |
| 2026-05-07 | LMU661 | SSH → SVX | May 7, 16:50 UTC | May 8, 04:44 UTC | 11h 55m |
| 2026-05-07 | LMU649 | - | May 7, 00:45 UTC | May 7, 03:15 UTC | 2h 30m |
| 2026-05-06 | LMU625 | - | May 6, 10:45 UTC | May 6, 22:25 UTC | 11h 39m |
| 2026-05-06 | LMU632 | - | May 6, 05:40 UTC | May 6, 08:05 UTC | 2h 25m |
| 2026-05-04 | LMU613 | SSH → SSH | May 4, 05:35 UTC | May 4, 23:50 UTC | 18h 16m |
| 2026-05-04 | LMU613 | SSH → SSH | May 4, 05:20 UTC | May 4, 23:50 UTC | 18h 31m |
| 2026-05-03 | LMU661 | SSH → SVX | May 3, 13:20 UTC | May 4, 02:04 UTC | 12h 45m |
| 2026-05-02 | LMU703 | SSH → SSH | May 2, 15:25 UTC | May 3, 04:00 UTC | 12h 34m |
| 2026-05-01 | LMU625 | - | May 1, 18:00 UTC | May 2, 03:35 UTC | 9h 35m |
| 2026-05-01 | LMU695 | - | May 1, 01:00 UTC | May 1, 13:35 UTC | 12h 35m |
| 2026-04-30 | LMU616 | SSH → SVO | Apr 30, 22:20 UTC | Apr 30, 22:50 UTC | 30m |
| 2026-04-28 | LMU615 | - | Apr 28, 23:45 UTC | Apr 29, 09:55 UTC | 10h 11m |
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-TCM page for operator, model, and routing details .