sensors Mode-S transponder
151EC2
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73410 · BOEING 737-800
- Hex
- 151EC2
- Octal
- 05217302
- Decimal
- 1,384,130
- Country
- RU
- Tail
- RA-73410
- Type
- B738
- Flights observed
- 175
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- 2h ago
Last known position
Country allocation
The ICAO 24-bit address 151EC2 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 |
|---|---|---|---|
| SBI6311 | - | 9 | 2026-07-12 |
| SBI5732 | - | 9 | 2026-06-24 |
| SBI6409 | - | 6 | 2026-06-12 |
| SBI5725 | S7 Airlines (Siberia Airlines) | 6 | 2026-06-25 |
| SBI5066 | - | 6 | 2026-07-02 |
| SBI6309 | - | 5 | 2026-07-11 |
| SBI5864 | - | 5 | 2026-06-25 |
| SBI5863 | - | 5 | 2026-06-25 |
| SBI5250 | S7 Airlines (Siberia Airlines) | 5 | 2026-05-13 |
| SBI5204 | S7 Airlines (Siberia Airlines) | 5 | 2026-06-02 |
| SBI6419 | - | 4 | 2026-07-14 |
| SBI6415 | - | 4 | 2026-07-11 |
| SBI6327 | S7 Airlines (Siberia Airlines) | 4 | 2026-06-12 |
| SBI6310 | - | 4 | 2026-07-11 |
| SBI5726 | - | 4 | 2026-06-26 |
| SBI5211 | S7 Airlines (Siberia Airlines) | 4 | 2026-06-17 |
| SBI6410 | S7 Airlines (Siberia Airlines) | 3 | 2026-06-13 |
| SBI6312 | S7 Airlines (Siberia Airlines) | 3 | 2026-05-05 |
| SBI5889 | - | 3 | 2026-07-05 |
| SBI5542 | S7 Airlines (Siberia Airlines) | 3 | 2026-05-14 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | SBI6419 | - | Jul 14, 05:50 UTC | Jul 14, 18:05 UTC | 12h 15m |
| 2026-07-13 | SBI6419 | - | Jul 13, 12:35 UTC | Jul 14, 12:30 UTC | 23h 55m |
| 2026-07-13 | SBI6419 | - | Jul 13, 11:55 UTC | Jul 14, 06:35 UTC | 18h 40m |
| 2026-07-12 | SBI6419 | - | Jul 12, 21:35 UTC | Jul 13, 12:35 UTC | 15h 0m |
| 2026-07-12 | SBI6311 | - | Jul 12, 19:15 UTC | Jul 12, 19:25 UTC | 10m |
| 2026-07-11 | SBI6415 | - | Jul 11, 23:45 UTC | Jul 12, 11:15 UTC | 11h 30m |
| 2026-07-11 | SBI6311 | - | Jul 11, 19:55 UTC | Jul 11, 20:05 UTC | 10m |
| 2026-07-11 | SBI6310 | - | Jul 11, 11:10 UTC | Jul 11, 11:25 UTC | 15m |
| 2026-07-11 | SBI6310 | - | Jul 11, 10:05 UTC | Jul 11, 10:15 UTC | 10m |
| 2026-07-11 | SBI6309 | - | Jul 11, 08:05 UTC | Jul 11, 08:20 UTC | 15m |
| 2026-07-10 | SBI6309 | - | Jul 10, 22:00 UTC | Jul 11, 07:15 UTC | 9h 15m |
| 2026-07-10 | SBI6311 | - | Jul 10, 19:50 UTC | Jul 10, 20:00 UTC | 10m |
| 2026-07-09 | SBI6310 | - | Jul 9, 15:15 UTC | Jul 9, 15:45 UTC | 30m |
| 2026-07-08 | SBI6309 | - | Jul 8, 21:35 UTC | Jul 9, 11:20 UTC | 13h 45m |
| 2026-07-08 | SBI6309 | - | Jul 8, 16:05 UTC | Jul 9, 11:20 UTC | 19h 15m |
| 2026-07-08 | SBI6415 | - | Jul 8, 04:35 UTC | Jul 8, 21:55 UTC | 17h 20m |
| 2026-07-07 | SBI6415 | - | Jul 7, 22:00 UTC | Jul 8, 16:20 UTC | 18h 20m |
| 2026-07-07 | SBI6311 | - | Jul 7, 19:45 UTC | Jul 7, 19:55 UTC | 10m |
| 2026-07-07 | SBI6414 | - | Jul 7, 08:40 UTC | Jul 7, 14:40 UTC | 6h 0m |
| 2026-07-06 | SBI6413 | - | Jul 6, 11:30 UTC | Jul 7, 09:20 UTC | 21h 50m |
| 2026-07-06 | SBI5891 | OVB → IST | Jul 6, 09:25 UTC | Jul 6, 09:35 UTC | 10m |
| 2026-07-05 | SBI5889 | - | Jul 5, 08:30 UTC | Jul 5, 08:55 UTC | 25m |
| 2026-07-04 | SBI5239 | OVB → IKT | Jul 4, 14:50 UTC | Jul 4, 15:25 UTC | 35m |
| 2026-07-03 | SBI5242 | - | Jul 3, 22:15 UTC | Jul 4, 04:55 UTC | 6h 40m |
| 2026-07-03 | SBI5890 | - | Jul 3, 12:40 UTC | Jul 3, 13:10 UTC | 30m |
| 2026-07-03 | SBI5889 | - | Jul 3, 10:10 UTC | Jul 3, 10:35 UTC | 25m |
| 2026-07-02 | SBI5206 | - | Jul 2, 14:05 UTC | Jul 3, 02:00 UTC | 11h 55m |
| 2026-07-02 | SBI5066 | - | Jul 2, 07:40 UTC | Jul 2, 08:35 UTC | 55m |
| 2026-07-01 | SBI5234 | IKT → OVB | Jul 1, 09:25 UTC | Jul 1, 10:05 UTC | 40m |
| 2026-06-30 | SBI6306 | BKK → IKT | Jun 30, 09:05 UTC | Jun 30, 10:25 UTC | 1h 20m |
| 2026-06-29 | SBI6305 | - | Jun 29, 15:45 UTC | Jun 30, 07:10 UTC | 15h 26m |
| 2026-06-29 | SBI6318 | - | Jun 29, 04:55 UTC | Jun 29, 20:59 UTC | 16h 5m |
| 2026-06-28 | SBI6310 | - | Jun 28, 14:14 UTC | Jun 29, 03:25 UTC | 13h 10m |
| 2026-06-28 | SBI6309 | - | Jun 28, 11:19 UTC | Jun 28, 12:50 UTC | 1h 30m |
| 2026-06-26 | SBI5726 | - | Jun 26, 00:55 UTC | Jun 26, 17:19 UTC | 16h 25m |
| 2026-06-25 | SBI5725 | OVB → PKX | Jun 25, 22:45 UTC | Jun 25, 22:59 UTC | 15m |
| 2026-06-25 | SBI5864 | - | Jun 25, 11:30 UTC | Jun 25, 19:59 UTC | 8h 30m |
| 2026-06-25 | SBI5863 | - | Jun 25, 08:40 UTC | Jun 25, 10:09 UTC | 1h 30m |
| 2026-06-24 | SBI5732 | - | Jun 24, 14:04 UTC | Jun 25, 02:10 UTC | 12h 5m |
| 2026-06-24 | SBI5307 | - | Jun 24, 09:05 UTC | Jun 24, 11:39 UTC | 2h 35m |
| 2026-06-23 | SBI5208 | - | Jun 23, 19:34 UTC | Jun 24, 06:59 UTC | 11h 25m |
| 2026-06-22 | SBI5283 | OVB → PWE | Jun 22, 21:54 UTC | Jun 23, 10:49 UTC | 12h 55m |
| 2026-06-22 | SBI5864 | - | Jun 22, 11:30 UTC | Jun 22, 13:14 UTC | 1h 45m |
| 2026-06-21 | SBI8991 | OVB → OVB | Jun 21, 22:44 UTC | Jun 22, 10:00 UTC | 11h 15m |
| 2026-06-17 | SBI5211 | OVB → BQS | Jun 17, 21:15 UTC | Jun 18, 06:10 UTC | 8h 55m |
| 2026-06-16 | SBI5725 | OVB → PKX | Jun 16, 19:19 UTC | Jun 16, 19:55 UTC | 36m |
| 2026-06-16 | SBI5066 | - | Jun 16, 02:34 UTC | Jun 16, 08:44 UTC | 6h 10m |
| 2026-06-15 | SBI5232 | IKT → OVB | Jun 15, 02:50 UTC | Jun 15, 03:24 UTC | 35m |
| 2026-06-13 | SBI6410 | LED → IKT | Jun 13, 09:55 UTC | Jun 13, 10:10 UTC | 15m |
| 2026-06-12 | SBI6409 | - | Jun 12, 21:40 UTC | Jun 13, 06:45 UTC | 9h 4m |
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-73410 page for operator, model, and routing details .