sensors Mode-S transponder
151ECB
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73419 · AIRBUS A-320
- Hex
- 151ECB
- Octal
- 05217313
- Decimal
- 1,384,139
- Country
- RU
- Tail
- RA-73419
- Type
- A320
- Flights observed
- 124
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- 12h ago
Last known position
Country allocation
The ICAO 24-bit address 151ECB 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 |
|---|---|---|---|
| SBI5304 | - | 7 | 2026-07-07 |
| SBI3746 | S7 Airlines (Siberia Airlines) | 6 | 2026-07-09 |
| SBI3745 | - | 6 | 2026-07-13 |
| SBI2606 | S7 Airlines (Siberia Airlines) | 6 | 2026-06-12 |
| SBI2572 | S7 Airlines (Siberia Airlines) | 6 | 2026-04-25 |
| SBI3031 | - | 5 | 2026-07-13 |
| SBI1214 | - | 5 | 2026-06-30 |
| SBI3032 | - | 4 | 2026-06-24 |
| SBI2605 | S7 Airlines (Siberia Airlines) | 4 | 2026-06-12 |
| SBI2601 | S7 Airlines (Siberia Airlines) | 4 | 2026-05-10 |
| SBI1138 | S7 Airlines (Siberia Airlines) | 4 | 2026-05-04 |
| SBI3749 | - | 3 | 2026-06-27 |
| SBI3033 | - | 3 | 2026-06-28 |
| SBI3022 | - | 3 | 2026-06-25 |
| SBI3018 | S7 Airlines (Siberia Airlines) | 3 | 2026-06-14 |
| SBI2630 | - | 3 | 2026-06-22 |
| SBI2593 | - | 3 | 2026-06-27 |
| SBI2582 | S7 Airlines (Siberia Airlines) | 3 | 2026-04-16 |
| SBI1213 | - | 3 | 2026-07-07 |
| SBI5303 | - | 2 | 2026-07-05 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-15 | SBI2626 | - | Jul 15, 05:50 UTC | Jul 15, 06:10 UTC | 20m |
| 2026-07-15 | SBI2626 | - | Jul 15, 01:55 UTC | Jul 15, 05:15 UTC | 3h 20m |
| 2026-07-14 | SBI3748 | AYT → DME | Jul 14, 14:40 UTC | Jul 15, 00:30 UTC | 9h 49m |
| 2026-07-13 | SBI3747 | DME → AYT | Jul 13, 21:45 UTC | Jul 14, 13:25 UTC | 15h 40m |
| 2026-07-13 | SBI3031 | - | Jul 13, 12:05 UTC | Jul 14, 03:40 UTC | 15h 35m |
| 2026-07-13 | SBI3745 | - | Jul 13, 09:35 UTC | Jul 13, 10:40 UTC | 1h 5m |
| 2026-07-11 | SBI1005 | - | Jul 11, 14:10 UTC | Jul 11, 15:45 UTC | 1h 35m |
| 2026-07-10 | SBI5211 | - | Jul 10, 19:35 UTC | Jul 11, 05:01 UTC | 9h 26m |
| 2026-07-09 | SBI3746 | AYT → DME | Jul 9, 11:55 UTC | Jul 10, 03:50 UTC | 15h 55m |
| 2026-07-09 | SBI3745 | - | Jul 9, 08:40 UTC | Jul 9, 10:35 UTC | 1h 55m |
| 2026-07-07 | SBI1213 | - | Jul 7, 13:55 UTC | Jul 7, 14:40 UTC | 45m |
| 2026-07-07 | SBI5304 | - | Jul 7, 05:00 UTC | Jul 7, 05:30 UTC | 30m |
| 2026-07-05 | SBI5303 | - | Jul 5, 22:10 UTC | Jul 6, 03:55 UTC | 5h 45m |
| 2026-07-04 | SBI5555 | - | Jul 4, 07:15 UTC | Jul 4, 12:50 UTC | 5h 35m |
| 2026-07-03 | SBI5727 | OVB → XIY | Jul 3, 17:20 UTC | Jul 4, 03:05 UTC | 9h 45m |
| 2026-07-02 | SBI5303 | - | Jul 2, 21:55 UTC | Jul 3, 03:45 UTC | 5h 50m |
| 2026-07-01 | SBI5304 | - | Jul 1, 22:05 UTC | Jul 2, 03:50 UTC | 5h 45m |
| 2026-06-30 | SBI1214 | - | Jun 30, 15:10 UTC | Jul 1, 03:40 UTC | 12h 30m |
| 2026-06-30 | SBI1213 | - | Jun 30, 13:15 UTC | Jun 30, 13:50 UTC | 35m |
| 2026-06-29 | SBI5304 | - | Jun 29, 22:35 UTC | Jun 30, 04:00 UTC | 5h 26m |
| 2026-06-29 | SBI5304 | - | Jun 29, 06:50 UTC | Jun 30, 04:00 UTC | 21h 11m |
| 2026-06-29 | SBI5304 | - | Jun 29, 06:44 UTC | Jun 30, 04:00 UTC | 21h 16m |
| 2026-06-28 | SBI3033 | - | Jun 28, 22:49 UTC | Jun 29, 22:44 UTC | 23h 55m |
| 2026-06-28 | SBI3033 | - | Jun 28, 13:45 UTC | Jun 29, 07:15 UTC | 17h 30m |
| 2026-06-28 | SBI2594 | - | Jun 28, 00:55 UTC | Jun 28, 11:39 UTC | 10h 45m |
| 2026-06-27 | SBI2593 | - | Jun 27, 22:40 UTC | Jun 27, 23:19 UTC | 40m |
| 2026-06-27 | SBI3750 | IST → DME | Jun 27, 13:44 UTC | Jun 27, 14:20 UTC | 35m |
| 2026-06-27 | SBI3749 | - | Jun 27, 11:09 UTC | Jun 27, 11:25 UTC | 15m |
| 2026-06-26 | SBI3749 | - | Jun 26, 23:34 UTC | Jun 27, 10:25 UTC | 10h 50m |
| 2026-06-25 | SBI3022 | - | Jun 25, 21:44 UTC | Jun 26, 05:30 UTC | 7h 45m |
| 2026-06-25 | SBI6311 | IKT → PKX | Jun 25, 19:49 UTC | Jun 25, 19:59 UTC | 10m |
| 2026-06-25 | SBI3021 | - | Jun 25, 13:14 UTC | Jun 25, 13:55 UTC | 40m |
| 2026-06-24 | SBI2168 | MRV → DME | Jun 24, 13:10 UTC | Jun 24, 13:34 UTC | 25m |
| 2026-06-24 | SBI3032 | - | Jun 24, 02:45 UTC | Jun 24, 11:05 UTC | 8h 20m |
| 2026-06-23 | SBI3746 | AYT → DME | Jun 23, 12:49 UTC | Jun 24, 11:05 UTC | 22h 15m |
| 2026-06-23 | SBI3746 | AYT → DME | Jun 23, 11:49 UTC | Jun 24, 10:45 UTC | 22h 55m |
| 2026-06-23 | SBI3745 | - | Jun 23, 07:40 UTC | Jun 23, 10:24 UTC | 2h 45m |
| 2026-06-22 | SBI2630 | - | Jun 22, 07:10 UTC | Jun 22, 07:45 UTC | 35m |
| 2026-06-21 | SBI3750 | IST → DME | Jun 21, 13:54 UTC | Jun 21, 23:40 UTC | 9h 45m |
| 2026-06-19 | SBI3746 | AYT → DME | Jun 19, 12:25 UTC | Jun 20, 03:09 UTC | 14h 45m |
| 2026-06-18 | SBI1214 | KGD → DME | Jun 18, 16:25 UTC | Jun 19, 10:39 UTC | 18h 14m |
| 2026-06-18 | SBI1214 | KGD → DME | Jun 18, 03:00 UTC | Jun 18, 18:05 UTC | 15h 5m |
| 2026-06-17 | SBI1214 | KGD → DME | Jun 17, 21:55 UTC | Jun 18, 18:05 UTC | 20h 10m |
| 2026-06-17 | SBI1214 | KGD → DME | Jun 17, 18:50 UTC | Jun 18, 18:05 UTC | 23h 15m |
| 2026-06-17 | SBI3031 | - | Jun 17, 18:40 UTC | Jun 18, 16:45 UTC | 22h 5m |
| 2026-06-17 | SBI3042 | BTK → DME | Jun 17, 07:45 UTC | Jun 17, 08:00 UTC | 15m |
| 2026-06-15 | SBI3746 | AYT → DME | Jun 15, 12:49 UTC | Jun 15, 14:45 UTC | 1h 55m |
| 2026-06-15 | SBI3745 | - | Jun 15, 11:05 UTC | Jun 15, 11:34 UTC | 30m |
| 2026-06-14 | SBI2505 | - | Jun 14, 11:55 UTC | Jun 14, 12:05 UTC | 10m |
| 2026-06-14 | SBI3018 | IKT → DME | Jun 14, 08:10 UTC | Jun 14, 08:20 UTC | 10m |
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-73419 page for operator, model, and routing details .