sensors Mode-S transponder
02013C
ICAO 24-bit transponder address · allocated to Morocco
Currently assigned to CN-RAM · BOEING 787-9 Dreamliner
- Hex
- 02013C
- Octal
- 00400474
- Decimal
- 131,388
- Country
- MA
- Tail
- CN-RAM
- Type
- B789
- Flights observed
- 189
- Distinct callsigns
- 20
- Country
- MA
- Last broadcast
- 1h ago
Last known position
Country allocation
The ICAO 24-bit address 02013C falls within the block assigned to Morocco (MA) by ICAO Annex 10, Volume III. Every aircraft registered in Morocco 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 |
|---|---|---|---|
| RAM200N | Royal Air Maroc | 28 | 2026-06-28 |
| RAM230 | Royal Air Maroc | 21 | 2026-07-07 |
| RAM231 | - | 19 | 2026-07-07 |
| RAM201N | - | 17 | 2026-06-29 |
| RAM208M | Royal Air Maroc | 13 | 2026-07-05 |
| RAM209M | - | 9 | 2026-07-06 |
| RAM251 | - | 7 | 2026-07-14 |
| RAM250 | - | 6 | 2026-07-14 |
| RAM501B | - | 5 | 2026-07-08 |
| RAM500B | - | 5 | 2026-07-08 |
| RAM204F | Royal Air Maroc | 5 | 2026-06-03 |
| RAM202J | - | 5 | 2026-07-12 |
| RAM218W | Royal Air Maroc | 4 | 2026-06-10 |
| RAM911T | - | 3 | 2026-07-09 |
| RAM910T | - | 3 | 2026-07-09 |
| RAM249 | Royal Air Maroc | 3 | 2026-07-02 |
| RAM219W | Royal Air Maroc | 3 | 2026-06-11 |
| RAM205F | Royal Air Maroc | 3 | 2026-06-04 |
| RAM203J | - | 3 | 2026-07-13 |
| RAM761R | Royal Air Maroc | 2 | 2026-05-08 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | RAM251 | - | Jul 14, 17:40 UTC | Jul 14, 22:55 UTC | 5h 14m |
| 2026-07-14 | RAM250 | - | Jul 14, 03:25 UTC | Jul 14, 14:15 UTC | 10h 50m |
| 2026-07-13 | RAM203J | JFK → CMN | Jul 13, 15:05 UTC | Jul 13, 21:30 UTC | 6h 25m |
| 2026-07-12 | RAM202J | - | Jul 12, 17:05 UTC | Jul 13, 12:20 UTC | 19h 15m |
| 2026-07-11 | RAM202J | - | Jul 11, 21:40 UTC | Jul 12, 14:50 UTC | 17h 10m |
| 2026-07-11 | RAM202J | - | Jul 11, 17:05 UTC | Jul 12, 14:50 UTC | 21h 45m |
| 2026-07-11 | RAM206T | - | Jul 11, 07:55 UTC | Jul 11, 14:45 UTC | 6h 50m |
| 2026-07-10 | RAM251 | - | Jul 10, 17:40 UTC | Jul 11, 03:25 UTC | 9h 45m |
| 2026-07-10 | RAM250 | - | Jul 10, 03:20 UTC | Jul 10, 14:40 UTC | 11h 20m |
| 2026-07-09 | RAM911T | - | Jul 9, 15:55 UTC | Jul 9, 20:20 UTC | 4h 25m |
| 2026-07-09 | RAM910T | - | Jul 9, 09:35 UTC | Jul 9, 13:30 UTC | 3h 55m |
| 2026-07-08 | RAM217 | - | Jul 8, 22:55 UTC | Jul 9, 05:50 UTC | 6h 55m |
| 2026-07-08 | RAM216 | - | Jul 8, 13:30 UTC | Jul 8, 20:35 UTC | 7h 5m |
| 2026-07-08 | RAM500B | - | Jul 8, 03:05 UTC | Jul 8, 03:20 UTC | 15m |
| 2026-07-08 | RAM501B | - | Jul 8, 01:10 UTC | Jul 8, 01:40 UTC | 30m |
| 2026-07-07 | RAM231 | - | Jul 7, 06:15 UTC | Jul 7, 17:55 UTC | 11h 40m |
| 2026-07-07 | RAM230 | CMN → PKX | Jul 7, 02:45 UTC | Jul 7, 03:00 UTC | 15m |
| 2026-07-06 | RAM230 | CMN → PKX | Jul 6, 15:40 UTC | Jul 6, 21:00 UTC | 5h 20m |
| 2026-07-06 | RAM209M | - | Jul 6, 03:15 UTC | Jul 6, 09:15 UTC | 6h 0m |
| 2026-07-05 | RAM208M | CMN → YUL | Jul 5, 22:35 UTC | Jul 5, 23:45 UTC | 1h 10m |
| 2026-07-05 | RAM208M | CMN → YUL | Jul 5, 16:55 UTC | Jul 5, 17:35 UTC | 40m |
| 2026-07-05 | RAM2225 | - | Jul 5, 04:20 UTC | Jul 5, 12:40 UTC | 8h 20m |
| 2026-07-04 | RAM2224 | - | Jul 4, 02:05 UTC | Jul 4, 11:20 UTC | 9h 15m |
| 2026-07-03 | RAM2733 | - | Jul 3, 14:20 UTC | Jul 3, 23:05 UTC | 8h 45m |
| 2026-07-03 | RAM2232 | - | Jul 3, 01:20 UTC | Jul 3, 10:30 UTC | 9h 10m |
| 2026-07-02 | RAM249 | JED → CMN | Jul 2, 02:05 UTC | Jul 2, 18:20 UTC | 16h 15m |
| 2026-07-01 | RAM249 | JED → CMN | Jul 1, 02:05 UTC | Jul 1, 18:05 UTC | 16h 0m |
| 2026-06-30 | RAM231 | - | Jun 30, 09:05 UTC | Jun 30, 18:15 UTC | 9h 10m |
| 2026-06-30 | RAM230 | CMN → PKX | Jun 30, 03:00 UTC | Jun 30, 03:10 UTC | 10m |
| 2026-06-29 | RAM230 | CMN → PKX | Jun 29, 15:45 UTC | Jun 29, 21:14 UTC | 5h 30m |
| 2026-06-29 | RAM201N | - | Jun 29, 02:25 UTC | Jun 29, 08:35 UTC | 6h 10m |
| 2026-06-28 | RAM200N | CMN → JFK | Jun 28, 16:05 UTC | Jun 28, 23:09 UTC | 7h 5m |
| 2026-06-28 | RAM200N | CMN → JFK | Jun 28, 15:44 UTC | Jun 28, 15:55 UTC | 10m |
| 2026-06-28 | RAM500B | - | Jun 28, 05:29 UTC | Jun 28, 05:49 UTC | 20m |
| 2026-06-28 | RAM500B | - | Jun 28, 03:09 UTC | Jun 28, 03:25 UTC | 15m |
| 2026-06-28 | RAM501B | - | Jun 28, 00:59 UTC | Jun 28, 01:25 UTC | 25m |
| 2026-06-27 | RAM911T | IST → CMN | Jun 27, 15:39 UTC | Jun 27, 19:45 UTC | 4h 5m |
| 2026-06-27 | RAM910T | - | Jun 27, 09:40 UTC | Jun 27, 13:30 UTC | 3h 50m |
| 2026-06-27 | RAM500B | - | Jun 27, 02:45 UTC | Jun 27, 02:59 UTC | 15m |
| 2026-06-27 | RAM501B | - | Jun 27, 00:39 UTC | Jun 27, 01:09 UTC | 30m |
| 2026-06-26 | RAM231 | - | Jun 26, 09:14 UTC | Jun 26, 17:54 UTC | 8h 40m |
| 2026-06-26 | RAM230 | CMN → PKX | Jun 26, 03:00 UTC | Jun 26, 03:15 UTC | 15m |
| 2026-06-25 | RAM230 | CMN → PKX | Jun 25, 16:05 UTC | Jun 25, 21:20 UTC | 5h 15m |
| 2026-06-25 | RAM201N | - | Jun 25, 01:40 UTC | Jun 25, 07:19 UTC | 5h 40m |
| 2026-06-24 | RAM200N | CMN → JFK | Jun 24, 15:49 UTC | Jun 24, 22:45 UTC | 6h 55m |
| 2026-06-24 | RAM251 | JED → CMN | Jun 24, 02:54 UTC | Jun 24, 15:44 UTC | 12h 50m |
| 2026-06-23 | RAM251 | JED → CMN | Jun 23, 17:39 UTC | Jun 24, 02:45 UTC | 9h 5m |
| 2026-06-23 | RAM250 | CMN → JED | Jun 23, 03:15 UTC | Jun 23, 14:44 UTC | 11h 30m |
| 2026-06-22 | RAM207T | - | Jun 22, 16:20 UTC | Jun 22, 21:54 UTC | 5h 35m |
| 2026-06-22 | RAM206T | - | Jun 22, 02:40 UTC | Jun 22, 14:24 UTC | 11h 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 CN-RAM page for operator, model, and routing details .