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
- 140
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- Jul 25, 19:20 UTC
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
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| SBI6245 | - | 9 | 2026-07-24 |
| SBI5204 | - | 8 | 2026-07-07 |
| SBI6419 | S7 Airlines (Siberia Airlines) | 7 | 2026-06-11 |
| SBI5889 | - | 7 | 2026-07-19 |
| SBI6318 | - | 5 | 2026-07-10 |
| SBI5863 | S7 Airlines (Siberia Airlines) | 5 | 2026-06-19 |
| SBI6410 | S7 Airlines (Siberia Airlines) | 4 | 2026-05-20 |
| SBI5864 | S7 Airlines (Siberia Airlines) | 4 | 2026-06-19 |
| SBI6415 | S7 Airlines (Siberia Airlines) | 3 | 2026-06-10 |
| SBI6409 | S7 Airlines (Siberia Airlines) | 3 | 2026-04-15 |
| SBI6310 | S7 Airlines (Siberia Airlines) | 3 | 2026-06-07 |
| SBI6309 | S7 Airlines (Siberia Airlines) | 3 | 2026-06-07 |
| SBI5250 | - | 3 | 2026-07-01 |
| SBI5246 | - | 3 | 2026-07-21 |
| SBI5232 | - | 3 | 2026-07-12 |
| SBI5212 | - | 3 | 2026-06-14 |
| SBI5207 | S7 Airlines (Siberia Airlines) | 3 | 2026-06-19 |
| SBI5010 | - | 3 | 2026-07-04 |
| SBI2510 | S7 Airlines (Siberia Airlines) | 3 | 2026-06-04 |
| SBI6420 | S7 Airlines (Siberia Airlines) | 2 | 2026-05-21 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-25 | SBI6242 | PKX → VVO | Jul 25, 19:10 UTC | Jul 25, 19:20 UTC | 10m |
| 2026-07-25 | SBI6241 | VVO → PKX | Jul 25, 17:00 UTC | Jul 25, 17:10 UTC | 10m |
| 2026-07-24 | SBI6245 | - | Jul 24, 18:30 UTC | Jul 25, 07:00 UTC | 12h 30m |
| 2026-07-24 | SBI6245 | - | Jul 24, 06:25 UTC | Jul 25, 00:00 UTC | 17h 35m |
| 2026-07-23 | SBI6202 | UUS → VVO | Jul 23, 06:50 UTC | Jul 24, 06:30 UTC | 23h 40m |
| 2026-07-22 | SBI6245 | - | Jul 22, 18:55 UTC | Jul 23, 06:50 UTC | 11h 55m |
| 2026-07-21 | SBI5246 | - | Jul 21, 01:50 UTC | Jul 21, 17:05 UTC | 15h 15m |
| 2026-07-20 | SBI5246 | - | Jul 20, 18:20 UTC | Jul 21, 16:45 UTC | 22h 24m |
| 2026-07-20 | SBI5246 | - | Jul 20, 11:55 UTC | Jul 21, 08:10 UTC | 20h 14m |
| 2026-07-19 | SBI5264 | YKS → OVB | Jul 19, 18:25 UTC | Jul 20, 02:35 UTC | 8h 10m |
| 2026-07-19 | SBI5890 | - | Jul 19, 11:05 UTC | Jul 19, 11:35 UTC | 30m |
| 2026-07-19 | SBI5889 | - | Jul 19, 09:15 UTC | Jul 19, 09:25 UTC | 10m |
| 2026-07-18 | SBI5239 | OVB → IKT | Jul 18, 10:40 UTC | Jul 18, 15:30 UTC | 4h 50m |
| 2026-07-17 | SBI8971 | - | Jul 17, 04:49 UTC | Jul 17, 05:35 UTC | 45m |
| 2026-07-12 | SBI5232 | - | Jul 12, 21:50 UTC | Jul 13, 03:30 UTC | 5h 40m |
| 2026-07-12 | SBI5066 | - | Jul 12, 07:31 UTC | Jul 13, 03:30 UTC | 20h 0m |
| 2026-07-11 | SBI5358 | TLK → OVB | Jul 11, 07:45 UTC | Jul 11, 08:10 UTC | 25m |
| 2026-07-10 | SBI6318 | - | Jul 10, 18:25 UTC | Jul 10, 18:40 UTC | 15m |
| 2026-07-10 | SBI6318 | - | Jul 10, 17:05 UTC | Jul 10, 17:25 UTC | 20m |
| 2026-07-09 | SBI6317 | - | Jul 9, 17:50 UTC | Jul 10, 07:15 UTC | 13h 25m |
| 2026-07-08 | SBI5240 | - | Jul 8, 17:10 UTC | Jul 9, 03:45 UTC | 10h 35m |
| 2026-07-08 | SBI5556 | LBD → OVB | Jul 8, 07:05 UTC | Jul 8, 12:50 UTC | 5h 45m |
| 2026-07-07 | SBI5204 | - | Jul 7, 16:25 UTC | Jul 8, 04:15 UTC | 11h 50m |
| 2026-07-07 | SBI5565 | - | Jul 7, 08:35 UTC | Jul 7, 14:20 UTC | 5h 45m |
| 2026-07-06 | SBI5066 | - | Jul 6, 11:00 UTC | Jul 7, 06:10 UTC | 19h 10m |
| 2026-07-06 | SBI5065 | - | Jul 6, 08:05 UTC | Jul 6, 08:45 UTC | 40m |
| 2026-07-05 | SBI5009 | - | Jul 5, 15:05 UTC | Jul 5, 15:35 UTC | 30m |
| 2026-07-04 | SBI5010 | - | Jul 4, 17:05 UTC | Jul 4, 17:20 UTC | 15m |
| 2026-07-03 | SBI5010 | - | Jul 3, 17:10 UTC | Jul 3, 17:35 UTC | 25m |
| 2026-07-03 | SBI5009 | - | Jul 3, 15:25 UTC | Jul 3, 15:35 UTC | 10m |
| 2026-07-02 | SBI5010 | - | Jul 2, 17:05 UTC | Jul 2, 17:20 UTC | 15m |
| 2026-07-01 | SBI5250 | - | Jul 1, 18:05 UTC | Jul 2, 07:15 UTC | 13h 10m |
| 2026-07-01 | SBI5890 | - | Jul 1, 10:55 UTC | Jul 2, 07:15 UTC | 20h 20m |
| 2026-07-01 | SBI5889 | - | Jul 1, 08:20 UTC | Jul 1, 08:45 UTC | 25m |
| 2026-06-30 | SBI5239 | OVB → IKT | Jun 30, 14:45 UTC | Jul 1, 01:05 UTC | 10h 20m |
| 2026-06-29 | SBI5204 | - | Jun 29, 16:25 UTC | Jun 30, 04:40 UTC | 12h 16m |
| 2026-06-28 | SBI5204 | - | Jun 28, 16:19 UTC | Jun 29, 04:34 UTC | 12h 15m |
| 2026-06-27 | SBI5204 | - | Jun 27, 19:15 UTC | Jun 28, 04:25 UTC | 9h 10m |
| 2026-06-27 | SBI6202 | - | Jun 27, 06:54 UTC | Jun 27, 06:59 UTC | 5m |
| 2026-06-26 | SBI6245 | VVO → PVG | Jun 26, 06:25 UTC | Jun 27, 00:14 UTC | 17h 50m |
| 2026-06-24 | SBI6245 | VVO → PVG | Jun 24, 19:00 UTC | Jun 25, 04:14 UTC | 9h 15m |
| 2026-06-24 | SBI6245 | VVO → PVG | Jun 24, 04:59 UTC | Jun 25, 04:14 UTC | 23h 15m |
| 2026-06-22 | SBI5203 | OVB → VVO | Jun 22, 16:29 UTC | Jun 23, 04:39 UTC | 12h 10m |
| 2026-06-22 | SBI5254 | UUD → OVB | Jun 22, 01:15 UTC | Jun 22, 01:49 UTC | 35m |
| 2026-06-21 | SBI5253 | OVB → UUD | Jun 21, 20:09 UTC | Jun 21, 20:24 UTC | 15m |
| 2026-06-20 | SBI1006 | LED → DME | Jun 20, 17:29 UTC | Jun 20, 17:49 UTC | 20m |
| 2026-06-19 | SBI5207 | OVB → VVO | Jun 19, 18:59 UTC | Jun 19, 19:29 UTC | 30m |
| 2026-06-19 | SBI5864 | AYT → OVB | Jun 19, 11:34 UTC | Jun 19, 13:14 UTC | 1h 40m |
| 2026-06-19 | SBI5863 | OVB → AYT | Jun 19, 07:59 UTC | Jun 19, 10:09 UTC | 2h 10m |
| 2026-06-18 | SBI8992 | OVB → IKT | Jun 18, 20:45 UTC | Jun 18, 21:20 UTC | 35m |
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 .