sensors Mode-S transponder
151FC3
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73667 · BOEING 737-800
- Hex
- 151FC3
- Octal
- 05217703
- Decimal
- 1,384,387
- Country
- RU
- Tail
- RA-73667
- Type
- B738
- Flights observed
- 98
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- 1h ago
Last known position
Country allocation
The ICAO 24-bit address 151FC3 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 | SBI5045 | OVB → UFA | May 30, 07:35 UTC | May 30, 07:45 UTC | 10m |
| 2026-05-29 | SBI5264 | YKS → OVB | May 29, 18:25 UTC | May 30, 02:40 UTC | 8h 15m |
| 2026-05-28 | SBI6416 | SVX → IKT | May 28, 12:45 UTC | May 29, 03:40 UTC | 14h 55m |
| 2026-05-27 | SBI6415 | IKT → SVX | May 27, 12:50 UTC | May 28, 07:45 UTC | 18h 55m |
| 2026-05-27 | SBI6328 | OSS → IKT | May 27, 11:45 UTC | May 28, 07:45 UTC | 20h 0m |
| 2026-05-27 | SBI6327 | IKT → OSS | May 27, 06:25 UTC | May 27, 13:00 UTC | 6h 36m |
| 2026-05-26 | SBI6320 | CAN → IKT | May 26, 22:29 UTC | May 26, 22:44 UTC | 15m |
| 2026-05-25 | SRI6409 | - | May 25, 03:40 UTC | May 25, 13:45 UTC | 10h 5m |
| 2026-05-22 | SBI6419 | IKT → UFA | May 22, 19:35 UTC | May 23, 12:45 UTC | 17h 9m |
| 2026-05-21 | SBI6416 | SVX → IKT | May 21, 12:40 UTC | May 21, 13:30 UTC | 50m |
| 2026-05-20 | SBI6415 | IKT → SVX | May 20, 12:50 UTC | May 21, 07:40 UTC | 18h 50m |
| 2026-05-20 | SBI6415 | IKT → SVX | May 20, 12:40 UTC | May 21, 07:40 UTC | 19h 0m |
| 2026-05-20 | SBI6327 | IKT → OSS | May 20, 06:30 UTC | May 20, 12:55 UTC | 6h 25m |
| 2026-05-18 | SBI6326 | PVG → IKT | May 18, 15:40 UTC | May 18, 21:00 UTC | 5h 19m |
| 2026-05-17 | SBI5229 | OVB → IKT | May 17, 22:15 UTC | May 18, 20:45 UTC | 22h 29m |
| 2026-05-17 | SBI5208 | VVO → OVB | May 17, 06:20 UTC | May 17, 22:35 UTC | 16h 15m |
| 2026-05-16 | SBI5208 | VVO → OVB | May 16, 11:11 UTC | May 17, 10:45 UTC | 23h 35m |
| 2026-05-16 | SBI5889 | OVB → IST | May 16, 06:16 UTC | May 16, 07:55 UTC | 1h 40m |
| 2026-05-15 | SBI5889 | OVB → IST | May 15, 10:50 UTC | May 16, 07:55 UTC | 21h 5m |
| 2026-05-15 | SBI5889 | OVB → IST | May 15, 10:10 UTC | May 16, 07:55 UTC | 21h 45m |
| 2026-05-14 | SBI5204 | VVO → OVB | May 14, 16:35 UTC | May 15, 04:50 UTC | 12h 15m |
| 2026-05-13 | SBI5864 | AYT → OVB | May 13, 12:30 UTC | May 13, 15:00 UTC | 2h 30m |
| 2026-05-13 | - | - | May 13, 11:00 UTC | May 13, 11:15 UTC | 15m |
| 2026-05-13 | SBI5863 | OVB → AYT | May 13, 03:00 UTC | May 13, 10:15 UTC | 7h 15m |
| 2026-05-13 | SBI5232 | IKT → OVB | May 13, 01:30 UTC | May 13, 01:40 UTC | 10m |
| 2026-05-12 | SBI6401 | KJA → BTK | May 12, 17:05 UTC | May 12, 17:20 UTC | 15m |
| 2026-05-12 | SBI6409 | IKT → LED | May 12, 05:45 UTC | May 12, 13:40 UTC | 7h 55m |
| 2026-05-11 | SBI6409 | IKT → LED | May 11, 17:10 UTC | May 12, 13:40 UTC | 20h 30m |
| 2026-05-11 | SBI6318 | OSS → IKT | May 11, 05:05 UTC | May 11, 10:45 UTC | 5h 40m |
| 2026-05-11 | SBI6317 | IKT → OSS | May 11, 02:30 UTC | May 11, 03:35 UTC | 1h 5m |
| 2026-05-10 | SBI6310 | BKK → IKT | May 10, 14:20 UTC | May 10, 20:05 UTC | 5h 45m |
| 2026-05-10 | SBI6309 | IKT → BKK | May 10, 11:45 UTC | May 10, 12:49 UTC | 1h 5m |
| 2026-05-10 | SBI6309 | IKT → BKK | May 10, 06:59 UTC | May 10, 07:25 UTC | 25m |
| 2026-05-09 | SBI6312 | PKX → IKT | May 9, 22:00 UTC | May 10, 00:34 UTC | 2h 35m |
| 2026-05-09 | SBI6311 | IKT → PKX | May 9, 19:45 UTC | May 9, 20:00 UTC | 15m |
| 2026-05-09 | SBI6409 | IKT → LED | May 9, 02:10 UTC | May 9, 07:35 UTC | 5h 25m |
| 2026-05-08 | SBI5864 | AYT → OVB | May 8, 11:30 UTC | May 8, 22:30 UTC | 11h 0m |
| 2026-05-08 | SBI5863 | OVB → AYT | May 8, 09:34 UTC | May 8, 09:49 UTC | 15m |
| 2026-05-08 | SBI5863 | OVB → AYT | May 8, 07:39 UTC | May 8, 08:34 UTC | 55m |
| 2026-05-07 | SBI5256 | UUD → OVB | May 7, 04:55 UTC | May 7, 05:30 UTC | 35m |
| 2026-05-07 | SBI5256 | UUD → OVB | May 7, 03:35 UTC | May 7, 03:45 UTC | 10m |
| 2026-05-06 | SBI6326 | PVG → IKT | May 6, 15:55 UTC | May 6, 23:05 UTC | 7h 9m |
| 2026-05-06 | SBI6325 | IKT → PVG | May 6, 14:00 UTC | May 6, 14:15 UTC | 15m |
| 2026-05-06 | SBI5229 | OVB → IKT | May 6, 00:31 UTC | May 6, 01:05 UTC | 35m |
| 2026-05-05 | SBI2510 | OVB → DME | May 5, 13:25 UTC | May 5, 16:10 UTC | 2h 45m |
| 2026-05-04 | SBI5284 | PWE → OVB | May 4, 21:55 UTC | May 5, 11:35 UTC | 13h 40m |
| 2026-05-04 | SBI5892 | IST → OVB | May 4, 12:55 UTC | May 5, 11:35 UTC | 22h 41m |
| 2026-05-04 | SBI5892 | IST → OVB | May 4, 12:00 UTC | May 4, 22:20 UTC | 10h 21m |
| 2026-05-03 | SBI5891 | OVB → IST | May 3, 13:40 UTC | May 4, 08:45 UTC | 19h 5m |
| 2026-05-03 | SBI5891 | OVB → IST | May 3, 08:50 UTC | May 4, 08:45 UTC | 23h 55m |
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-73667 page for operator, model, and routing details .