sensors Mode-S transponder
151FC0
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73664 · BOEING 737-800
- Hex
- 151FC0
- Octal
- 05217700
- Decimal
- 1,384,384
- Country
- RU
- Tail
- RA-73664
- Type
- B738
- Flights observed
- 102
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- 10h ago
Last known position
Country allocation
The ICAO 24-bit address 151FC0 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-29 | SBI5207 | OVB → VVO | May 29, 18:55 UTC | May 29, 19:25 UTC | 30m |
| 2026-05-28 | SBI5250 | PKC → OVB | May 28, 16:30 UTC | May 29, 06:00 UTC | 13h 30m |
| 2026-05-28 | SBI5066 | KGD → OVB | May 28, 07:40 UTC | May 28, 12:10 UTC | 4h 30m |
| 2026-05-28 | SBI5065 | OVB → KGD | May 28, 00:25 UTC | May 28, 05:05 UTC | 4h 40m |
| 2026-05-25 | SBI5250 | PKC → OVB | May 25, 12:00 UTC | May 26, 05:45 UTC | 17h 44m |
| 2026-05-25 | SBI5250 | PKC → OVB | May 25, 07:35 UTC | May 26, 05:45 UTC | 22h 9m |
| 2026-05-24 | SBI5203 | OVB → VVO | May 24, 16:15 UTC | May 25, 04:35 UTC | 12h 20m |
| 2026-05-23 | SBI5066 | KGD → OVB | May 23, 16:15 UTC | May 23, 17:15 UTC | 1h 0m |
| 2026-05-23 | SBI5065 | OVB → KGD | May 23, 08:40 UTC | May 23, 13:55 UTC | 5h 15m |
| 2026-05-22 | SBI5249 | OVB → PKC | May 22, 16:55 UTC | May 23, 06:25 UTC | 13h 30m |
| 2026-05-20 | SBI5204 | VVO → OVB | May 20, 17:15 UTC | May 21, 05:35 UTC | 12h 20m |
| 2026-05-19 | SBI5240 | IKT → OVB | May 19, 14:30 UTC | May 20, 02:50 UTC | 12h 20m |
| 2026-05-19 | SBI5240 | IKT → OVB | May 19, 04:05 UTC | May 20, 02:50 UTC | 22h 45m |
| 2026-05-19 | SBI5258 | UUS → OVB | May 19, 03:30 UTC | May 19, 16:55 UTC | 13h 25m |
| 2026-05-18 | SBI5258 | UUS → OVB | May 18, 16:25 UTC | May 19, 14:30 UTC | 22h 4m |
| 2026-05-18 | SBI5258 | UUS → OVB | May 18, 04:05 UTC | May 19, 04:00 UTC | 23h 54m |
| 2026-05-18 | SBI5258 | UUS → OVB | May 18, 03:50 UTC | May 18, 16:50 UTC | 13h 0m |
| 2026-05-17 | SBI5258 | UUS → OVB | May 17, 16:40 UTC | May 18, 04:20 UTC | 11h 40m |
| 2026-05-17 | SBI5240 | IKT → OVB | May 17, 00:55 UTC | May 17, 16:55 UTC | 16h 0m |
| 2026-05-16 | SBI5240 | IKT → OVB | May 16, 15:05 UTC | May 17, 01:30 UTC | 10h 25m |
| 2026-05-15 | SBI5239 | OVB → IKT | May 15, 18:55 UTC | May 16, 15:25 UTC | 20h 31m |
| 2026-05-13 | SBI5204 | VVO → OVB | May 13, 04:10 UTC | May 13, 17:50 UTC | 13h 40m |
| 2026-05-12 | SBI5204 | VVO → OVB | May 12, 16:45 UTC | May 13, 12:50 UTC | 20h 5m |
| 2026-05-12 | SBI5204 | VVO → OVB | May 12, 10:55 UTC | May 13, 07:30 UTC | 20h 35m |
| 2026-05-12 | SBI5258 | UUS → OVB | May 12, 04:00 UTC | May 12, 16:55 UTC | 12h 55m |
| 2026-05-11 | SBI5258 | UUS → OVB | May 11, 16:25 UTC | May 12, 11:10 UTC | 18h 46m |
| 2026-05-09 | SBI5117 | OVB → KRR | May 9, 10:20 UTC | May 10, 05:50 UTC | 19h 30m |
| 2026-05-09 | SBI5246 | NER → OVB | May 9, 02:25 UTC | May 9, 02:55 UTC | 30m |
| 2026-05-08 | SBI5232 | IKT → OVB | May 8, 03:04 UTC | May 8, 03:39 UTC | 35m |
| 2026-05-07 | SBI6402 | BTK → KJA | May 7, 17:05 UTC | May 7, 23:49 UTC | 6h 44m |
| 2026-05-07 | SBI6409 | IKT → LED | May 7, 03:40 UTC | May 7, 07:40 UTC | 4h 0m |
| 2026-05-07 | SBI6409 | IKT → LED | May 7, 02:10 UTC | May 7, 02:20 UTC | 10m |
| 2026-05-06 | SBI6402 | BTK → KJA | May 6, 17:45 UTC | May 6, 23:55 UTC | 6h 10m |
| 2026-05-06 | SBI6415 | IKT → SVX | May 6, 04:40 UTC | May 6, 10:45 UTC | 6h 5m |
| 2026-05-06 | SBI6415 | IKT → SVX | May 6, 03:10 UTC | May 6, 03:20 UTC | 10m |
| 2026-05-06 | SBI6404 | VVO → IKT | May 6, 01:15 UTC | May 6, 01:40 UTC | 25m |
| 2026-05-05 | SBI6403 | IKT → VVO | May 5, 16:45 UTC | May 5, 17:05 UTC | 20m |
| 2026-05-05 | SBI6410 | LED → IKT | May 5, 09:55 UTC | May 5, 13:45 UTC | 3h 50m |
| 2026-05-04 | SBI6409 | IKT → LED | May 4, 12:05 UTC | May 5, 07:50 UTC | 19h 46m |
| 2026-05-04 | SBI6409 | IKT → LED | May 4, 11:45 UTC | May 5, 07:50 UTC | 20h 6m |
| 2026-05-04 | SBI6419 | IKT → UFA | May 4, 05:35 UTC | May 4, 12:25 UTC | 6h 50m |
| 2026-05-03 | SBI6410 | LED → IKT | May 3, 13:20 UTC | May 3, 13:45 UTC | 25m |
| 2026-05-03 | SBI6410 | LED → IKT | May 3, 09:45 UTC | May 3, 10:05 UTC | 20m |
| 2026-05-02 | SBI6409 | IKT → LED | May 2, 17:30 UTC | May 3, 07:35 UTC | 14h 4m |
| 2026-05-02 | SBI6410 | LED → IKT | May 2, 14:55 UTC | May 2, 15:05 UTC | 10m |
| 2026-05-02 | SBI6409 | IKT → LED | May 2, 03:45 UTC | May 2, 13:45 UTC | 10h 0m |
| 2026-05-01 | SBI6402 | BTK → KJA | May 1, 23:15 UTC | May 1, 23:35 UTC | 20m |
| 2026-05-01 | SBI6401 | KJA → BTK | May 1, 17:20 UTC | May 1, 17:40 UTC | 20m |
| 2026-05-01 | SBI6410 | LED → IKT | May 1, 11:10 UTC | May 1, 11:25 UTC | 15m |
| 2026-05-01 | SBI6410 | LED → IKT | May 1, 09:50 UTC | May 1, 10:05 UTC | 15m |
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-73664 page for operator, model, and routing details .