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
- 161
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- 1h ago
Last known 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
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| SBI5889 | - | 6 | 2026-07-10 |
| SBI5864 | - | 6 | 2026-07-08 |
| SBI5890 | - | 5 | 2026-07-10 |
| SBI5208 | - | 5 | 2026-07-13 |
| SBI6409 | S7 Airlines (Siberia Airlines) | 4 | 2026-05-10 |
| SBI6309 | S7 Airlines (Siberia Airlines) | 4 | 2026-05-17 |
| SBI6306 | S7 Airlines (Siberia Airlines) | 4 | 2026-05-19 |
| SBI6245 | S7 Airlines (Siberia Airlines) | 4 | 2026-06-07 |
| SBI5863 | - | 4 | 2026-07-08 |
| SBI5732 | - | 4 | 2026-07-12 |
| SBI5250 | - | 4 | 2026-07-05 |
| SBI6410 | S7 Airlines (Siberia Airlines) | 3 | 2026-05-10 |
| SBI6318 | S7 Airlines (Siberia Airlines) | 3 | 2026-05-18 |
| SBI6317 | S7 Airlines (Siberia Airlines) | 3 | 2026-05-17 |
| SBI5731 | S7 Airlines (Siberia Airlines) | 3 | 2026-06-14 |
| SBI5592 | - | 3 | 2026-07-12 |
| SBI5266 | - | 3 | 2026-07-07 |
| SBI5264 | - | 3 | 2026-07-07 |
| SBI5249 | S7 Airlines (Siberia Airlines) | 3 | 2026-06-29 |
| SBI5203 | - | 3 | 2026-04-18 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | SBI5265 | OVB → GDX | Jul 14, 14:30 UTC | Jul 15, 01:15 UTC | 10h 44m |
| 2026-07-13 | SBI5208 | - | Jul 13, 18:45 UTC | Jul 14, 06:40 UTC | 11h 55m |
| 2026-07-13 | SBI5892 | IST → OVB | Jul 13, 11:45 UTC | Jul 13, 12:15 UTC | 30m |
| 2026-07-13 | SBI5891 | OVB → IST | Jul 13, 09:45 UTC | Jul 13, 10:10 UTC | 25m |
| 2026-07-13 | SBI5891 | OVB → IST | Jul 13, 08:20 UTC | Jul 13, 09:10 UTC | 50m |
| 2026-07-12 | SBI5732 | - | Jul 12, 14:05 UTC | Jul 13, 02:20 UTC | 12h 15m |
| 2026-07-12 | SBI5592 | - | Jul 12, 07:50 UTC | Jul 12, 08:15 UTC | 25m |
| 2026-07-12 | SBI5591 | - | Jul 12, 05:05 UTC | Jul 12, 05:40 UTC | 35m |
| 2026-07-11 | SBI5009 | - | Jul 11, 16:35 UTC | Jul 11, 16:50 UTC | 15m |
| 2026-07-11 | SBI5009 | - | Jul 11, 14:05 UTC | Jul 11, 14:20 UTC | 15m |
| 2026-07-10 | SBI5207 | OVB → VVO | Jul 10, 18:50 UTC | Jul 11, 06:40 UTC | 11h 50m |
| 2026-07-10 | SBI5890 | - | Jul 10, 11:35 UTC | Jul 10, 13:20 UTC | 1h 45m |
| 2026-07-10 | SBI5889 | - | Jul 10, 09:35 UTC | Jul 10, 10:00 UTC | 25m |
| 2026-07-10 | SBI5889 | - | Jul 10, 07:25 UTC | Jul 10, 08:55 UTC | 1h 30m |
| 2026-07-09 | SBI5205 | - | Jul 9, 14:10 UTC | Jul 10, 02:05 UTC | 11h 55m |
| 2026-07-09 | SBI5065 | - | Jul 9, 02:35 UTC | Jul 9, 09:45 UTC | 7h 10m |
| 2026-07-08 | SBI5864 | - | Jul 8, 11:25 UTC | Jul 9, 09:45 UTC | 22h 20m |
| 2026-07-08 | SBI5863 | - | Jul 8, 08:00 UTC | Jul 8, 09:00 UTC | 1h 0m |
| 2026-07-07 | SBI5266 | - | Jul 7, 15:10 UTC | Jul 8, 02:00 UTC | 10h 50m |
| 2026-07-07 | SBI5264 | - | Jul 7, 00:05 UTC | Jul 7, 12:20 UTC | 12h 15m |
| 2026-07-05 | SBI5250 | - | Jul 5, 16:45 UTC | Jul 6, 05:55 UTC | 13h 10m |
| 2026-07-05 | SBI5104 | AER → OVB | Jul 5, 10:50 UTC | Jul 5, 11:05 UTC | 15m |
| 2026-07-04 | SBI5864 | - | Jul 4, 11:20 UTC | Jul 5, 11:05 UTC | 23h 45m |
| 2026-07-04 | SBI5864 | - | Jul 4, 11:10 UTC | Jul 4, 13:00 UTC | 1h 50m |
| 2026-07-03 | SBI5206 | - | Jul 3, 14:05 UTC | Jul 4, 02:00 UTC | 11h 55m |
| 2026-07-03 | SBI5066 | - | Jul 3, 02:35 UTC | Jul 3, 08:30 UTC | 5h 55m |
| 2026-07-01 | SBI5212 | - | Jul 1, 19:45 UTC | Jul 2, 04:55 UTC | 9h 10m |
| 2026-06-30 | SBI5247 | OVB → NER | Jun 30, 22:45 UTC | Jul 1, 06:45 UTC | 8h 0m |
| 2026-06-30 | SBI5009 | - | Jun 30, 14:55 UTC | Jun 30, 15:20 UTC | 25m |
| 2026-06-29 | SBI5249 | OVB → PKC | Jun 29, 16:29 UTC | Jun 29, 16:59 UTC | 30m |
| 2026-06-28 | SBI5732 | - | Jun 28, 13:59 UTC | Jun 29, 02:20 UTC | 12h 20m |
| 2026-06-28 | SBI5592 | - | Jun 28, 07:14 UTC | Jun 28, 07:40 UTC | 25m |
| 2026-06-27 | SBI5591 | - | Jun 27, 11:20 UTC | Jun 28, 05:34 UTC | 18h 15m |
| 2026-06-26 | SBI5208 | - | Jun 26, 19:24 UTC | Jun 27, 07:19 UTC | 11h 55m |
| 2026-06-25 | SBI5250 | - | Jun 25, 18:19 UTC | Jun 26, 08:05 UTC | 13h 45m |
| 2026-06-24 | SBI5250 | - | Jun 24, 16:34 UTC | Jun 25, 05:55 UTC | 13h 20m |
| 2026-06-24 | SBI5726 | - | Jun 24, 00:55 UTC | Jun 24, 04:55 UTC | 4h 0m |
| 2026-06-23 | SBI5725 | OVB → PKX | Jun 23, 22:34 UTC | Jun 23, 22:44 UTC | 10m |
| 2026-06-23 | SBI5255 | OVB → UUD | Jun 23, 00:19 UTC | Jun 23, 05:24 UTC | 5h 5m |
| 2026-06-22 | SBI5105 | OVB → AER | Jun 22, 12:10 UTC | Jun 22, 12:44 UTC | 35m |
| 2026-06-21 | SBI5250 | - | Jun 21, 16:25 UTC | Jun 22, 05:29 UTC | 13h 5m |
| 2026-06-21 | SBI5592 | EVN → OVB | Jun 21, 07:29 UTC | Jun 21, 07:55 UTC | 25m |
| 2026-06-20 | SBI5864 | AYT → OVB | Jun 20, 11:25 UTC | Jun 21, 05:54 UTC | 18h 30m |
| 2026-06-20 | SBI5863 | OVB → AYT | Jun 20, 09:29 UTC | Jun 20, 09:59 UTC | 30m |
| 2026-06-19 | SBI5890 | - | Jun 19, 10:54 UTC | Jun 19, 11:24 UTC | 30m |
| 2026-06-18 | SBI8991 | OVB → OVB | Jun 18, 01:45 UTC | Jun 18, 15:45 UTC | 14h 0m |
| 2026-06-17 | SBI5864 | AYT → OVB | Jun 17, 11:25 UTC | Jun 17, 13:15 UTC | 1h 50m |
| 2026-06-17 | SBI5863 | OVB → AYT | Jun 17, 09:35 UTC | Jun 17, 10:10 UTC | 35m |
| 2026-06-16 | SBI5259 | OVB → UUS | Jun 16, 14:35 UTC | Jun 17, 02:20 UTC | 11h 46m |
| 2026-06-15 | SBI5208 | - | Jun 15, 16:24 UTC | Jun 16, 06:45 UTC | 14h 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 RA-73669 page for operator, model, and routing details .