sensors Mode-S transponder
151EC4
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73412 · BOEING 737-800
- Hex
- 151EC4
- Octal
- 05217304
- Decimal
- 1,384,132
- Country
- RU
- Tail
- RA-73412
- Type
- B738
- Flights observed
- 204
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- 36m ago
Last known position
Country allocation
The ICAO 24-bit address 151EC4 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 |
|---|---|---|---|
| SBI6419 | S7 Airlines (Siberia Airlines) | 24 | 2026-06-06 |
| SBI6327 | S7 Airlines (Siberia Airlines) | 12 | 2026-06-17 |
| SBI6415 | - | 11 | 2026-06-18 |
| SBI6420 | S7 Airlines (Siberia Airlines) | 10 | 2026-06-16 |
| SBI6328 | S7 Airlines (Siberia Airlines) | 10 | 2026-07-08 |
| SBI6311 | - | 8 | 2026-07-08 |
| SBI6309 | - | 6 | 2026-07-05 |
| SBI5863 | - | 6 | 2026-07-03 |
| SBI5066 | - | 6 | 2026-06-23 |
| SBI6416 | S7 Airlines (Siberia Airlines) | 5 | 2026-06-18 |
| SBI6409 | - | 4 | 2026-07-10 |
| SBI6312 | S7 Airlines (Siberia Airlines) | 4 | 2026-04-26 |
| SBI5864 | - | 4 | 2026-07-03 |
| SBI5565 | - | 4 | 2026-07-04 |
| SBI5232 | S7 Airlines (Siberia Airlines) | 4 | 2026-06-08 |
| SBI6403 | S7 Airlines (Siberia Airlines) | 3 | 2026-05-11 |
| SBI6320 | S7 Airlines (Siberia Airlines) | 3 | 2026-05-13 |
| SBI6310 | S7 Airlines (Siberia Airlines) | 3 | 2026-06-04 |
| SBI5889 | - | 3 | 2026-07-02 |
| SBI5725 | S7 Airlines (Siberia Airlines) | 3 | 2026-06-30 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | SBI6204 | UUS → VVO | Jul 14, 01:00 UTC | Jul 14, 06:40 UTC | 5h 40m |
| 2026-07-13 | SBI6201 | - | Jul 13, 05:55 UTC | Jul 13, 23:25 UTC | 17h 30m |
| 2026-07-13 | SBI6201 | - | Jul 13, 00:50 UTC | Jul 13, 08:25 UTC | 7h 35m |
| 2026-07-10 | SBI6409 | - | Jul 10, 14:00 UTC | Jul 11, 07:15 UTC | 17h 15m |
| 2026-07-09 | SBI6410 | - | Jul 9, 13:15 UTC | Jul 9, 13:55 UTC | 40m |
| 2026-07-08 | SBI6409 | - | Jul 8, 21:45 UTC | Jul 9, 07:30 UTC | 9h 45m |
| 2026-07-08 | SBI6311 | - | Jul 8, 19:35 UTC | Jul 8, 19:50 UTC | 15m |
| 2026-07-08 | SBI6328 | OSS → IKT | Jul 8, 06:55 UTC | Jul 8, 13:15 UTC | 6h 20m |
| 2026-07-07 | SBI6328 | OSS → IKT | Jul 7, 18:35 UTC | Jul 8, 13:15 UTC | 18h 40m |
| 2026-07-07 | SBI6306 | BKK → IKT | Jul 7, 09:05 UTC | Jul 8, 07:55 UTC | 22h 50m |
| 2026-07-07 | SBI6306 | BKK → IKT | Jul 7, 08:50 UTC | Jul 8, 07:00 UTC | 22h 10m |
| 2026-07-06 | SBI6305 | - | Jul 6, 15:40 UTC | Jul 7, 07:05 UTC | 15h 25m |
| 2026-07-06 | SBI6318 | - | Jul 6, 05:10 UTC | Jul 6, 21:00 UTC | 15h 50m |
| 2026-07-05 | SBI6317 | - | Jul 5, 14:15 UTC | Jul 6, 03:20 UTC | 13h 5m |
| 2026-07-05 | SBI6309 | - | Jul 5, 12:00 UTC | Jul 5, 12:45 UTC | 45m |
| 2026-07-04 | SBI6309 | - | Jul 4, 15:25 UTC | Jul 5, 12:45 UTC | 21h 20m |
| 2026-07-04 | SBI5565 | - | Jul 4, 07:40 UTC | Jul 4, 13:30 UTC | 5h 50m |
| 2026-07-03 | SB5212 | - | Jul 3, 19:50 UTC | Jul 4, 04:55 UTC | 9h 5m |
| 2026-07-03 | SBI5864 | - | Jul 3, 11:15 UTC | Jul 3, 13:00 UTC | 1h 45m |
| 2026-07-03 | SBI5863 | - | Jul 3, 09:30 UTC | Jul 3, 10:00 UTC | 30m |
| 2026-07-02 | SBI5246 | - | Jul 2, 18:10 UTC | Jul 3, 02:25 UTC | 8h 15m |
| 2026-07-02 | SBI5890 | - | Jul 2, 11:10 UTC | Jul 2, 11:35 UTC | 25m |
| 2026-07-02 | SBI5889 | - | Jul 2, 08:50 UTC | Jul 2, 09:10 UTC | 20m |
| 2026-07-01 | SBI5240 | - | Jul 1, 14:50 UTC | Jul 2, 01:20 UTC | 10h 30m |
| 2026-07-01 | SBI5555 | - | Jul 1, 07:05 UTC | Jul 1, 12:35 UTC | 5h 30m |
| 2026-07-01 | SBI5726 | - | Jul 1, 01:00 UTC | Jul 1, 04:55 UTC | 3h 55m |
| 2026-06-30 | SBI5725 | OVB → PKX | Jun 30, 23:00 UTC | Jun 30, 23:10 UTC | 10m |
| 2026-06-30 | SBI5725 | OVB → PKX | Jun 30, 19:25 UTC | Jun 30, 20:05 UTC | 40m |
| 2026-06-30 | SBI5890 | - | Jun 30, 11:15 UTC | Jun 30, 11:40 UTC | 25m |
| 2026-06-30 | SBI5889 | - | Jun 30, 08:55 UTC | Jun 30, 09:25 UTC | 30m |
| 2026-06-29 | SBI5254 | UUD → OVB | Jun 29, 19:44 UTC | Jun 30, 01:25 UTC | 5h 40m |
| 2026-06-29 | SBI5864 | - | Jun 29, 11:20 UTC | Jun 29, 13:04 UTC | 1h 45m |
| 2026-06-29 | SBI5863 | - | Jun 29, 08:35 UTC | Jun 29, 10:04 UTC | 1h 30m |
| 2026-06-28 | SBI5223 | OVB → HTA | Jun 28, 18:55 UTC | Jun 29, 01:50 UTC | 6h 55m |
| 2026-06-27 | SBI5250 | - | Jun 27, 16:24 UTC | Jun 28, 05:55 UTC | 13h 30m |
| 2026-06-26 | SBI5263 | OVB → YKS | Jun 26, 11:00 UTC | Jun 27, 02:55 UTC | 15h 55m |
| 2026-06-26 | SBI5889 | - | Jun 26, 08:45 UTC | Jun 26, 09:14 UTC | 30m |
| 2026-06-25 | SBI5240 | - | Jun 25, 14:59 UTC | Jun 26, 01:10 UTC | 10h 10m |
| 2026-06-24 | SBI5864 | - | Jun 24, 11:14 UTC | Jun 24, 13:50 UTC | 2h 35m |
| 2026-06-23 | SBI5863 | - | Jun 23, 15:04 UTC | Jun 24, 09:45 UTC | 18h 40m |
| 2026-06-23 | SBI5863 | - | Jun 23, 14:49 UTC | Jun 24, 09:45 UTC | 18h 55m |
| 2026-06-23 | SBI5066 | - | Jun 23, 07:29 UTC | Jun 24, 06:59 UTC | 23h 30m |
| 2026-06-21 | SBI5732 | PVG → OVB | Jun 21, 14:10 UTC | Jun 22, 02:14 UTC | 12h 5m |
| 2026-06-20 | SBI5204 | - | Jun 20, 04:04 UTC | Jun 20, 13:49 UTC | 9h 45m |
| 2026-06-19 | SBI5204 | - | Jun 19, 17:24 UTC | Jun 20, 13:49 UTC | 20h 25m |
| 2026-06-19 | SBI5002 | LED → OVB | Jun 19, 11:39 UTC | Jun 19, 12:04 UTC | 25m |
| 2026-06-18 | SBI6416 | SVX → IKT | Jun 18, 13:00 UTC | Jun 19, 03:34 UTC | 14h 34m |
| 2026-06-18 | SBI6416 | SVX → IKT | Jun 18, 07:05 UTC | Jun 19, 03:34 UTC | 20h 29m |
| 2026-06-18 | SBI6415 | - | Jun 18, 06:55 UTC | Jun 19, 03:34 UTC | 20h 39m |
| 2026-06-17 | SBI6415 | - | Jun 17, 13:05 UTC | Jun 18, 13:00 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-73412 page for operator, model, and routing details .