sensors Mode-S transponder
151EC3
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73411 · BOEING 737-800
- Hex
- 151EC3
- Octal
- 05217303
- Decimal
- 1,384,131
- Country
- RU
- Tail
- RA-73411
- Type
- B738
- Flights observed
- 62
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- 7d ago
Last known position
Country allocation
The ICAO 24-bit address 151EC3 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-22 | SBI5265 | OVB → GDX | May 22, 14:30 UTC | May 23, 01:45 UTC | 11h 15m |
| 2026-05-22 | SBI5308 | KJA → OVB | May 22, 07:10 UTC | May 22, 09:35 UTC | 2h 25m |
| 2026-05-21 | SBI6420 | UFA → IKT | May 21, 12:00 UTC | May 22, 03:20 UTC | 15h 20m |
| 2026-05-21 | SBI6419 | IKT → UFA | May 21, 05:40 UTC | May 22, 03:20 UTC | 21h 40m |
| 2026-05-20 | SBI6419 | IKT → UFA | May 20, 21:50 UTC | May 21, 12:40 UTC | 14h 50m |
| 2026-05-20 | SBI6410 | LED → IKT | May 20, 06:05 UTC | May 20, 19:50 UTC | 13h 45m |
| 2026-05-19 | SBI6410 | LED → IKT | May 19, 21:55 UTC | May 20, 19:50 UTC | 21h 56m |
| 2026-05-19 | SBI6311 | IKT → PKX | May 19, 19:55 UTC | May 19, 20:10 UTC | 15m |
| 2026-05-17 | SBI6420 | UFA → IKT | May 17, 21:45 UTC | May 18, 12:35 UTC | 14h 50m |
| 2026-05-13 | SBI6326 | PVG → IKT | May 13, 13:55 UTC | May 13, 22:50 UTC | 8h 55m |
| 2026-05-12 | SBI5235 | OVB → IKT | May 12, 16:20 UTC | May 12, 16:35 UTC | 15m |
| 2026-05-12 | SBI5284 | PWE → OVB | May 12, 10:30 UTC | May 12, 15:20 UTC | 4h 50m |
| 2026-05-11 | SBI5284 | PWE → OVB | May 11, 12:50 UTC | May 12, 11:05 UTC | 22h 16m |
| 2026-05-10 | SBI5889 | OVB → IST | May 10, 06:30 UTC | May 10, 08:30 UTC | 2h 0m |
| 2026-05-09 | SBI5889 | OVB → IST | May 9, 10:50 UTC | May 10, 08:30 UTC | 21h 40m |
| 2026-05-09 | SBI5105 | OVB → AER | May 9, 03:40 UTC | May 9, 11:30 UTC | 7h 50m |
| 2026-05-08 | SBI5105 | OVB → AER | May 8, 12:49 UTC | May 9, 11:30 UTC | 22h 40m |
| 2026-05-08 | SBI5258 | UUS → OVB | May 8, 12:39 UTC | May 9, 10:45 UTC | 22h 5m |
| 2026-05-08 | SBI5258 | UUS → OVB | May 8, 07:55 UTC | May 9, 04:10 UTC | 20h 15m |
| 2026-05-08 | SBI5204 | VVO → OVB | May 8, 04:04 UTC | May 8, 13:05 UTC | 9h 0m |
| 2026-05-07 | SBI5204 | VVO → OVB | May 7, 13:35 UTC | May 8, 12:44 UTC | 23h 9m |
| 2026-05-06 | SBI5864 | AYT → OVB | May 6, 12:55 UTC | May 7, 07:55 UTC | 19h 0m |
| 2026-05-06 | SBI5864 | AYT → OVB | May 6, 12:01 UTC | May 7, 07:55 UTC | 19h 54m |
| 2026-05-06 | SBI5863 | OVB → AYT | May 6, 10:15 UTC | May 6, 10:40 UTC | 25m |
| 2026-05-06 | SBI5863 | OVB → AYT | May 6, 09:00 UTC | May 6, 09:30 UTC | 30m |
| 2026-05-04 | SBI5728 | XIY → OVB | May 4, 16:55 UTC | May 5, 02:40 UTC | 9h 46m |
| 2026-05-04 | SBI5566 | TAS → OVB | May 4, 07:55 UTC | May 4, 13:30 UTC | 5h 35m |
| 2026-05-03 | SBI5204 | VVO → OVB | May 3, 16:20 UTC | May 4, 04:24 UTC | 12h 5m |
| 2026-05-02 | SBI5204 | VVO → OVB | May 2, 19:10 UTC | May 3, 04:40 UTC | 9h 29m |
| 2026-05-01 | SBI6245 | VVO → PVG | May 1, 18:55 UTC | May 2, 00:35 UTC | 5h 40m |
| 2026-04-29 | SBI6245 | VVO → PVG | Apr 29, 18:45 UTC | Apr 30, 00:30 UTC | 5h 44m |
| 2026-04-27 | SBI6242 | PKX → VVO | Apr 27, 19:10 UTC | Apr 27, 19:20 UTC | 10m |
| 2026-04-26 | SBI6245 | VVO → PVG | Apr 26, 19:10 UTC | Apr 27, 00:45 UTC | 5h 35m |
| 2026-04-25 | SBI5207 | OVB → VVO | Apr 25, 18:55 UTC | Apr 25, 19:25 UTC | 30m |
| 2026-04-25 | SBI5115 | OVB → KRR | Apr 25, 08:00 UTC | Apr 25, 08:55 UTC | 55m |
| 2026-04-24 | SBI5728 | XIY → OVB | Apr 24, 16:55 UTC | Apr 25, 02:45 UTC | 9h 50m |
| 2026-04-24 | SBI5575 | OVB → AZN | Apr 24, 07:30 UTC | Apr 24, 12:50 UTC | 5h 20m |
| 2026-04-23 | SRI5242 | - | Apr 23, 21:15 UTC | Apr 24, 04:15 UTC | 7h 0m |
| 2026-04-22 | SBI5212 | BQS → OVB | Apr 22, 19:45 UTC | Apr 23, 05:05 UTC | 9h 20m |
| 2026-04-21 | SBI2510 | OVB → DME | Apr 21, 10:30 UTC | Apr 21, 13:25 UTC | 2h 55m |
| 2026-04-20 | SBI5232 | IKT → OVB | Apr 20, 01:40 UTC | Apr 20, 03:45 UTC | 2h 5m |
| 2026-04-19 | SBI6415 | IKT → SVX | Apr 19, 06:30 UTC | Apr 19, 12:35 UTC | 6h 5m |
| 2026-04-18 | SBI6319 | - | Apr 18, 15:45 UTC | Apr 19, 02:40 UTC | 10h 55m |
| 2026-04-17 | SBI6332 | - | Apr 17, 19:35 UTC | Apr 17, 19:50 UTC | 15m |
| 2026-04-17 | SBI6331 | - | Apr 17, 14:00 UTC | Apr 17, 15:15 UTC | 1h 15m |
| 2026-04-17 | SBI6318 | OSS → IKT | Apr 17, 09:55 UTC | Apr 17, 10:15 UTC | 20m |
| 2026-04-17 | SBI6318 | OSS → IKT | Apr 17, 04:40 UTC | Apr 17, 04:55 UTC | 15m |
| 2026-04-17 | SBI6317 | IKT → OSS | Apr 17, 02:40 UTC | Apr 17, 03:05 UTC | 25m |
| 2026-04-16 | SBI6310 | - | Apr 16, 15:30 UTC | Apr 16, 16:05 UTC | 35m |
| 2026-04-16 | SBI6310 | - | Apr 16, 10:14 UTC | Apr 16, 10:40 UTC | 25m |
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-73411 page for operator, model, and routing details .