sensors Mode-S transponder
151EBA
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73402 · AIRBUS A-320
- Hex
- 151EBA
- Octal
- 05217272
- Decimal
- 1,384,122
- Country
- RU
- Tail
- RA-73402
- Type
- A320
- Flights observed
- 217
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- 2h ago
Last known position
Country allocation
The ICAO 24-bit address 151EBA 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 |
|---|---|---|---|
| SBI3034 | - | 16 | 2026-07-04 |
| SBI3022 | - | 15 | 2026-07-13 |
| SBI3021 | - | 13 | 2026-07-13 |
| SBI3033 | - | 11 | 2026-06-30 |
| SBI3032 | - | 11 | 2026-07-06 |
| SBI3031 | S7 Airlines (Siberia Airlines) | 10 | 2026-06-09 |
| SBI1213 | - | 10 | 2026-07-12 |
| SBI3746 | S7 Airlines (Siberia Airlines) | 7 | 2026-07-03 |
| SBI1214 | - | 7 | 2026-07-02 |
| SBI3275 | - | 6 | 2026-06-25 |
| SBI3017 | - | 6 | 2026-07-06 |
| SBI3749 | - | 5 | 2026-07-08 |
| SBI3018 | S7 Airlines (Siberia Airlines) | 5 | 2026-05-20 |
| SBI2605 | - | 5 | 2026-07-07 |
| SBI6403 | S7 Airlines (Siberia Airlines) | 4 | 2026-05-12 |
| SBI3745 | - | 4 | 2026-07-03 |
| SBI2606 | - | 4 | 2026-07-08 |
| SBI2594 | - | 4 | 2026-06-29 |
| SBI2572 | - | 4 | 2026-06-27 |
| SBI6404 | S7 Airlines (Siberia Airlines) | 3 | 2026-05-10 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | SBI3022 | - | Jul 13, 22:40 UTC | Jul 14, 05:50 UTC | 7h 10m |
| 2026-07-13 | SBI6311 | - | Jul 13, 19:35 UTC | Jul 13, 19:50 UTC | 15m |
| 2026-07-13 | SBI3021 | - | Jul 13, 13:30 UTC | Jul 13, 14:00 UTC | 30m |
| 2026-07-12 | SBI1213 | - | Jul 12, 04:50 UTC | Jul 12, 14:30 UTC | 9h 40m |
| 2026-07-11 | SBI3021 | - | Jul 11, 13:20 UTC | Jul 12, 05:30 UTC | 16h 10m |
| 2026-07-11 | SBI3021 | - | Jul 11, 10:15 UTC | Jul 12, 05:30 UTC | 19h 15m |
| 2026-07-10 | SBI3021 | - | Jul 10, 22:50 UTC | Jul 11, 14:00 UTC | 15h 10m |
| 2026-07-10 | SBI3022 | - | Jul 10, 04:40 UTC | Jul 11, 04:30 UTC | 23h 51m |
| 2026-07-09 | SBI3022 | - | Jul 9, 21:50 UTC | Jul 10, 05:30 UTC | 7h 40m |
| 2026-07-09 | SBI3021 | - | Jul 9, 10:30 UTC | Jul 9, 14:05 UTC | 3h 35m |
| 2026-07-08 | SBI3750 | IST → DME | Jul 8, 13:30 UTC | Jul 9, 10:30 UTC | 21h 0m |
| 2026-07-08 | SBI3749 | - | Jul 8, 11:30 UTC | Jul 8, 11:55 UTC | 25m |
| 2026-07-08 | SBI2606 | - | Jul 8, 01:10 UTC | Jul 8, 01:40 UTC | 30m |
| 2026-07-07 | SBI2605 | - | Jul 7, 04:40 UTC | Jul 7, 23:45 UTC | 19h 5m |
| 2026-07-06 | SBI3017 | - | Jul 6, 23:20 UTC | Jul 7, 05:20 UTC | 6h 0m |
| 2026-07-06 | SBI3017 | - | Jul 6, 02:35 UTC | Jul 7, 00:05 UTC | 21h 30m |
| 2026-07-06 | SBI3032 | - | Jul 6, 02:25 UTC | Jul 7, 00:05 UTC | 21h 40m |
| 2026-07-05 | SBI1210 | - | Jul 5, 13:55 UTC | Jul 6, 03:15 UTC | 13h 20m |
| 2026-07-04 | SBI3034 | - | Jul 4, 22:50 UTC | Jul 5, 12:05 UTC | 13h 15m |
| 2026-07-04 | SBI3032 | - | Jul 4, 03:10 UTC | Jul 4, 23:30 UTC | 20h 20m |
| 2026-07-03 | SBI3746 | AYT → DME | Jul 3, 12:05 UTC | Jul 4, 03:55 UTC | 15h 50m |
| 2026-07-03 | SBI3745 | KEJ → AYT | Jul 3, 00:20 UTC | Jul 3, 10:45 UTC | 10h 25m |
| 2026-07-02 | SBI1214 | - | Jul 2, 15:20 UTC | Jul 2, 23:05 UTC | 7h 45m |
| 2026-07-02 | SBI1213 | - | Jul 2, 03:00 UTC | Jul 2, 13:45 UTC | 10h 45m |
| 2026-07-01 | SBI3034 | - | Jul 1, 04:35 UTC | Jul 2, 03:05 UTC | 22h 30m |
| 2026-06-30 | SBI3033 | - | Jun 30, 23:10 UTC | Jul 1, 04:55 UTC | 5h 45m |
| 2026-06-30 | SBI3032 | - | Jun 30, 02:55 UTC | Jun 30, 23:45 UTC | 20h 50m |
| 2026-06-29 | SBI3746 | AYT → DME | Jun 29, 12:00 UTC | Jun 30, 03:40 UTC | 15h 41m |
| 2026-06-29 | SBI2594 | - | Jun 29, 00:39 UTC | Jun 29, 10:24 UTC | 9h 45m |
| 2026-06-28 | SBI2593 | - | Jun 28, 19:34 UTC | Jun 28, 23:04 UTC | 3h 30m |
| 2026-06-28 | SBI2593 | - | Jun 28, 04:29 UTC | Jun 28, 23:04 UTC | 18h 35m |
| 2026-06-27 | SBI2168 | MRV → DME | Jun 27, 12:39 UTC | Jun 27, 12:55 UTC | 15m |
| 2026-06-27 | SBI2572 | - | Jun 27, 01:04 UTC | Jun 27, 05:49 UTC | 4h 45m |
| 2026-06-25 | SBI3748 | AYT → DME | Jun 25, 14:39 UTC | Jun 26, 04:24 UTC | 13h 45m |
| 2026-06-25 | SBI3747 | DME → AYT | Jun 25, 02:54 UTC | Jun 25, 13:09 UTC | 10h 15m |
| 2026-06-25 | SBI3275 | - | Jun 25, 01:04 UTC | Jun 25, 01:30 UTC | 25m |
| 2026-06-24 | SBI3275 | - | Jun 24, 04:34 UTC | Jun 25, 01:30 UTC | 20h 55m |
| 2026-06-24 | SBI3034 | - | Jun 24, 04:00 UTC | Jun 25, 01:30 UTC | 21h 30m |
| 2026-06-23 | SBI2594 | - | Jun 23, 00:54 UTC | Jun 23, 01:35 UTC | 40m |
| 2026-06-22 | SBI2593 | - | Jun 22, 19:19 UTC | Jun 22, 23:20 UTC | 4h 0m |
| 2026-06-22 | SBI1004 | LED → DME | Jun 22, 10:25 UTC | Jun 22, 11:24 UTC | 1h 0m |
| 2026-06-21 | SBI1007 | DME → LED | Jun 21, 16:14 UTC | Jun 21, 16:30 UTC | 15m |
| 2026-06-20 | SBI2509 | DME → OVB | Jun 20, 16:24 UTC | Jun 21, 07:59 UTC | 15h 35m |
| 2026-06-20 | SBI2606 | - | Jun 20, 04:39 UTC | Jun 20, 04:49 UTC | 10m |
| 2026-06-20 | SBI2606 | - | Jun 20, 00:24 UTC | Jun 20, 00:54 UTC | 30m |
| 2026-06-19 | SBI2605 | - | Jun 19, 22:39 UTC | Jun 19, 23:14 UTC | 35m |
| 2026-06-19 | SBI2605 | - | Jun 19, 19:39 UTC | Jun 19, 19:49 UTC | 10m |
| 2026-06-19 | SBI1010 | - | Jun 19, 15:54 UTC | Jun 19, 16:39 UTC | 45m |
| 2026-06-18 | SBI3033 | - | Jun 18, 22:40 UTC | Jun 19, 14:19 UTC | 15h 39m |
| 2026-06-18 | SBI3033 | - | Jun 18, 00:35 UTC | Jun 18, 23:25 UTC | 22h 50m |
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-73402 page for operator, model, and routing details .