sensors Mode-S transponder
010261
ICAO 24-bit transponder address · allocated to Egypt
Currently assigned to SU-SFY · BOEING 737-800
- Hex
- 010261
- Octal
- 00201141
- Decimal
- 66,145
- Country
- EG
- Tail
- SU-SFY
- Type
- B738
- Flights observed
- 87
- Distinct callsigns
- 20
- Country
- EG
- Last broadcast
- 3d ago
Last known position
Country allocation
The ICAO 24-bit address 010261 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 |
|---|---|---|---|
| RMX2203 | - | 17 | 2026-05-29 |
| RMX7702 | - | 9 | 2026-05-10 |
| RMX7701 | - | 8 | 2026-05-10 |
| RMX2202 | - | 6 | 2026-05-27 |
| RMX2201 | - | 6 | 2026-05-25 |
| RMX2204 | - | 5 | 2026-05-29 |
| RMX7721 | - | 4 | 2026-04-18 |
| RMX9002 | - | 3 | 2026-05-14 |
| RMX7720 | - | 3 | 2026-04-17 |
| RMX7703 | - | 3 | 2026-05-11 |
| RMX9001 | - | 2 | 2026-05-30 |
| RMX8303 | - | 2 | 2026-04-15 |
| RMX8302 | - | 2 | 2026-04-14 |
| RMX8202 | - | 2 | 2026-04-18 |
| RMX8806 | - | 1 | 2026-05-03 |
| RMX8805 | - | 1 | 2026-05-03 |
| RMX8804 | - | 1 | 2026-05-03 |
| RMX8803 | - | 1 | 2026-05-03 |
| RMX8802 | - | 1 | 2026-05-02 |
| RMX8801 | - | 1 | 2026-05-02 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-30 | RMX9001 | - | May 30, 19:50 UTC | May 30, 23:20 UTC | 3h 30m |
| 2026-05-29 | RMX2204 | - | May 29, 04:15 UTC | May 29, 05:10 UTC | 55m |
| 2026-05-29 | RMX2203 | - | May 29, 01:50 UTC | May 29, 02:50 UTC | 1h 0m |
| 2026-05-27 | RMX2202 | - | May 27, 15:35 UTC | May 27, 16:20 UTC | 45m |
| 2026-05-27 | RMX2203 | - | May 27, 03:29 UTC | May 27, 13:30 UTC | 10h 1m |
| 2026-05-26 | RMX2203 | - | May 26, 15:35 UTC | May 27, 13:30 UTC | 21h 56m |
| 2026-05-26 | RMX2203 | - | May 26, 03:40 UTC | May 26, 13:19 UTC | 9h 40m |
| 2026-05-25 | RMX2203 | - | May 25, 15:00 UTC | May 26, 13:19 UTC | 22h 19m |
| 2026-05-25 | RMX2201 | - | May 25, 12:30 UTC | May 26, 07:29 UTC | 18h 59m |
| 2026-05-25 | RMX2201 | - | May 25, 06:20 UTC | May 26, 04:30 UTC | 22h 9m |
| 2026-05-25 | RMX2201 | - | May 25, 06:05 UTC | May 26, 04:15 UTC | 22h 9m |
| 2026-05-24 | RMX2202 | - | May 24, 15:20 UTC | May 25, 04:05 UTC | 12h 45m |
| 2026-05-24 | RMX2203 | - | May 24, 03:40 UTC | May 24, 13:25 UTC | 9h 45m |
| 2026-05-23 | RMX2203 | - | May 23, 15:25 UTC | May 24, 13:25 UTC | 22h 0m |
| 2026-05-23 | RMX2204 | - | May 23, 06:25 UTC | May 24, 06:15 UTC | 23h 50m |
| 2026-05-23 | RMX2202 | - | May 23, 06:10 UTC | May 24, 04:15 UTC | 22h 6m |
| 2026-05-22 | RMX2203 | - | May 22, 12:40 UTC | May 23, 04:40 UTC | 15h 59m |
| 2026-05-22 | RMX2203 | - | May 22, 07:20 UTC | May 23, 04:40 UTC | 21h 19m |
| 2026-05-22 | RMX2203 | - | May 22, 03:15 UTC | May 22, 16:20 UTC | 13h 5m |
| 2026-05-21 | RMX2203 | - | May 21, 09:15 UTC | May 22, 08:00 UTC | 22h 45m |
| 2026-05-21 | RMX2203 | - | May 21, 04:20 UTC | May 22, 04:05 UTC | 23h 45m |
| 2026-05-21 | RMX2201 | - | May 21, 03:50 UTC | May 21, 10:00 UTC | 6h 10m |
| 2026-05-19 | RMX2202 | - | May 19, 16:20 UTC | May 19, 17:15 UTC | 55m |
| 2026-05-19 | RMX2204 | - | May 19, 02:55 UTC | May 19, 13:25 UTC | 10h 30m |
| 2026-05-18 | RMX2203 | - | May 18, 15:40 UTC | May 19, 00:35 UTC | 8h 54m |
| 2026-05-18 | RMX2201 | - | May 18, 03:05 UTC | May 18, 13:00 UTC | 9h 55m |
| 2026-05-17 | RMX2202 | - | May 17, 14:45 UTC | May 18, 00:15 UTC | 9h 30m |
| 2026-05-17 | RMX2204 | - | May 17, 02:55 UTC | May 17, 11:20 UTC | 8h 25m |
| 2026-05-16 | RMX2203 | - | May 16, 23:55 UTC | May 17, 00:40 UTC | 45m |
| 2026-05-16 | RMX2203 | - | May 16, 22:05 UTC | May 16, 22:30 UTC | 25m |
| 2026-05-16 | RMX2202 | - | May 16, 15:01 UTC | May 16, 16:00 UTC | 1h 0m |
| 2026-05-16 | RMX2201 | - | May 16, 10:20 UTC | May 16, 11:11 UTC | 50m |
| 2026-05-16 | RMX2204 | - | May 16, 03:05 UTC | May 16, 04:10 UTC | 1h 5m |
| 2026-05-15 | RMX2203 | - | May 15, 23:30 UTC | May 16, 00:45 UTC | 1h 15m |
| 2026-05-15 | RMX2203 | - | May 15, 03:20 UTC | May 16, 00:45 UTC | 21h 24m |
| 2026-05-14 | RMX9002 | - | May 14, 17:40 UTC | May 14, 18:00 UTC | 20m |
| 2026-05-14 | RMX9002 | - | May 14, 14:30 UTC | May 14, 17:05 UTC | 2h 35m |
| 2026-05-11 | RMX7703 | - | May 11, 01:30 UTC | May 11, 06:30 UTC | 5h 0m |
| 2026-05-10 | RMX7702 | - | May 10, 19:40 UTC | May 10, 23:05 UTC | 3h 25m |
| 2026-05-10 | RMX7701 | - | May 10, 10:40 UTC | May 10, 13:19 UTC | 2h 40m |
| 2026-05-08 | RMX5321 | - | May 8, 08:14 UTC | May 8, 09:44 UTC | 1h 30m |
| 2026-05-07 | RMX7724 | - | May 7, 15:45 UTC | May 7, 17:20 UTC | 1h 35m |
| 2026-05-07 | RMX7702 | - | May 7, 08:25 UTC | May 7, 13:20 UTC | 4h 55m |
| 2026-05-06 | RMX5902 | - | May 6, 09:35 UTC | May 6, 10:05 UTC | 30m |
| 2026-05-04 | RMX7703 | - | May 4, 16:45 UTC | May 4, 21:25 UTC | 4h 41m |
| 2026-05-04 | RMX7702 | - | May 4, 10:45 UTC | May 4, 14:20 UTC | 3h 35m |
| 2026-05-04 | RMX7701 | - | May 4, 05:25 UTC | May 4, 08:50 UTC | 3h 25m |
| 2026-05-03 | RMX8806 | - | May 3, 17:40 UTC | May 3, 19:05 UTC | 1h 25m |
| 2026-05-03 | RMX8805 | - | May 3, 14:25 UTC | May 3, 15:35 UTC | 1h 10m |
| 2026-05-03 | RMX8804 | - | May 3, 10:05 UTC | May 3, 11:35 UTC | 1h 30m |
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-SFY page for operator, model, and routing details .