sensors Mode-S transponder
151ECE
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73422 · AIRBUS A-320
- Hex
- 151ECE
- Octal
- 05217316
- Decimal
- 1,384,142
- Country
- RU
- Tail
- RA-73422
- Type
- A320
- Flights observed
- 222
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- 1h ago
Last known position
Country allocation
The ICAO 24-bit address 151ECE 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 |
|---|---|---|---|
| SBI3022 | - | 16 | 2026-06-29 |
| SBI3034 | - | 13 | 2026-07-13 |
| SBI3032 | - | 10 | 2026-06-22 |
| SBI3021 | - | 10 | 2026-06-28 |
| SBI1004 | S7 Airlines (Siberia Airlines) | 9 | 2026-07-05 |
| SBI2582 | - | 8 | 2026-07-10 |
| SBI1214 | S7 Airlines (Siberia Airlines) | 8 | 2026-06-23 |
| SBI2606 | - | 7 | 2026-06-18 |
| SBI1213 | S7 Airlines (Siberia Airlines) | 6 | 2026-06-23 |
| SBI1074 | S7 Airlines (Siberia Airlines) | 6 | 2026-05-26 |
| SBI5303 | - | 5 | 2026-06-22 |
| SBI2594 | - | 5 | 2026-07-12 |
| SBI2572 | - | 5 | 2026-06-17 |
| SBI2508 | S7 Airlines (Siberia Airlines) | 5 | 2026-06-10 |
| SBI1073 | S7 Airlines (Siberia Airlines) | 5 | 2026-06-06 |
| SBI5242 | S7 Airlines (Siberia Airlines) | 4 | 2026-05-12 |
| SBI3031 | - | 4 | 2026-06-21 |
| SBI3018 | - | 4 | 2026-07-13 |
| SBI2605 | S7 Airlines (Siberia Airlines) | 4 | 2026-06-04 |
| SBI2593 | - | 4 | 2026-07-11 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | SBI3018 | - | Jul 13, 23:15 UTC | Jul 14, 05:00 UTC | 5h 45m |
| 2026-07-13 | SBI3034 | - | Jul 13, 04:25 UTC | Jul 13, 23:55 UTC | 19h 30m |
| 2026-07-12 | SBI3034 | - | Jul 12, 23:35 UTC | Jul 13, 23:30 UTC | 23h 55m |
| 2026-07-12 | SBI3034 | - | Jul 12, 23:20 UTC | Jul 13, 05:10 UTC | 5h 50m |
| 2026-07-12 | SBI2594 | - | Jul 12, 00:45 UTC | Jul 12, 01:35 UTC | 50m |
| 2026-07-11 | SBI2593 | - | Jul 11, 19:10 UTC | Jul 11, 23:00 UTC | 3h 50m |
| 2026-07-10 | SBI2582 | - | Jul 10, 23:05 UTC | Jul 11, 05:25 UTC | 6h 20m |
| 2026-07-10 | SBI1006 | LED → DME | Jul 10, 16:30 UTC | Jul 10, 16:45 UTC | 15m |
| 2026-07-10 | SBI5390 | - | Jul 10, 02:55 UTC | Jul 10, 06:30 UTC | 3h 35m |
| 2026-07-09 | SBI5239 | OVB → IKT | Jul 9, 14:55 UTC | Jul 10, 01:20 UTC | 10h 25m |
| 2026-07-08 | SBI8992 | OVB → IKT | Jul 8, 23:45 UTC | Jul 9, 11:55 UTC | 12h 10m |
| 2026-07-08 | SBI8992 | OVB → IKT | Jul 8, 17:05 UTC | Jul 9, 11:55 UTC | 18h 50m |
| 2026-07-07 | SBI3034 | - | Jul 7, 23:35 UTC | Jul 8, 05:20 UTC | 5h 45m |
| 2026-07-07 | SBI2600 | - | Jul 7, 01:35 UTC | Jul 8, 00:05 UTC | 22h 30m |
| 2026-07-06 | SBI2599 | - | Jul 6, 22:30 UTC | Jul 7, 02:15 UTC | 3h 45m |
| 2026-07-06 | SBI1005 | - | Jul 6, 15:10 UTC | Jul 6, 15:20 UTC | 10m |
| 2026-07-05 | SBI1004 | LED → DME | Jul 5, 09:10 UTC | Jul 5, 09:35 UTC | 25m |
| 2026-07-05 | SBI1003 | - | Jul 5, 07:20 UTC | Jul 5, 07:35 UTC | 15m |
| 2026-07-05 | SBI2594 | - | Jul 5, 00:55 UTC | Jul 5, 01:45 UTC | 50m |
| 2026-07-04 | SBI2593 | - | Jul 4, 16:30 UTC | Jul 4, 23:15 UTC | 6h 45m |
| 2026-07-04 | SBI1005 | - | Jul 4, 15:05 UTC | Jul 4, 15:15 UTC | 10m |
| 2026-07-02 | SBI3040 | - | Jul 2, 22:10 UTC | Jul 3, 04:00 UTC | 5h 50m |
| 2026-07-02 | SBI3040 | - | Jul 2, 07:05 UTC | Jul 3, 04:00 UTC | 20h 55m |
| 2026-07-01 | SBI5263 | OVB → YKS | Jul 1, 18:40 UTC | Jul 2, 02:40 UTC | 8h 0m |
| 2026-06-30 | SBI5241 | - | Jun 30, 22:10 UTC | Jul 1, 04:40 UTC | 6h 30m |
| 2026-06-29 | SBI2170 | MRV → DME | Jun 29, 15:09 UTC | Jun 29, 15:19 UTC | 10m |
| 2026-06-29 | SBI3022 | - | Jun 29, 04:55 UTC | Jun 29, 12:00 UTC | 7h 5m |
| 2026-06-28 | SBI3022 | - | Jun 28, 13:34 UTC | Jun 29, 12:00 UTC | 22h 25m |
| 2026-06-28 | SBI3021 | - | Jun 28, 13:10 UTC | Jun 29, 05:34 UTC | 16h 25m |
| 2026-06-28 | SBI3021 | - | Jun 28, 10:24 UTC | Jun 29, 05:34 UTC | 19h 10m |
| 2026-06-27 | SBI3021 | - | Jun 27, 23:19 UTC | Jun 28, 13:55 UTC | 14h 35m |
| 2026-06-27 | SBI3021 | - | Jun 27, 16:55 UTC | Jun 28, 13:55 UTC | 21h 0m |
| 2026-06-27 | SBI1005 | - | Jun 27, 15:14 UTC | Jun 27, 15:24 UTC | 10m |
| 2026-06-26 | SBI3017 | - | Jun 26, 21:59 UTC | Jun 27, 03:40 UTC | 5h 40m |
| 2026-06-25 | SBI2050 | AER → DME | Jun 25, 11:15 UTC | Jun 25, 11:25 UTC | 10m |
| 2026-06-24 | SBI2153 | DME → OGZ | Jun 24, 11:34 UTC | Jun 25, 11:25 UTC | 23h 50m |
| 2026-06-23 | SBI3039 | - | Jun 23, 22:05 UTC | Jun 24, 12:25 UTC | 14h 20m |
| 2026-06-23 | SBI1214 | KGD → DME | Jun 23, 15:34 UTC | Jun 24, 12:25 UTC | 20h 50m |
| 2026-06-23 | SBI1214 | KGD → DME | Jun 23, 15:24 UTC | Jun 24, 12:25 UTC | 21h 0m |
| 2026-06-23 | SBI1213 | DME → MRV | Jun 23, 12:40 UTC | Jun 23, 13:45 UTC | 1h 5m |
| 2026-06-22 | SBI5303 | - | Jun 22, 22:05 UTC | Jun 23, 04:00 UTC | 5h 55m |
| 2026-06-22 | SBI3032 | - | Jun 22, 02:50 UTC | Jun 22, 17:34 UTC | 14h 45m |
| 2026-06-21 | SBI3031 | - | Jun 21, 21:34 UTC | Jun 22, 17:34 UTC | 20h 0m |
| 2026-06-21 | SBI3031 | - | Jun 21, 13:09 UTC | Jun 22, 03:35 UTC | 14h 25m |
| 2026-06-18 | SBI2606 | - | Jun 18, 00:15 UTC | Jun 18, 00:45 UTC | 30m |
| 2026-06-17 | SBI2572 | - | Jun 17, 04:15 UTC | Jun 17, 23:00 UTC | 18h 45m |
| 2026-06-17 | SBI2572 | - | Jun 17, 00:10 UTC | Jun 17, 23:00 UTC | 22h 50m |
| 2026-06-15 | SBI5303 | - | Jun 15, 22:20 UTC | Jun 16, 03:50 UTC | 5h 30m |
| 2026-06-15 | SBI1212 | - | Jun 15, 12:35 UTC | Jun 15, 17:34 UTC | 5h 0m |
| 2026-06-14 | SBI1211 | - | Jun 14, 21:35 UTC | Jun 15, 10:50 UTC | 13h 14m |
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-73422 page for operator, model, and routing details .