sensors Mode-S transponder
01023F
ICAO 24-bit transponder address · allocated to Egypt
Currently assigned to SU-RSB · BOEING 737-800
- Hex
- 01023F
- Octal
- 00201077
- Decimal
- 66,111
- Country
- EG
- Tail
- SU-RSB
- Type
- B738
- Flights observed
- 155
- Distinct callsigns
- 20
- Country
- EG
- Last broadcast
- 1h ago
Current position
Country allocation
The ICAO 24-bit address 01023F 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 |
|---|---|---|---|
| RSX337 | Red Sea Airlines | 22 | 2026-05-27 |
| RSX311 | Red Sea Airlines | 19 | 2026-05-25 |
| RSX317 | - | 14 | 2026-05-22 |
| RSX327 | Red Sea Airlines | 13 | 2026-05-14 |
| RSX331 | - | 10 | 2026-05-19 |
| RSX328 | Red Sea Airlines | 10 | 2026-05-11 |
| RSX312 | Red Sea Airlines | 10 | 2026-05-18 |
| RSX338 | Red Sea Airlines | 9 | 2026-05-27 |
| RSX314 | Red Sea Airlines | 9 | 2026-05-24 |
| RSX318 | - | 6 | 2026-05-23 |
| RSX313 | Red Sea Airlines | 6 | 2026-05-17 |
| RSX325 | - | 5 | 2026-05-28 |
| RSX315 | Red Sea Airlines | 4 | 2026-04-25 |
| RSX332 | - | 3 | 2026-04-22 |
| RSX326 | - | 3 | 2026-05-22 |
| RSX316 | Red Sea Airlines | 3 | 2026-04-25 |
| RSX336 | Red Sea Airlines | 2 | 2026-05-29 |
| RSX335 | Red Sea Airlines | 2 | 2026-05-15 |
| RSX121 | - | 2 | 2026-05-13 |
| RSX6008 | - | 1 | 2026-04-12 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | RSX336 | KRR → SSH | May 29, 17:20 UTC | May 29, 21:45 UTC | 4h 25m |
| 2026-05-28 | RSX325 | - | May 28, 18:50 UTC | May 29, 13:25 UTC | 18h 35m |
| 2026-05-28 | RSX325 | - | May 28, 03:50 UTC | May 29, 03:45 UTC | 23h 55m |
| 2026-05-28 | RSX325 | - | May 28, 01:50 UTC | May 28, 23:20 UTC | 21h 30m |
| 2026-05-28 | RSX325 | - | May 28, 01:35 UTC | May 28, 23:20 UTC | 21h 45m |
| 2026-05-27 | RSX338 | VKO → SSH | May 27, 19:50 UTC | May 28, 19:45 UTC | 23h 55m |
| 2026-05-27 | RSX337 | SSH → VKO | May 27, 17:20 UTC | May 28, 04:50 UTC | 11h 30m |
| 2026-05-25 | RSX311 | SSH → VKO | May 25, 14:20 UTC | May 26, 01:34 UTC | 11h 15m |
| 2026-05-24 | RSX338 | VKO → SSH | May 24, 23:20 UTC | May 25, 11:20 UTC | 12h 0m |
| 2026-05-24 | RSX337 | SSH → VKO | May 24, 07:50 UTC | May 25, 03:50 UTC | 20h 0m |
| 2026-05-24 | RSX314 | VKO → SSH | May 24, 05:50 UTC | May 25, 03:50 UTC | 22h 0m |
| 2026-05-24 | RSX314 | VKO → SSH | May 24, 05:40 UTC | May 25, 03:45 UTC | 22h 5m |
| 2026-05-23 | RSX314 | VKO → SSH | May 23, 21:25 UTC | May 24, 08:50 UTC | 11h 25m |
| 2026-05-23 | RSX314 | VKO → SSH | May 23, 07:50 UTC | May 24, 07:45 UTC | 23h 55m |
| 2026-05-23 | RSX318 | - | May 23, 07:30 UTC | May 24, 05:45 UTC | 22h 16m |
| 2026-05-22 | RSX318 | - | May 22, 23:50 UTC | May 23, 23:30 UTC | 23h 40m |
| 2026-05-22 | RSX317 | - | May 22, 21:50 UTC | May 23, 21:45 UTC | 23h 55m |
| 2026-05-22 | RSX317 | - | May 22, 21:25 UTC | May 23, 09:15 UTC | 11h 49m |
| 2026-05-22 | RSX326 | - | May 22, 04:10 UTC | May 22, 18:40 UTC | 14h 30m |
| 2026-05-21 | RSX326 | - | May 21, 21:50 UTC | May 22, 18:40 UTC | 20h 50m |
| 2026-05-21 | RSX326 | - | May 21, 19:50 UTC | May 22, 18:40 UTC | 22h 50m |
| 2026-05-21 | RSX325 | - | May 21, 18:45 UTC | May 22, 17:45 UTC | 23h 0m |
| 2026-05-19 | RSX331 | - | May 19, 18:00 UTC | May 20, 05:40 UTC | 11h 41m |
| 2026-05-19 | RSX331 | - | May 19, 01:50 UTC | May 19, 21:20 UTC | 19h 30m |
| 2026-05-18 | RSX312 | VKO → SSH | May 18, 23:50 UTC | May 19, 21:20 UTC | 21h 30m |
| 2026-05-18 | RSX312 | VKO → SSH | May 18, 22:20 UTC | May 19, 21:20 UTC | 23h 0m |
| 2026-05-18 | RSX311 | SSH → VKO | May 18, 14:15 UTC | May 19, 01:55 UTC | 11h 39m |
| 2026-05-18 | RSX311 | SSH → VKO | May 18, 01:50 UTC | May 19, 01:45 UTC | 23h 54m |
| 2026-05-17 | RSX311 | SSH → VKO | May 17, 23:50 UTC | May 18, 23:45 UTC | 23h 54m |
| 2026-05-17 | RSX337 | SSH → VKO | May 17, 22:55 UTC | May 18, 18:30 UTC | 19h 34m |
| 2026-05-17 | RSX337 | SSH → VKO | May 17, 09:20 UTC | May 18, 03:15 UTC | 17h 55m |
| 2026-05-17 | RSX337 | SSH → VKO | May 17, 03:50 UTC | May 18, 03:15 UTC | 23h 25m |
| 2026-05-17 | RSX314 | VKO → SSH | May 17, 01:50 UTC | May 18, 01:45 UTC | 23h 55m |
| 2026-05-17 | RSX313 | SSH → VKO | May 17, 00:40 UTC | May 17, 23:45 UTC | 23h 5m |
| 2026-05-16 | RSX313 | SSH → VKO | May 16, 09:51 UTC | May 17, 09:45 UTC | 23h 55m |
| 2026-05-16 | RSX318 | - | May 16, 07:51 UTC | May 17, 05:10 UTC | 21h 20m |
| 2026-05-15 | RSX317 | - | May 15, 17:55 UTC | May 16, 06:16 UTC | 12h 21m |
| 2026-05-15 | RSX335 | SSH → KRR | May 15, 12:00 UTC | May 15, 14:15 UTC | 2h 15m |
| 2026-05-14 | RSX327 | SSH → LED | May 14, 17:05 UTC | May 15, 04:50 UTC | 11h 45m |
| 2026-05-14 | RSX327 | SSH → LED | May 14, 05:50 UTC | May 15, 04:50 UTC | 23h 0m |
| 2026-05-14 | RSX327 | SSH → LED | May 14, 04:00 UTC | May 15, 03:45 UTC | 23h 45m |
| 2026-05-14 | RSX327 | SSH → LED | May 14, 00:10 UTC | May 14, 21:50 UTC | 21h 40m |
| 2026-05-13 | RSX121 | - | May 13, 05:00 UTC | May 14, 00:45 UTC | 19h 45m |
| 2026-05-13 | RSX121 | - | May 13, 02:10 UTC | May 14, 00:45 UTC | 22h 35m |
| 2026-05-12 | RSX331 | - | May 12, 17:50 UTC | May 12, 21:01 UTC | 3h 10m |
| 2026-05-11 | RSX331 | - | May 11, 20:55 UTC | May 12, 19:45 UTC | 22h 50m |
| 2026-05-11 | RSX328 | LED → SSH | May 11, 05:05 UTC | May 11, 21:25 UTC | 16h 21m |
| 2026-05-10 | RSX328 | LED → SSH | May 10, 23:50 UTC | May 11, 21:25 UTC | 21h 36m |
| 2026-05-10 | RSX327 | SSH → LED | May 10, 22:05 UTC | May 11, 21:25 UTC | 23h 21m |
| 2026-05-10 | RSX327 | SSH → LED | May 10, 20:25 UTC | May 11, 13:10 UTC | 16h 45m |
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-RSB page for operator, model, and routing details .