sensors Mode-S transponder
151ECF
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73423 · AIRBUS A-320
- Hex
- 151ECF
- Octal
- 05217317
- Decimal
- 1,384,143
- Country
- RU
- Tail
- RA-73423
- Type
- A320
- Flights observed
- 173
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- 14h ago
Last known position
Country allocation
The ICAO 24-bit address 151ECF 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 |
|---|---|---|---|
| SBI2582 | - | 14 | 2026-07-03 |
| SBI3034 | - | 10 | 2026-07-13 |
| SBI3018 | S7 Airlines (Siberia Airlines) | 10 | 2026-05-18 |
| SBI3022 | - | 9 | 2026-07-13 |
| SBI2572 | S7 Airlines (Siberia Airlines) | 8 | 2026-06-06 |
| SBI3021 | - | 7 | 2026-07-12 |
| SBI3042 | - | 6 | 2026-07-05 |
| SBI1214 | S7 Airlines (Siberia Airlines) | 6 | 2026-05-26 |
| SBI3031 | - | 5 | 2026-07-11 |
| SBI2629 | S7 Airlines (Siberia Airlines) | 5 | 2026-05-27 |
| SBI2571 | S7 Airlines (Siberia Airlines) | 5 | 2026-04-15 |
| SBI1213 | S7 Airlines (Siberia Airlines) | 5 | 2026-05-26 |
| SBI5303 | - | 4 | 2026-07-08 |
| SBI3032 | - | 4 | 2026-06-20 |
| SBI2625 | S7 Airlines (Siberia Airlines) | 4 | 2026-06-06 |
| SBI2605 | S7 Airlines (Siberia Airlines) | 4 | 2026-05-07 |
| SBI2630 | - | 3 | 2026-07-01 |
| SBI2606 | S7 Airlines (Siberia Airlines) | 3 | 2026-05-08 |
| SBI2594 | S7 Airlines (Siberia Airlines) | 3 | 2026-04-23 |
| SBI2581 | S7 Airlines (Siberia Airlines) | 3 | 2026-06-07 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | SBI3034 | - | Jul 13, 22:55 UTC | Jul 14, 04:55 UTC | 6h 0m |
| 2026-07-13 | SBI3022 | - | Jul 13, 04:50 UTC | Jul 13, 23:35 UTC | 18h 45m |
| 2026-07-12 | SBI3021 | - | Jul 12, 13:25 UTC | Jul 13, 05:31 UTC | 16h 5m |
| 2026-07-11 | SBI3031 | - | Jul 11, 18:10 UTC | Jul 12, 03:20 UTC | 9h 10m |
| 2026-07-10 | SBI2514 | OVB → DME | Jul 10, 17:20 UTC | Jul 10, 17:40 UTC | 20m |
| 2026-07-08 | SBI5303 | - | Jul 8, 22:00 UTC | Jul 9, 03:35 UTC | 5h 35m |
| 2026-07-08 | SBI1073 | DME → KUF | Jul 8, 12:40 UTC | Jul 8, 12:50 UTC | 10m |
| 2026-07-06 | SBI3040 | - | Jul 6, 22:35 UTC | Jul 7, 16:35 UTC | 18h 0m |
| 2026-07-05 | SBI3021 | - | Jul 5, 13:20 UTC | Jul 6, 05:25 UTC | 16h 5m |
| 2026-07-05 | SBI3042 | - | Jul 5, 08:10 UTC | Jul 5, 08:20 UTC | 10m |
| 2026-07-03 | SBI3022 | - | Jul 3, 13:20 UTC | Jul 4, 05:25 UTC | 16h 5m |
| 2026-07-03 | SBI2582 | - | Jul 3, 05:50 UTC | Jul 4, 05:25 UTC | 23h 35m |
| 2026-07-03 | SBI2582 | - | Jul 3, 05:20 UTC | Jul 3, 13:55 UTC | 8h 35m |
| 2026-07-01 | SBI2630 | - | Jul 1, 21:50 UTC | Jul 2, 03:30 UTC | 5h 40m |
| 2026-06-29 | SBI3040 | - | Jun 29, 22:44 UTC | Jun 30, 04:40 UTC | 5h 56m |
| 2026-06-28 | SBI3031 | - | Jun 28, 21:24 UTC | Jun 28, 22:04 UTC | 40m |
| 2026-06-28 | SBI3031 | - | Jun 28, 03:35 UTC | Jun 28, 22:04 UTC | 18h 30m |
| 2026-06-27 | SBI3031 | - | Jun 27, 23:50 UTC | Jun 28, 22:04 UTC | 22h 15m |
| 2026-06-27 | SBI3042 | - | Jun 27, 07:30 UTC | Jun 28, 03:40 UTC | 20h 10m |
| 2026-06-25 | SBI1006 | LED → DME | Jun 25, 16:29 UTC | Jun 26, 06:39 UTC | 14h 10m |
| 2026-06-25 | SBI1005 | - | Jun 25, 14:55 UTC | Jun 25, 15:15 UTC | 20m |
| 2026-06-25 | SBI3034 | - | Jun 25, 01:09 UTC | Jun 25, 09:29 UTC | 8h 20m |
| 2026-06-24 | SBI2582 | - | Jun 24, 03:50 UTC | Jun 25, 01:40 UTC | 21h 50m |
| 2026-06-24 | SBI2582 | - | Jun 24, 03:44 UTC | Jun 25, 01:40 UTC | 21h 55m |
| 2026-06-23 | SBI2582 | - | Jun 23, 21:05 UTC | Jun 24, 05:20 UTC | 8h 15m |
| 2026-06-22 | SBI3034 | - | Jun 22, 22:59 UTC | Jun 23, 16:29 UTC | 17h 30m |
| 2026-06-21 | SBI2582 | - | Jun 21, 21:44 UTC | Jun 22, 06:15 UTC | 8h 30m |
| 2026-06-20 | SBI3032 | - | Jun 20, 21:49 UTC | Jun 21, 21:44 UTC | 23h 55m |
| 2026-06-20 | SBI3032 | - | Jun 20, 21:10 UTC | Jun 21, 03:19 UTC | 6h 10m |
| 2026-06-20 | SBI2582 | - | Jun 20, 03:49 UTC | Jun 21, 03:19 UTC | 23h 30m |
| 2026-06-20 | SBI2582 | - | Jun 20, 03:39 UTC | Jun 20, 21:49 UTC | 18h 10m |
| 2026-06-19 | SBI2582 | - | Jun 19, 21:54 UTC | Jun 20, 21:44 UTC | 23h 50m |
| 2026-06-19 | SBI1007 | DME → LED | Jun 19, 16:34 UTC | Jun 19, 16:59 UTC | 25m |
| 2026-06-18 | SBI3031 | - | Jun 18, 21:20 UTC | Jun 19, 03:20 UTC | 5h 59m |
| 2026-06-17 | SBI5303 | - | Jun 17, 22:20 UTC | Jun 18, 04:05 UTC | 5h 45m |
| 2026-06-16 | SBI3032 | - | Jun 16, 21:50 UTC | Jun 17, 17:20 UTC | 19h 30m |
| 2026-06-16 | SBI3032 | - | Jun 16, 21:25 UTC | Jun 17, 17:20 UTC | 19h 55m |
| 2026-06-15 | SBI3022 | - | Jun 15, 04:45 UTC | Jun 15, 05:25 UTC | 40m |
| 2026-06-14 | SBI3021 | DME → IKT | Jun 14, 14:45 UTC | Jun 14, 15:25 UTC | 40m |
| 2026-06-14 | SBI2632 | - | Jun 14, 08:00 UTC | Jun 14, 08:15 UTC | 15m |
| 2026-06-12 | SBI2582 | - | Jun 12, 23:00 UTC | Jun 13, 15:00 UTC | 15h 59m |
| 2026-06-12 | SBI2566 | OMS → DME | Jun 12, 04:05 UTC | Jun 12, 04:15 UTC | 10m |
| 2026-06-11 | SBI3022 | - | Jun 11, 05:50 UTC | Jun 12, 02:20 UTC | 20h 31m |
| 2026-06-10 | SBI3021 | DME → IKT | Jun 10, 13:30 UTC | Jun 11, 06:10 UTC | 16h 40m |
| 2026-06-10 | SBI3034 | UUD → DME | Jun 10, 08:20 UTC | Jun 10, 08:45 UTC | 25m |
| 2026-06-09 | SBI3034 | UUD → DME | Jun 9, 23:15 UTC | Jun 10, 05:10 UTC | 5h 55m |
| 2026-06-09 | SBI2566 | OMS → DME | Jun 9, 02:40 UTC | Jun 9, 23:45 UTC | 21h 5m |
| 2026-06-08 | SBI1008 | LED → DME | Jun 8, 18:00 UTC | Jun 9, 03:25 UTC | 9h 25m |
| 2026-06-07 | SBI2582 | NSK → DME | Jun 7, 22:10 UTC | Jun 8, 05:00 UTC | 6h 50m |
| 2026-06-07 | SBI2581 | DME → NSK | Jun 7, 05:10 UTC | Jun 7, 22:25 UTC | 17h 15m |
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-73423 page for operator, model, and routing details .