sensors Mode-S transponder
151FC1
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73665 · BOEING 737-800
- Hex
- 151FC1
- Octal
- 05217701
- Decimal
- 1,384,385
- Country
- RU
- Tail
- RA-73665
- Type
- B738
- Flights observed
- 70
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 151FC1 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-06-11 | SBI6409 | IKT → LED | Jun 11, 12:50 UTC | Jun 12, 07:05 UTC | 18h 15m |
| 2026-06-11 | SBI6415 | IKT → SVX | Jun 11, 06:50 UTC | Jun 12, 06:15 UTC | 23h 26m |
| 2026-06-09 | SBI6409 | IKT → LED | Jun 9, 05:45 UTC | Jun 9, 13:55 UTC | 8h 10m |
| 2026-06-08 | SBI6409 | IKT → LED | Jun 8, 12:20 UTC | Jun 9, 11:15 UTC | 22h 55m |
| 2026-06-08 | SBI6409 | IKT → LED | Jun 8, 11:50 UTC | Jun 9, 07:10 UTC | 19h 20m |
| 2026-06-08 | SBI6419 | IKT → UFA | Jun 8, 05:20 UTC | Jun 8, 12:30 UTC | 7h 10m |
| 2026-06-07 | SBI6419 | IKT → UFA | Jun 7, 13:30 UTC | Jun 8, 12:15 UTC | 22h 45m |
| 2026-06-07 | SBI6410 | LED → IKT | Jun 7, 09:45 UTC | Jun 7, 10:10 UTC | 25m |
| 2026-06-06 | SBI6409 | IKT → LED | Jun 6, 13:30 UTC | Jun 7, 07:10 UTC | 17h 40m |
| 2026-06-06 | SBI6409 | IKT → LED | Jun 6, 10:45 UTC | Jun 7, 07:10 UTC | 20h 25m |
| 2026-06-06 | SBI6410 | LED → IKT | Jun 6, 09:45 UTC | Jun 6, 10:04 UTC | 20m |
| 2026-06-05 | SBI6409 | IKT → LED | Jun 5, 13:50 UTC | Jun 6, 07:00 UTC | 17h 10m |
| 2026-06-04 | SBI6409 | IKT → LED | Jun 4, 12:45 UTC | Jun 5, 07:05 UTC | 18h 20m |
| 2026-06-04 | SBI6416 | SVX → IKT | Jun 4, 06:50 UTC | Jun 5, 06:15 UTC | 23h 25m |
| 2026-06-02 | SBI6410 | LED → IKT | Jun 2, 10:45 UTC | Jun 2, 14:00 UTC | 3h 15m |
| 2026-06-02 | SBI6410 | LED → IKT | Jun 2, 09:50 UTC | Jun 2, 10:05 UTC | 15m |
| 2026-06-01 | SBI6409 | IKT → LED | Jun 1, 13:20 UTC | Jun 2, 07:15 UTC | 17h 55m |
| 2026-06-01 | SBI6409 | IKT → LED | Jun 1, 06:20 UTC | Jun 2, 04:10 UTC | 21h 50m |
| 2026-06-01 | SBI6409 | IKT → LED | Jun 1, 05:45 UTC | Jun 2, 04:10 UTC | 22h 25m |
| 2026-05-31 | SBI6409 | IKT → LED | May 31, 22:05 UTC | Jun 1, 13:50 UTC | 15h 45m |
| 2026-05-29 | SBI5266 | GDX → OVB | May 29, 14:35 UTC | May 30, 01:45 UTC | 11h 10m |
| 2026-05-28 | SBI2502 | OVB → DME | May 28, 23:20 UTC | May 29, 06:10 UTC | 6h 50m |
| 2026-05-27 | SBI5212 | BQS → OVB | May 27, 20:05 UTC | May 28, 05:05 UTC | 9h 0m |
| 2026-05-27 | SBI5105 | OVB → AER | May 27, 12:00 UTC | May 27, 12:20 UTC | 20m |
| 2026-05-27 | SBI5266 | GDX → OVB | May 27, 01:05 UTC | May 27, 01:39 UTC | 35m |
| 2026-05-25 | SBI5284 | PWE → OVB | May 25, 22:00 UTC | May 26, 11:34 UTC | 13h 35m |
| 2026-05-24 | SBI5006 | LED → OVB | May 24, 12:50 UTC | May 24, 16:25 UTC | 3h 35m |
| 2026-05-24 | SBI5005 | OVB → LED | May 24, 11:15 UTC | May 24, 11:35 UTC | 20m |
| 2026-05-24 | SBI5005 | OVB → LED | May 24, 07:20 UTC | May 24, 09:50 UTC | 2h 30m |
| 2026-05-23 | SBI5212 | BQS → OVB | May 23, 20:10 UTC | May 24, 05:10 UTC | 9h 0m |
| 2026-05-22 | SBI5204 | VVO → OVB | May 22, 16:20 UTC | May 23, 04:20 UTC | 11h 59m |
| 2026-05-22 | SBI5046 | UFA → OVB | May 22, 08:55 UTC | May 22, 12:50 UTC | 3h 55m |
| 2026-05-21 | SBI5258 | UUS → OVB | May 21, 16:25 UTC | May 22, 04:25 UTC | 12h 0m |
| 2026-05-21 | SBI5046 | UFA → OVB | May 21, 09:15 UTC | May 21, 11:35 UTC | 2h 20m |
| 2026-05-20 | SBI5212 | BQS → OVB | May 20, 19:40 UTC | May 21, 05:20 UTC | 9h 40m |
| 2026-05-20 | SBI5151 | OVB → MCX | May 20, 10:40 UTC | May 20, 11:05 UTC | 25m |
| 2026-05-19 | SBI5204 | VVO → OVB | May 19, 17:05 UTC | May 20, 04:35 UTC | 11h 30m |
| 2026-05-19 | SBI5204 | VVO → OVB | May 19, 08:20 UTC | May 20, 04:35 UTC | 20h 15m |
| 2026-05-19 | SBI5127 | OVB → MRV | May 19, 07:50 UTC | May 20, 04:35 UTC | 20h 45m |
| 2026-05-19 | SBI5127 | OVB → MRV | May 19, 02:05 UTC | May 19, 17:20 UTC | 15h 15m |
| 2026-05-18 | SBI5127 | OVB → MRV | May 18, 15:20 UTC | May 19, 08:40 UTC | 17h 19m |
| 2026-05-18 | SBI5105 | OVB → AER | May 18, 10:25 UTC | May 19, 08:40 UTC | 22h 14m |
| 2026-05-16 | SBI5066 | KGD → OVB | May 16, 15:50 UTC | May 17, 07:55 UTC | 16h 5m |
| 2026-05-16 | SBI5065 | OVB → KGD | May 16, 05:30 UTC | May 16, 13:35 UTC | 8h 6m |
| 2026-05-15 | SBI5065 | OVB → KGD | May 15, 17:10 UTC | May 16, 13:35 UTC | 20h 26m |
| 2026-05-15 | SBI5250 | PKC → OVB | May 15, 07:15 UTC | May 16, 06:06 UTC | 22h 50m |
| 2026-05-14 | SBI5066 | KGD → OVB | May 14, 07:30 UTC | May 14, 11:55 UTC | 4h 25m |
| 2026-05-13 | SBI5103 | OVB → AER | May 13, 07:05 UTC | May 13, 08:00 UTC | 55m |
| 2026-05-11 | SBI5250 | PKC → OVB | May 11, 16:40 UTC | May 12, 05:55 UTC | 13h 16m |
| 2026-05-11 | SBI5066 | KGD → OVB | May 11, 09:25 UTC | May 12, 05:55 UTC | 20h 30m |
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-73665 page for operator, model, and routing details .