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
No current signal · last broadcast 14m ago
Flights observed
281
Distinct callsigns
20
Country
EG
Last broadcast
14m ago

Last known position

Most recent position reported by Mode-S 01023F.

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 - 37 2026-07-12
RSX311 Red Sea Airlines 35 2026-07-13
RSX317 - 17 2026-07-11
RSX321 - 14 2026-06-30
RSX312 - 14 2026-06-19
RSX327 Red Sea Airlines 13 2026-05-14
RSX313 Red Sea Airlines 13 2026-06-20
RSX338 Red Sea Airlines 12 2026-06-11
RSX331 - 12 2026-06-09
RSX341 - 11 2026-06-29
RSX314 Red Sea Airlines 11 2026-06-07
RSX328 Red Sea Airlines 10 2026-05-11
RSX326 - 8 2026-06-27
RSX325 - 8 2026-06-27
RSX315 - 8 2026-07-09
RSX322 - 7 2026-06-30
RSX318 - 6 2026-05-23
RSX371 - 5 2026-07-11
RSX333 - 5 2026-06-19
RSX332 - 5 2026-06-09

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-13 RSX311 SSH → VKO Jul 13, 13:50 UTCJul 14, 01:35 UTC11h 45m
2026-07-12 RSX337 - Jul 12, 23:20 UTCJul 13, 10:35 UTC11h 15m
2026-07-11 RSX371 - Jul 11, 15:20 UTCJul 12, 04:30 UTC13h 10m
2026-07-11 RSX317 - Jul 11, 00:20 UTCJul 11, 12:05 UTC11h 45m
2026-07-10 RSX335 SSH → KRR Jul 10, 19:40 UTCJul 10, 22:20 UTC2h 40m
2026-07-09 RSX315 - Jul 9, 22:40 UTCJul 10, 16:10 UTC17h 30m
2026-07-09 RSX5010 - Jul 9, 16:20 UTCJul 9, 20:50 UTC4h 30m
2026-07-09 RSX5009 - Jul 9, 09:55 UTCJul 9, 14:55 UTC5h 0m
2026-07-09 RSX122 - Jul 9, 05:15 UTCJul 9, 07:20 UTC2h 5m
2026-07-08 RSX121 - Jul 8, 23:50 UTCJul 9, 02:45 UTC2h 55m
2026-07-08 RSX371 - Jul 8, 04:55 UTCJul 8, 23:40 UTC18h 45m
2026-07-08 RSX371 - Jul 8, 02:55 UTCJul 8, 23:40 UTC20h 45m
2026-07-07 RSX371 - Jul 7, 17:55 UTCJul 8, 13:40 UTC19h 45m
2026-07-06 RSX311 SSH → VKO Jul 6, 14:15 UTCJul 7, 01:40 UTC11h 25m
2026-07-05 RSX337 - Jul 5, 22:45 UTCJul 6, 10:45 UTC12h 0m
2026-07-04 RSX371 - Jul 4, 14:55 UTCJul 5, 03:45 UTC12h 50m
2026-07-03 RSX317 - Jul 3, 21:40 UTCJul 4, 09:20 UTC11h 40m
2026-07-03 RSX336 KRR → SSH Jul 3, 16:55 UTCJul 3, 18:45 UTC1h 50m
2026-07-03 RSX335 SSH → KRR Jul 3, 11:25 UTCJul 3, 13:30 UTC2h 5m
2026-07-02 RSX315 - Jul 2, 20:30 UTCJul 3, 08:15 UTC11h 45m
2026-07-02 RSX5010 - Jul 2, 13:50 UTCJul 2, 18:45 UTC4h 55m
2026-07-02 RSX5009 - Jul 2, 07:35 UTCJul 2, 12:30 UTC4h 55m
2026-07-01 RSX337 - Jul 1, 17:25 UTCJul 2, 05:30 UTC12h 5m
2026-06-30 RSX322 - Jun 30, 09:50 UTCJul 1, 05:20 UTC19h 30m
2026-06-30 RSX322 - Jun 30, 07:50 UTCJul 1, 05:20 UTC21h 30m
2026-06-30 RSX322 - Jun 30, 03:50 UTCJul 1, 03:25 UTC23h 35m
2026-06-30 RSX322 - Jun 30, 01:50 UTCJun 30, 20:25 UTC18h 35m
2026-06-30 RSX321 - Jun 30, 00:00 UTCJun 30, 20:25 UTC20h 25m
2026-06-29 RSX321 - Jun 29, 19:49 UTCJun 30, 18:35 UTC22h 46m
2026-06-29 RSX321 - Jun 29, 16:59 UTCJun 30, 11:30 UTC18h 30m
2026-06-29 RSX321 - Jun 29, 13:49 UTCJun 30, 11:30 UTC21h 40m
2026-06-29 RSX321 - Jun 29, 11:50 UTCJun 30, 11:30 UTC23h 40m
2026-06-29 RSX321 - Jun 29, 09:50 UTCJun 30, 09:45 UTC23h 56m
2026-06-29 RSX341 - Jun 29, 09:14 UTCJun 30, 04:35 UTC19h 21m
2026-06-29 RSX341 - Jun 29, 05:50 UTCJun 30, 04:35 UTC22h 46m
2026-06-29 RSX341 - Jun 29, 03:49 UTCJun 30, 03:45 UTC23h 56m
2026-06-29 RSX341 - Jun 29, 01:50 UTCJun 30, 01:45 UTC23h 56m
2026-06-29 RSX341 - Jun 29, 01:29 UTCJun 29, 21:09 UTC19h 40m
2026-06-28 RSX341 - Jun 28, 21:50 UTCJun 29, 21:09 UTC23h 20m
2026-06-28 RSX341 - Jun 28, 19:49 UTCJun 29, 19:44 UTC23h 55m
2026-06-28 RSX323 - Jun 28, 18:25 UTCJun 29, 17:45 UTC23h 20m
2026-06-28 RSX323 - Jun 28, 07:50 UTCJun 29, 05:54 UTC22h 5m
2026-06-28 RSX323 - Jun 28, 05:49 UTCJun 29, 05:45 UTC23h 55m
2026-06-28 RSX323 - Jun 28, 04:25 UTCJun 29, 03:44 UTC23h 20m
2026-06-27 RSX323 - Jun 27, 23:50 UTCJun 28, 23:20 UTC23h 30m
2026-06-27 RSX326 - Jun 27, 21:50 UTCJun 28, 21:45 UTC23h 55m
2026-06-27 RSX325 - Jun 27, 20:44 UTCJun 28, 19:44 UTC23h 0m
2026-06-27 RSX325 - Jun 27, 03:49 UTCJun 28, 00:50 UTC21h 0m
2026-06-27 RSX325 - Jun 27, 01:49 UTCJun 28, 00:50 UTC23h 0m
2026-06-27 RSX322 - Jun 27, 00:44 UTCJun 27, 23:45 UTC23h 0m

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 .

Mode-S 01023F frequently asked

What is Mode-S code 01023F?
01023F is an ICAO 24-bit transponder address. Allocated to Egypt. Assigned to SU-RSB.
Where is Mode-S 01023F registered?
Mode-S code 01023F is allocated to Egypt (EG). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 01023F broadcasting right now?
No active broadcast right now. Last signal was 14m ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 01023F, octal 00201077, decimal 66,111.
What flights does 01023F operate?
Mode-S 01023F has broadcast 20 distinct callsigns, including RSX337, RSX311, RSX317, RSX321, RSX312.