sensors Mode-S transponder
151FC5
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73669 · BOEING 737-800
- Hex
- 151FC5
- Octal
- 05217705
- Decimal
- 1,384,389
- Country
- RU
- Tail
- RA-73669
- Type
- B738
- Flights observed
- 90
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- 3h ago
Current position
Country allocation
The ICAO 24-bit address 151FC5 falls within the block assigned to Russia (RU) by ICAO Annex 10, Volume III. Every aircraft registered in Russia 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
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-30 | SBI5889 | OVB → IST | May 30, 09:20 UTC | May 30, 09:30 UTC | 10m |
| 2026-05-29 | SBI5033 | - | May 29, 15:55 UTC | May 29, 22:30 UTC | 6h 35m |
| 2026-05-27 | SBI5264 | YKS → OVB | May 27, 11:25 UTC | May 28, 02:40 UTC | 15h 15m |
| 2026-05-26 | SBI5240 | IKT → OVB | May 26, 14:45 UTC | May 27, 01:29 UTC | 10h 45m |
| 2026-05-25 | SBI5728 | XIY → OVB | May 25, 17:10 UTC | May 26, 02:44 UTC | 9h 35m |
| 2026-05-24 | SBI5731 | OVB → PVG | May 24, 13:55 UTC | May 25, 02:05 UTC | 12h 10m |
| 2026-05-23 | SBI5257 | OVB → UUS | May 23, 18:10 UTC | May 24, 05:55 UTC | 11h 45m |
| 2026-05-21 | SBI5249 | OVB → PKC | May 21, 16:35 UTC | May 22, 06:05 UTC | 13h 30m |
| 2026-05-20 | SBI5555 | OVB → LBD | May 20, 07:05 UTC | May 20, 07:30 UTC | 25m |
| 2026-05-19 | SBI6306 | BKK → IKT | May 19, 09:20 UTC | May 20, 03:20 UTC | 18h 0m |
| 2026-05-19 | SBI6306 | BKK → IKT | May 19, 09:00 UTC | May 20, 03:20 UTC | 18h 20m |
| 2026-05-19 | SBI6305 | IKT → BKK | May 19, 07:10 UTC | May 19, 07:40 UTC | 30m |
| 2026-05-18 | SBI6318 | OSS → IKT | May 18, 05:15 UTC | May 18, 06:05 UTC | 50m |
| 2026-05-17 | SBI6317 | IKT → OSS | May 17, 14:15 UTC | May 18, 03:55 UTC | 13h 40m |
| 2026-05-17 | SBI6309 | IKT → BKK | May 17, 11:40 UTC | May 17, 12:40 UTC | 1h 0m |
| 2026-05-16 | SBI6310 | BKK → IKT | May 16, 10:25 UTC | May 16, 11:16 UTC | 50m |
| 2026-05-15 | SBI6309 | IKT → BKK | May 15, 14:05 UTC | May 16, 08:46 UTC | 18h 40m |
| 2026-05-15 | SBI6318 | OSS → IKT | May 15, 04:40 UTC | May 15, 15:15 UTC | 10h 34m |
| 2026-05-14 | SBI6317 | IKT → OSS | May 14, 13:35 UTC | May 15, 03:05 UTC | 13h 30m |
| 2026-05-14 | SBI6309 | IKT → BKK | May 14, 10:55 UTC | May 14, 12:00 UTC | 1h 5m |
| 2026-05-13 | SBI6402 | BTK → KJA | May 13, 17:10 UTC | May 13, 23:50 UTC | 6h 40m |
| 2026-05-13 | SBI6416 | SVX → IKT | May 13, 12:25 UTC | May 13, 12:35 UTC | 10m |
| 2026-05-13 | SBI6416 | SVX → IKT | May 13, 10:40 UTC | May 13, 11:15 UTC | 35m |
| 2026-05-13 | SBI6415 | IKT → SVX | May 13, 07:05 UTC | May 13, 07:15 UTC | 10m |
| 2026-05-13 | SBI6415 | IKT → SVX | May 13, 04:45 UTC | May 13, 05:25 UTC | 40m |
| 2026-05-13 | SBI6312 | PKX → IKT | May 13, 00:20 UTC | May 13, 00:35 UTC | 15m |
| 2026-05-12 | SBN6311 | - | May 12, 17:45 UTC | May 12, 18:00 UTC | 15m |
| 2026-05-12 | SBI6306 | BKK → IKT | May 12, 14:15 UTC | May 12, 14:35 UTC | 20m |
| 2026-05-12 | SBI6306 | BKK → IKT | May 12, 09:05 UTC | May 12, 10:05 UTC | 1h 0m |
| 2026-05-11 | SBI6305 | IKT → BKK | May 11, 13:45 UTC | May 12, 07:45 UTC | 18h 1m |
| 2026-05-10 | SBI6410 | LED → IKT | May 10, 10:30 UTC | May 11, 00:30 UTC | 14h 0m |
| 2026-05-10 | SBI6410 | LED → IKT | May 10, 09:40 UTC | May 10, 09:55 UTC | 15m |
| 2026-05-10 | SBI6409 | IKT → LED | May 10, 08:00 UTC | May 10, 08:10 UTC | 10m |
| 2026-05-10 | SBI6409 | IKT → LED | May 10, 06:30 UTC | May 10, 07:19 UTC | 50m |
| 2026-05-09 | SBI6310 | BKK → IKT | May 9, 10:05 UTC | May 9, 15:55 UTC | 5h 50m |
| 2026-05-09 | SBI6309 | IKT → BKK | May 9, 02:55 UTC | May 9, 08:35 UTC | 5h 40m |
| 2026-05-08 | SBI6331 | IKT → YKS | May 8, 14:05 UTC | May 8, 20:30 UTC | 6h 25m |
| 2026-05-08 | SBI6331 | IKT → YKS | May 8, 12:49 UTC | May 8, 12:55 UTC | 5m |
| 2026-05-07 | SBI6403 | IKT → VVO | May 7, 16:45 UTC | May 7, 17:00 UTC | 15m |
| 2026-05-06 | SBI6404 | VVO → IKT | May 6, 16:50 UTC | May 7, 01:45 UTC | 8h 55m |
| 2026-05-06 | SBI6410 | LED → IKT | May 6, 09:45 UTC | May 6, 10:01 UTC | 15m |
| 2026-05-06 | SBI6409 | IKT → LED | May 6, 03:35 UTC | May 6, 08:30 UTC | 4h 55m |
| 2026-05-06 | SBI6409 | IKT → LED | May 6, 02:05 UTC | May 6, 02:20 UTC | 15m |
| 2026-05-05 | SBI6430 | UUD → IKT | May 5, 22:50 UTC | May 5, 23:15 UTC | 25m |
| 2026-05-05 | SBI6429 | IKT → UUD | May 5, 21:30 UTC | May 5, 21:40 UTC | 10m |
| 2026-05-05 | SBI5235 | OVB → IKT | May 5, 16:06 UTC | May 5, 16:40 UTC | 35m |
| 2026-05-04 | SBI5211 | OVB → BQS | May 4, 19:40 UTC | May 5, 04:55 UTC | 9h 15m |
| 2026-05-04 | SBI5864 | AYT → OVB | May 4, 12:35 UTC | May 4, 14:25 UTC | 1h 50m |
| 2026-05-03 | SBI5732 | PVG → OVB | May 3, 13:55 UTC | May 4, 02:54 UTC | 13h 0m |
| 2026-05-03 | SBI5230 | IKT → OVB | May 3, 06:40 UTC | May 3, 07:20 UTC | 40m |
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 RA-73669 page for operator, model, and routing details .