sensors Mode-S transponder
010195
ICAO 24-bit transponder address · allocated to Egypt
Currently assigned to SU-TCF · AIRBUS A-320
- Hex
- 010195
- Octal
- 00200625
- Decimal
- 65,941
- Country
- EG
- Tail
- SU-TCF
- Type
- A320
- Flights observed
- 102
- Distinct callsigns
- 9
- Country
- EG
- Last broadcast
- 4h ago
Current position
Country allocation
The ICAO 24-bit address 010195 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 9 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | LMU736 | LED → HRG | May 29, 22:15 UTC | May 30, 02:00 UTC | 3h 45m |
| 2026-05-29 | LMU736 | LED → HRG | May 29, 01:45 UTC | May 30, 01:15 UTC | 23h 30m |
| 2026-05-29 | LMU743 | - | May 29, 00:05 UTC | May 29, 23:15 UTC | 23h 10m |
| 2026-05-27 | LMU755 | - | May 27, 21:10 UTC | May 27, 23:25 UTC | 2h 15m |
| 2026-05-26 | LMU735 | - | May 26, 14:24 UTC | May 26, 19:25 UTC | 5h 0m |
| 2026-05-24 | LMU736 | LED → HRG | May 24, 20:45 UTC | May 25, 14:25 UTC | 17h 40m |
| 2026-05-24 | LMU736 | LED → HRG | May 24, 17:20 UTC | May 25, 14:25 UTC | 21h 5m |
| 2026-05-24 | LMU735 | - | May 24, 15:20 UTC | May 25, 14:25 UTC | 23h 5m |
| 2026-05-24 | LMU735 | - | May 24, 13:20 UTC | May 25, 10:45 UTC | 21h 25m |
| 2026-05-24 | LMU735 | - | May 24, 12:55 UTC | May 25, 10:45 UTC | 21h 50m |
| 2026-05-23 | LMU735 | - | May 23, 23:35 UTC | May 24, 23:15 UTC | 23h 40m |
| 2026-05-23 | LMU735 | - | May 23, 21:50 UTC | May 24, 21:15 UTC | 23h 25m |
| 2026-05-21 | LMU743 | - | May 21, 23:50 UTC | May 22, 02:10 UTC | 2h 20m |
| 2026-05-20 | LMU707 | - | May 20, 03:20 UTC | May 20, 21:35 UTC | 18h 16m |
| 2026-05-20 | LMU707 | - | May 20, 01:20 UTC | May 20, 21:35 UTC | 20h 16m |
| 2026-05-20 | LMU707 | - | May 20, 00:35 UTC | May 20, 21:35 UTC | 21h 1m |
| 2026-05-19 | LMU707 | - | May 19, 17:20 UTC | May 20, 17:15 UTC | 23h 56m |
| 2026-05-19 | LMU707 | - | May 19, 15:20 UTC | May 20, 10:30 UTC | 19h 11m |
| 2026-05-19 | LMU735 | - | May 19, 14:30 UTC | May 20, 10:30 UTC | 20h 1m |
| 2026-05-17 | LMU736 | LED → HRG | May 17, 15:20 UTC | May 18, 10:10 UTC | 18h 50m |
| 2026-05-17 | LMU735 | - | May 17, 13:20 UTC | May 18, 10:10 UTC | 20h 50m |
| 2026-05-17 | LMU735 | - | May 17, 12:55 UTC | May 18, 10:10 UTC | 21h 15m |
| 2026-05-17 | LMU735 | - | May 17, 05:30 UTC | May 18, 00:10 UTC | 18h 40m |
| 2026-05-14 | LMU743 | - | May 14, 07:20 UTC | May 15, 03:15 UTC | 19h 55m |
| 2026-05-13 | LMU707 | - | May 13, 07:20 UTC | May 14, 07:15 UTC | 23h 55m |
| 2026-05-13 | LMU707 | - | May 13, 06:05 UTC | May 13, 07:35 UTC | 1h 30m |
| 2026-05-12 | LMU735 | - | May 12, 14:15 UTC | May 13, 02:40 UTC | 12h 25m |
| 2026-05-11 | LMU735 | - | May 11, 22:00 UTC | May 12, 19:10 UTC | 21h 10m |
| 2026-05-11 | LMU735 | - | May 11, 17:20 UTC | May 12, 17:15 UTC | 23h 55m |
| 2026-05-11 | LMU742 | - | May 11, 15:50 UTC | May 12, 15:15 UTC | 23h 26m |
| 2026-05-10 | LMU741 | - | May 10, 16:04 UTC | May 11, 10:45 UTC | 18h 40m |
| 2026-05-08 | LMU743 | - | May 8, 00:20 UTC | May 8, 03:19 UTC | 3h 0m |
| 2026-05-06 | LMU707 | - | May 6, 05:05 UTC | May 6, 17:35 UTC | 12h 29m |
| 2026-05-05 | LMU736 | LED → HRG | May 5, 05:20 UTC | May 6, 05:15 UTC | 23h 55m |
| 2026-05-05 | LMU743 | - | May 5, 02:50 UTC | May 5, 05:25 UTC | 2h 35m |
| 2026-05-04 | LMU743 | - | May 4, 09:20 UTC | May 5, 05:25 UTC | 20h 6m |
| 2026-05-04 | LMU743 | - | May 4, 07:20 UTC | May 5, 05:25 UTC | 22h 6m |
| 2026-05-02 | LMU707 | - | May 2, 07:50 UTC | May 2, 12:15 UTC | 4h 25m |
| 2026-04-29 | LMU755 | - | Apr 29, 20:55 UTC | Apr 29, 23:25 UTC | 2h 29m |
| 2026-04-27 | LMU741 | - | Apr 27, 07:20 UTC | Apr 28, 01:35 UTC | 18h 15m |
| 2026-04-26 | LMU741 | - | Apr 26, 15:20 UTC | Apr 27, 10:40 UTC | 19h 20m |
| 2026-04-26 | LMU735 | - | Apr 26, 13:20 UTC | Apr 27, 10:40 UTC | 21h 20m |
| 2026-04-26 | LMU735 | - | Apr 26, 12:45 UTC | Apr 27, 10:40 UTC | 21h 55m |
| 2026-04-25 | LMU735 | - | Apr 25, 23:20 UTC | Apr 26, 17:55 UTC | 18h 35m |
| 2026-04-25 | LMU735 | - | Apr 25, 21:20 UTC | Apr 26, 17:55 UTC | 20h 35m |
| 2026-04-25 | LMU735 | - | Apr 25, 17:20 UTC | Apr 26, 17:15 UTC | 23h 55m |
| 2026-04-25 | LMU735 | - | Apr 25, 15:20 UTC | Apr 26, 15:15 UTC | 23h 55m |
| 2026-04-25 | LMU708 | - | Apr 25, 14:15 UTC | Apr 26, 13:15 UTC | 23h 0m |
| 2026-04-25 | LMU707 | - | Apr 25, 05:45 UTC | Apr 25, 23:45 UTC | 18h 0m |
| 2026-04-25 | LMU707 | - | Apr 25, 01:20 UTC | Apr 25, 23:45 UTC | 22h 25m |
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-TCF page for operator, model, and routing details .