sensors Mode-S transponder
151FC6
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73670 · BOEING 737-800
- Hex
- 151FC6
- Octal
- 05217706
- Decimal
- 1,384,390
- Country
- RU
- Tail
- RA-73670
- Type
- B738
- Flights observed
- 74
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- 6h ago
Last known position
Country allocation
The ICAO 24-bit address 151FC6 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 | SBI5212 | BQS → OVB | May 29, 19:30 UTC | May 30, 05:10 UTC | 9h 40m |
| 2026-05-28 | SBI2509 | DME → OVB | May 28, 19:35 UTC | May 29, 14:25 UTC | 18h 50m |
| 2026-05-28 | SBI5207 | OVB → VVO | May 28, 19:05 UTC | May 29, 14:25 UTC | 19h 20m |
| 2026-05-28 | SBI2510 | OVB → DME | May 28, 08:45 UTC | May 28, 11:10 UTC | 2h 25m |
| 2026-05-27 | SBI5208 | VVO → OVB | May 27, 18:55 UTC | May 28, 06:55 UTC | 12h 0m |
| 2026-05-27 | SBI2510 | OVB → DME | May 27, 08:35 UTC | May 27, 15:10 UTC | 6h 35m |
| 2026-05-26 | SBI5250 | PKC → OVB | May 26, 16:40 UTC | May 27, 05:45 UTC | 13h 5m |
| 2026-05-25 | SBI5864 | AYT → OVB | May 25, 11:20 UTC | May 25, 13:20 UTC | 2h 0m |
| 2026-05-24 | SBI5864 | AYT → OVB | May 24, 11:10 UTC | May 24, 11:30 UTC | 20m |
| 2026-05-23 | SBI5863 | OVB → AYT | May 23, 14:00 UTC | May 24, 08:30 UTC | 18h 31m |
| 2026-05-23 | SBI2510 | OVB → DME | May 23, 10:15 UTC | May 23, 11:20 UTC | 1h 5m |
| 2026-05-22 | SBI5207 | OVB → VVO | May 22, 18:45 UTC | May 23, 06:40 UTC | 11h 54m |
| 2026-05-22 | SBI5575 | OVB → AZN | May 22, 07:20 UTC | May 22, 12:55 UTC | 5h 35m |
| 2026-05-21 | SBI5228 | IKT → OVB | May 21, 20:05 UTC | May 22, 01:10 UTC | 5h 5m |
| 2026-05-20 | SBI5240 | IKT → OVB | May 20, 14:45 UTC | May 21, 01:20 UTC | 10h 35m |
| 2026-05-19 | SBI5258 | UUS → OVB | May 19, 15:30 UTC | May 20, 06:10 UTC | 14h 41m |
| 2026-05-19 | SBI5258 | UUS → OVB | May 19, 07:35 UTC | May 20, 06:10 UTC | 22h 36m |
| 2026-05-19 | SBI5204 | VVO → OVB | May 19, 03:40 UTC | May 19, 19:05 UTC | 15h 25m |
| 2026-05-17 | SBI6246 | PVG → VVO | May 17, 19:20 UTC | May 18, 00:30 UTC | 5h 10m |
| 2026-05-15 | SBI6245 | VVO → PVG | May 15, 18:50 UTC | May 16, 00:20 UTC | 5h 30m |
| 2026-05-13 | SBI6245 | VVO → PVG | May 13, 18:30 UTC | May 13, 23:50 UTC | 5h 20m |
| 2026-05-11 | SBI5212 | BQS → OVB | May 11, 04:45 UTC | May 11, 16:55 UTC | 12h 10m |
| 2026-05-10 | SBI5212 | BQS → OVB | May 10, 19:50 UTC | May 11, 16:55 UTC | 21h 5m |
| 2026-05-10 | SBI5250 | PKC → OVB | May 10, 05:34 UTC | May 11, 05:20 UTC | 23h 45m |
| 2026-05-09 | SBI5208 | VVO → OVB | May 9, 06:25 UTC | May 10, 05:30 UTC | 23h 5m |
| 2026-05-08 | SBI6262 | BKK → VVO | May 8, 13:50 UTC | May 9, 07:05 UTC | 17h 15m |
| 2026-05-08 | SBI6261 | VVO → BKK | May 8, 07:04 UTC | May 8, 12:30 UTC | 5h 25m |
| 2026-05-06 | SBI6245 | VVO → PVG | May 6, 18:55 UTC | May 7, 00:10 UTC | 5h 15m |
| 2026-05-04 | SBI5207 | OVB → VVO | May 4, 18:55 UTC | May 4, 19:25 UTC | 30m |
| 2026-05-04 | SBI2510 | OVB → DME | May 4, 08:30 UTC | May 4, 08:40 UTC | 10m |
| 2026-05-03 | SBI5207 | OVB → VVO | May 3, 18:55 UTC | May 4, 06:50 UTC | 11h 55m |
| 2026-05-03 | SBI5864 | AYT → OVB | May 3, 11:30 UTC | May 3, 13:20 UTC | 1h 50m |
| 2026-05-02 | SBI5066 | KGD → OVB | May 2, 16:05 UTC | May 2, 17:00 UTC | 55m |
| 2026-05-02 | SBI5065 | OVB → KGD | May 2, 06:25 UTC | May 2, 13:40 UTC | 7h 15m |
| 2026-05-01 | SBI5065 | OVB → KGD | May 1, 18:25 UTC | May 2, 13:40 UTC | 19h 16m |
| 2026-05-01 | SBI6262 | BKK → VVO | May 1, 13:45 UTC | May 2, 13:30 UTC | 23h 45m |
| 2026-04-30 | SBI6261 | VVO → BKK | Apr 30, 19:25 UTC | May 1, 12:10 UTC | 16h 45m |
| 2026-04-30 | SBI5106 | AER → OVB | Apr 30, 14:00 UTC | Apr 30, 14:20 UTC | 20m |
| 2026-04-29 | SBI5265 | OVB → GDX | Apr 29, 18:10 UTC | Apr 29, 18:40 UTC | 30m |
| 2026-04-29 | SBI5726 | PKX → OVB | Apr 29, 04:20 UTC | Apr 29, 05:09 UTC | 50m |
| 2026-04-29 | SBI5726 | PKX → OVB | Apr 29, 01:05 UTC | Apr 29, 01:15 UTC | 10m |
| 2026-04-28 | SBI5725 | - | Apr 28, 23:05 UTC | Apr 28, 23:20 UTC | 15m |
| 2026-04-28 | SBI5725 | - | Apr 28, 19:45 UTC | Apr 28, 20:20 UTC | 35m |
| 2026-04-27 | SBI5250 | PKC → OVB | Apr 27, 16:30 UTC | Apr 28, 05:50 UTC | 13h 20m |
| 2026-04-27 | SBI5066 | KGD → OVB | Apr 27, 07:15 UTC | Apr 27, 10:10 UTC | 2h 55m |
| 2026-04-26 | SBI5065 | OVB → KGD | Apr 26, 13:20 UTC | Apr 27, 05:00 UTC | 15h 40m |
| 2026-04-26 | SBI5065 | OVB → KGD | Apr 26, 08:10 UTC | Apr 27, 05:00 UTC | 20h 50m |
| 2026-04-25 | SBI5561 | OVB → FEG | Apr 25, 16:30 UTC | Apr 26, 13:40 UTC | 21h 10m |
| 2026-04-25 | SBI5226 | IKT → OVB | Apr 25, 12:00 UTC | Apr 25, 13:55 UTC | 1h 55m |
| 2026-04-25 | SBI5225 | OVB → IKT | Apr 25, 10:40 UTC | Apr 25, 10:50 UTC | 10m |
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-73670 page for operator, model, and routing details .