sensors Mode-S transponder
47C1C2
ICAO 24-bit transponder address · allocated to Norway
Currently assigned to LN-RKU · AIRBUS A-330-300
- Hex
- 47C1C2
- Octal
- 21740702
- Decimal
- 4,702,658
- Country
- NO
- Tail
- LN-RKU
- Type
- A333
- Flights observed
- 160
- Distinct callsigns
- 14
- Country
- NO
- Last broadcast
- 23h ago
Last known position
Country allocation
The ICAO 24-bit address 47C1C2 falls within the block assigned to Norway (NO) by ICAO Annex 10, Volume III. Every aircraft registered in Norway 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 14 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| SAS932 | - | 34 | 2026-07-13 |
| SAS931 | - | 32 | 2026-07-12 |
| SAS916 | - | 14 | 2026-07-07 |
| SAS944 | - | 13 | 2026-07-08 |
| SAS943 | - | 13 | 2026-07-07 |
| SAS915 | Scandinavian Airlines System | 13 | 2026-07-06 |
| SAS927 | Scandinavian Airlines System | 11 | 2026-06-05 |
| SAS928 | Scandinavian Airlines System | 10 | 2026-06-05 |
| SAS930 | Scandinavian Airlines System | 9 | 2026-05-02 |
| SAS929 | Scandinavian Airlines System | 7 | 2026-05-02 |
| SAS926 | - | 1 | 2026-06-21 |
| SAS925 | Scandinavian Airlines System | 1 | 2026-06-20 |
| SAS910 | Scandinavian Airlines System | 1 | 2026-05-27 |
| SAS909 | Scandinavian Airlines System | 1 | 2026-05-26 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | SAS932 | - | Jul 13, 01:55 UTC | Jul 13, 12:00 UTC | 10h 5m |
| 2026-07-12 | SAS931 | - | Jul 12, 12:20 UTC | Jul 12, 23:20 UTC | 11h 0m |
| 2026-07-11 | SAS932 | - | Jul 11, 02:25 UTC | Jul 11, 12:40 UTC | 10h 15m |
| 2026-07-10 | SAS931 | - | Jul 10, 12:30 UTC | Jul 10, 23:40 UTC | 11h 10m |
| 2026-07-09 | SAS932 | LAX → CPH | Jul 9, 02:30 UTC | Jul 9, 12:50 UTC | 10h 20m |
| 2026-07-08 | SAS931 | - | Jul 8, 12:35 UTC | Jul 8, 23:45 UTC | 11h 10m |
| 2026-07-08 | SAS944 | - | Jul 8, 00:45 UTC | Jul 8, 08:30 UTC | 7h 45m |
| 2026-07-07 | SAS943 | - | Jul 7, 12:10 UTC | Jul 7, 21:00 UTC | 8h 50m |
| 2026-07-07 | SAS916 | JFK → CPH | Jul 7, 00:30 UTC | Jul 7, 07:10 UTC | 6h 40m |
| 2026-07-06 | SAS915 | CPH → JFK | Jul 6, 13:10 UTC | Jul 6, 21:25 UTC | 8h 15m |
| 2026-07-06 | SAS944 | ORD → CPH | Jul 6, 03:05 UTC | Jul 6, 10:40 UTC | 7h 35m |
| 2026-07-05 | SAS943 | - | Jul 5, 14:50 UTC | Jul 5, 23:35 UTC | 8h 45m |
| 2026-07-05 | SAS932 | LAX → CPH | Jul 5, 02:10 UTC | Jul 5, 12:15 UTC | 10h 5m |
| 2026-07-04 | SAS931 | CPH → LAX | Jul 4, 12:30 UTC | Jul 4, 23:25 UTC | 10h 55m |
| 2026-07-03 | SAS932 | LAX → CPH | Jul 3, 02:30 UTC | Jul 3, 12:45 UTC | 10h 15m |
| 2026-07-02 | SAS931 | CPH → LAX | Jul 2, 12:40 UTC | Jul 2, 23:40 UTC | 11h 0m |
| 2026-07-01 | SAS916 | JFK → CPH | Jul 1, 23:30 UTC | Jul 2, 06:20 UTC | 6h 50m |
| 2026-07-01 | SAS915 | CPH → JFK | Jul 1, 12:35 UTC | Jul 1, 20:30 UTC | 7h 55m |
| 2026-07-01 | SAS944 | ORD → CPH | Jul 1, 01:00 UTC | Jul 1, 08:35 UTC | 7h 35m |
| 2026-06-30 | SAS943 | - | Jun 30, 12:15 UTC | Jun 30, 20:55 UTC | 8h 40m |
| 2026-06-29 | SAS916 | - | Jun 29, 00:20 UTC | Jun 29, 07:40 UTC | 7h 20m |
| 2026-06-28 | SAS915 | CPH → JFK | Jun 28, 12:35 UTC | Jun 28, 20:29 UTC | 7h 55m |
| 2026-06-28 | SAS944 | - | Jun 28, 00:25 UTC | Jun 28, 08:19 UTC | 7h 55m |
| 2026-06-27 | SAS943 | - | Jun 27, 12:04 UTC | Jun 27, 20:39 UTC | 8h 35m |
| 2026-06-25 | SAS916 | - | Jun 25, 23:55 UTC | Jun 26, 06:29 UTC | 6h 35m |
| 2026-06-25 | SAS915 | CPH → JFK | Jun 25, 12:35 UTC | Jun 25, 20:45 UTC | 8h 10m |
| 2026-06-25 | SAS944 | ORD → CPH | Jun 25, 01:44 UTC | Jun 25, 09:14 UTC | 7h 30m |
| 2026-06-24 | SAS943 | - | Jun 24, 12:20 UTC | Jun 24, 20:49 UTC | 8h 30m |
| 2026-06-23 | SAS932 | LAX → CPH | Jun 23, 02:24 UTC | Jun 23, 12:40 UTC | 10h 15m |
| 2026-06-22 | SAS931 | CPH → LAX | Jun 22, 12:59 UTC | Jun 23, 00:15 UTC | 11h 15m |
| 2026-06-22 | SAS944 | - | Jun 22, 00:40 UTC | Jun 22, 08:19 UTC | 7h 40m |
| 2026-06-21 | SAS943 | CPH → ORD | Jun 21, 12:10 UTC | Jun 21, 20:59 UTC | 8h 50m |
| 2026-06-21 | SAS926 | IAD → CPH | Jun 21, 01:05 UTC | Jun 21, 08:15 UTC | 7h 10m |
| 2026-06-20 | SAS925 | CPH → IAD | Jun 20, 13:39 UTC | Jun 20, 21:40 UTC | 8h 0m |
| 2026-06-19 | SAS916 | JFK → CPH | Jun 19, 23:49 UTC | Jun 20, 06:29 UTC | 6h 40m |
| 2026-06-19 | SAS915 | CPH → JFK | Jun 19, 12:39 UTC | Jun 19, 20:40 UTC | 8h 0m |
| 2026-06-19 | SAS944 | ORD → CPH | Jun 19, 01:04 UTC | Jun 19, 08:50 UTC | 7h 45m |
| 2026-06-18 | SAS943 | - | Jun 18, 12:10 UTC | Jun 18, 20:45 UTC | 8h 35m |
| 2026-06-17 | SAS932 | LAX → CPH | Jun 17, 02:15 UTC | Jun 17, 12:40 UTC | 10h 25m |
| 2026-06-16 | SAS931 | CPH → LAX | Jun 16, 12:20 UTC | Jun 16, 23:00 UTC | 10h 41m |
| 2026-06-15 | SAS932 | LAX → CPH | Jun 15, 02:24 UTC | Jun 15, 13:00 UTC | 10h 35m |
| 2026-06-14 | SAS931 | CPH → LAX | Jun 14, 12:45 UTC | Jun 14, 23:29 UTC | 10h 45m |
| 2026-06-13 | SAS932 | LAX → CPH | Jun 13, 02:25 UTC | Jun 13, 12:45 UTC | 10h 19m |
| 2026-06-12 | SAS931 | CPH → LAX | Jun 12, 12:40 UTC | Jun 12, 23:30 UTC | 10h 50m |
| 2026-06-11 | SAS916 | JFK → CPH | Jun 11, 23:55 UTC | Jun 12, 07:00 UTC | 7h 6m |
| 2026-06-11 | SAS915 | CPH → JFK | Jun 11, 12:45 UTC | Jun 11, 20:20 UTC | 7h 35m |
| 2026-06-09 | SAS916 | JFK → CPH | Jun 9, 23:35 UTC | Jun 10, 06:45 UTC | 7h 10m |
| 2026-06-09 | SAS915 | CPH → JFK | Jun 9, 12:45 UTC | Jun 9, 20:20 UTC | 7h 35m |
| 2026-06-09 | SAS916 | JFK → CPH | Jun 9, 02:25 UTC | Jun 9, 09:40 UTC | 7h 15m |
| 2026-06-08 | SAS915 | CPH → JFK | Jun 8, 15:10 UTC | Jun 8, 22:30 UTC | 7h 20m |
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 LN-RKU page for operator, model, and routing details .