sensors Mode-S transponder
151EBF
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73407 · AIRBUS A-320
- Hex
- 151EBF
- Octal
- 05217277
- Decimal
- 1,384,127
- Country
- RU
- Tail
- RA-73407
- Type
- A320
- Flights observed
- 187
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 151EBF 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 | - | 16 | 2026-07-10 |
| SBI3032 | - | 9 | 2026-07-10 |
| SBI3746 | S7 Airlines (Siberia Airlines) | 7 | 2026-07-08 |
| SBI3021 | - | 7 | 2026-06-24 |
| SBI2514 | S7 Airlines (Siberia Airlines) | 7 | 2026-06-09 |
| SBI3745 | - | 6 | 2026-07-08 |
| SBI3022 | - | 6 | 2026-07-01 |
| SBI5115 | S7 Airlines (Siberia Airlines) | 5 | 2026-06-12 |
| SBI3031 | S7 Airlines (Siberia Airlines) | 5 | 2026-04-15 |
| SBI3018 | - | 5 | 2026-07-08 |
| SBI3017 | - | 5 | 2026-07-05 |
| SBI3749 | - | 4 | 2026-06-30 |
| SBI1214 | - | 4 | 2026-07-05 |
| SBI5245 | S7 Airlines (Siberia Airlines) | 3 | 2026-06-11 |
| SBI3750 | S7 Airlines (Siberia Airlines) | 3 | 2026-06-30 |
| SBI3034 | - | 3 | 2026-06-17 |
| SBI2630 | S7 Airlines (Siberia Airlines) | 3 | 2026-05-15 |
| SBI2572 | S7 Airlines (Siberia Airlines) | 3 | 2026-04-30 |
| SBI2565 | S7 Airlines (Siberia Airlines) | 3 | 2026-04-20 |
| SBI2511 | S7 Airlines (Siberia Airlines) | 3 | 2026-04-27 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | SBI5322 | - | Jul 13, 05:25 UTC | Jul 13, 05:40 UTC | 15m |
| 2026-07-13 | SBI5321 | - | Jul 13, 04:10 UTC | Jul 13, 04:25 UTC | 15m |
| 2026-07-11 | SBI5211 | - | Jul 11, 19:35 UTC | Jul 12, 04:45 UTC | 9h 10m |
| 2026-07-11 | SBI2509 | DME → OVB | Jul 11, 14:05 UTC | Jul 11, 14:15 UTC | 10m |
| 2026-07-10 | SBI3032 | - | Jul 10, 21:30 UTC | Jul 11, 03:20 UTC | 5h 50m |
| 2026-07-10 | SBI2582 | - | Jul 10, 03:50 UTC | Jul 11, 03:20 UTC | 23h 30m |
| 2026-07-09 | SBI2582 | - | Jul 9, 22:10 UTC | Jul 10, 21:45 UTC | 23h 35m |
| 2026-07-08 | SBI3018 | - | Jul 8, 22:10 UTC | Jul 9, 03:45 UTC | 5h 35m |
| 2026-07-08 | SBI3746 | AYT → DME | Jul 8, 12:10 UTC | Jul 8, 13:50 UTC | 1h 40m |
| 2026-07-08 | SBI3745 | - | Jul 8, 10:40 UTC | Jul 8, 11:05 UTC | 25m |
| 2026-07-06 | SBI3018 | - | Jul 6, 21:50 UTC | Jul 7, 04:25 UTC | 6h 35m |
| 2026-07-06 | SBI6311 | - | Jul 6, 19:35 UTC | Jul 6, 19:45 UTC | 10m |
| 2026-07-05 | SBI3017 | - | Jul 5, 22:15 UTC | Jul 6, 13:50 UTC | 15h 35m |
| 2026-07-05 | SBI3017 | - | Jul 5, 19:15 UTC | Jul 6, 13:50 UTC | 18h 35m |
| 2026-07-05 | SBI3017 | - | Jul 5, 15:50 UTC | Jul 6, 13:50 UTC | 22h 0m |
| 2026-07-05 | SBI1214 | - | Jul 5, 15:15 UTC | Jul 6, 13:45 UTC | 22h 30m |
| 2026-07-04 | SBI3040 | - | Jul 4, 22:05 UTC | Jul 5, 13:35 UTC | 15h 30m |
| 2026-07-04 | SBI2582 | - | Jul 4, 03:55 UTC | Jul 5, 03:45 UTC | 23h 50m |
| 2026-07-03 | SBI5726 | - | Jul 3, 01:05 UTC | Jul 3, 05:05 UTC | 4h 0m |
| 2026-07-02 | SBI5725 | OVB → PKX | Jul 2, 22:30 UTC | Jul 2, 22:40 UTC | 10m |
| 2026-07-02 | SBI5725 | OVB → PKX | Jul 2, 19:20 UTC | Jul 2, 19:55 UTC | 35m |
| 2026-07-01 | SBI3022 | - | Jul 1, 13:40 UTC | Jul 2, 05:30 UTC | 15h 50m |
| 2026-06-30 | SBI3039 | - | Jun 30, 23:25 UTC | Jul 1, 14:10 UTC | 14h 45m |
| 2026-06-30 | SBI3039 | - | Jun 30, 13:50 UTC | Jul 1, 13:45 UTC | 23h 55m |
| 2026-06-30 | SBI3750 | IST → DME | Jun 30, 13:35 UTC | Jul 1, 05:10 UTC | 15h 35m |
| 2026-06-30 | SBI3749 | - | Jun 30, 11:40 UTC | Jun 30, 12:05 UTC | 25m |
| 2026-06-28 | SBI2508 | - | Jun 28, 07:40 UTC | Jun 28, 23:39 UTC | 16h 0m |
| 2026-06-28 | SBI5550 | - | Jun 28, 02:29 UTC | Jun 28, 23:39 UTC | 21h 10m |
| 2026-06-27 | SBI5550 | - | Jun 27, 18:49 UTC | Jun 28, 07:44 UTC | 12h 55m |
| 2026-06-24 | SBI3021 | - | Jun 24, 13:34 UTC | Jun 25, 03:34 UTC | 14h 0m |
| 2026-06-23 | SBI3021 | - | Jun 23, 17:50 UTC | Jun 24, 14:15 UTC | 20h 25m |
| 2026-06-23 | SBI1006 | LED → DME | Jun 23, 17:15 UTC | Jun 24, 14:15 UTC | 21h 0m |
| 2026-06-23 | SBI1005 | - | Jun 23, 08:04 UTC | Jun 23, 15:50 UTC | 7h 45m |
| 2026-06-22 | SBI3750 | IST → DME | Jun 22, 14:45 UTC | Jun 23, 08:09 UTC | 17h 25m |
| 2026-06-22 | SBI3749 | - | Jun 22, 12:49 UTC | Jun 22, 13:10 UTC | 20m |
| 2026-06-21 | SBI1005 | - | Jun 21, 14:50 UTC | Jun 21, 15:09 UTC | 20m |
| 2026-06-20 | SBI3022 | - | Jun 20, 04:44 UTC | Jun 20, 23:55 UTC | 19h 10m |
| 2026-06-19 | SBI3021 | DME → IKT | Jun 19, 16:39 UTC | Jun 20, 05:24 UTC | 12h 45m |
| 2026-06-18 | SBI2582 | - | Jun 18, 21:50 UTC | Jun 19, 17:24 UTC | 19h 34m |
| 2026-06-18 | SBI2582 | - | Jun 18, 21:40 UTC | Jun 19, 17:24 UTC | 19h 44m |
| 2026-06-18 | SBI2582 | - | Jun 18, 07:10 UTC | Jun 19, 05:14 UTC | 22h 4m |
| 2026-06-17 | SBI2602 | - | Jun 17, 21:30 UTC | Jun 18, 07:15 UTC | 9h 45m |
| 2026-06-17 | SBI3034 | - | Jun 17, 04:05 UTC | Jun 17, 21:30 UTC | 17h 25m |
| 2026-06-16 | SBI3034 | - | Jun 16, 23:00 UTC | Jun 17, 21:30 UTC | 22h 30m |
| 2026-06-16 | SBI3746 | AYT → DME | Jun 16, 14:20 UTC | Jun 17, 04:55 UTC | 14h 36m |
| 2026-06-16 | SBI3745 | - | Jun 16, 12:00 UTC | Jun 16, 12:35 UTC | 35m |
| 2026-06-14 | SBI1212 | - | Jun 14, 12:00 UTC | Jun 15, 00:45 UTC | 12h 45m |
| 2026-06-13 | SBI1211 | - | Jun 13, 15:55 UTC | Jun 14, 10:00 UTC | 18h 5m |
| 2026-06-12 | SBI5115 | OVB → KRR | Jun 12, 07:50 UTC | Jun 13, 03:35 UTC | 19h 45m |
| 2026-06-12 | SBI5115 | OVB → KRR | Jun 12, 07:15 UTC | Jun 13, 03:35 UTC | 20h 20m |
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-73407 page for operator, model, and routing details .