sensors Mode-S transponder
151E90
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73360 · BOEING 737-800
- Hex
- 151E90
- Octal
- 05217220
- Decimal
- 1,384,080
- Country
- RU
- Tail
- RA-73360
- Type
- B738
- Flights observed
- 181
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- Jul 25, 07:15 UTC
Last known position
Country allocation
The ICAO 24-bit address 151E90 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 |
|---|---|---|---|
| SBI6419 | - | 12 | 2026-07-21 |
| SBI6327 | - | 10 | 2026-07-17 |
| SBI6311 | - | 9 | 2026-07-22 |
| SBI6409 | S7 Airlines (Siberia Airlines) | 8 | 2026-07-24 |
| SBI5250 | - | 7 | 2026-07-10 |
| SBI6420 | - | 6 | 2026-07-22 |
| SBI6318 | S7 Airlines (Siberia Airlines) | 6 | 2026-07-24 |
| SBI6317 | S7 Airlines (Siberia Airlines) | 6 | 2026-07-23 |
| SBI5863 | S7 Airlines (Siberia Airlines) | 6 | 2026-07-19 |
| SBI6415 | - | 5 | 2026-07-15 |
| SBI6410 | S7 Airlines (Siberia Airlines) | 5 | 2026-07-20 |
| SBI6328 | S7 Airlines (Siberia Airlines) | 5 | 2026-07-21 |
| SBI6312 | S7 Airlines (Siberia Airlines) | 4 | 2026-05-06 |
| SBI6310 | - | 4 | 2026-06-27 |
| SBI6309 | - | 4 | 2026-06-26 |
| SBI6245 | - | 4 | 2026-07-08 |
| SBI5864 | - | 4 | 2026-07-19 |
| SBI5732 | S7 Airlines (Siberia Airlines) | 4 | 2026-05-18 |
| SBI6306 | S7 Airlines (Siberia Airlines) | 3 | 2026-04-21 |
| SBI5889 | - | 3 | 2026-06-20 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-24 | SBI6409 | IKT → LED | Jul 24, 15:15 UTC | Jul 25, 07:15 UTC | 16h 0m |
| 2026-07-24 | SBI6331 | IKT → YKS | Jul 24, 06:05 UTC | Jul 25, 06:00 UTC | 23h 55m |
| 2026-07-24 | SBI6318 | OSS → IKT | Jul 24, 05:05 UTC | Jul 24, 21:10 UTC | 16h 5m |
| 2026-07-23 | SBI6317 | IKT → OSS | Jul 23, 10:55 UTC | Jul 24, 02:30 UTC | 15h 35m |
| 2026-07-22 | SBI6420 | - | Jul 22, 22:05 UTC | Jul 23, 17:20 UTC | 19h 15m |
| 2026-07-22 | SBI6420 | - | Jul 22, 21:50 UTC | Jul 23, 17:20 UTC | 19h 30m |
| 2026-07-22 | SBI6311 | - | Jul 22, 19:40 UTC | Jul 22, 19:50 UTC | 10m |
| 2026-07-21 | SBI6328 | OSS → IKT | Jul 21, 18:05 UTC | Jul 22, 12:55 UTC | 18h 50m |
| 2026-07-21 | SBI6419 | - | Jul 21, 05:55 UTC | Jul 21, 18:10 UTC | 12h 15m |
| 2026-07-20 | SBI6419 | - | Jul 20, 13:40 UTC | Jul 21, 06:40 UTC | 16h 59m |
| 2026-07-20 | SBI6410 | LED → IKT | Jul 20, 10:30 UTC | Jul 21, 06:40 UTC | 20h 10m |
| 2026-07-20 | SBI6410 | LED → IKT | Jul 20, 09:50 UTC | Jul 21, 06:40 UTC | 20h 49m |
| 2026-07-19 | SBI6409 | - | Jul 19, 21:55 UTC | Jul 20, 07:00 UTC | 9h 5m |
| 2026-07-19 | SBI5864 | - | Jul 19, 12:25 UTC | Jul 19, 14:15 UTC | 1h 50m |
| 2026-07-19 | SBI5863 | OVB → AYT | Jul 19, 09:50 UTC | Jul 19, 11:00 UTC | 1h 10m |
| 2026-07-18 | SBI5863 | OVB → AYT | Jul 18, 13:00 UTC | Jul 19, 11:00 UTC | 22h 0m |
| 2026-07-17 | SBI5204 | - | Jul 17, 12:40 UTC | Jul 18, 05:10 UTC | 16h 31m |
| 2026-07-17 | SBI6327 | - | Jul 17, 06:25 UTC | Jul 18, 05:10 UTC | 22h 46m |
| 2026-07-16 | SBI6327 | - | Jul 16, 12:05 UTC | Jul 17, 07:00 UTC | 18h 55m |
| 2026-07-16 | SBI6420 | - | Jul 16, 11:54 UTC | Jul 17, 07:00 UTC | 19h 5m |
| 2026-07-15 | SBI6419 | - | Jul 15, 20:50 UTC | Jul 16, 12:34 UTC | 15h 45m |
| 2026-07-15 | SBI6419 | - | Jul 15, 15:45 UTC | Jul 16, 12:34 UTC | 20h 50m |
| 2026-07-15 | SBI6419 | - | Jul 15, 10:05 UTC | Jul 16, 06:20 UTC | 20h 15m |
| 2026-07-15 | SBI6415 | - | Jul 15, 04:35 UTC | Jul 15, 21:05 UTC | 16h 30m |
| 2026-07-14 | SBI6415 | - | Jul 14, 22:05 UTC | Jul 15, 21:05 UTC | 22h 59m |
| 2026-07-14 | SBI6311 | - | Jul 14, 19:45 UTC | Jul 14, 19:55 UTC | 10m |
| 2026-07-14 | SBI6413 | - | Jul 14, 08:05 UTC | Jul 14, 14:30 UTC | 6h 25m |
| 2026-07-13 | SBI6242 | - | Jul 13, 19:10 UTC | Jul 13, 19:20 UTC | 10m |
| 2026-07-12 | SBI6246 | - | Jul 12, 18:50 UTC | Jul 13, 00:15 UTC | 5h 25m |
| 2026-07-11 | SBI5207 | OVB → VVO | Jul 11, 19:10 UTC | Jul 11, 19:45 UTC | 35m |
| 2026-07-11 | SBI5864 | - | Jul 11, 11:45 UTC | Jul 11, 13:25 UTC | 1h 40m |
| 2026-07-11 | SBI5863 | - | Jul 11, 09:30 UTC | Jul 11, 10:10 UTC | 40m |
| 2026-07-11 | SBI5266 | - | Jul 11, 01:40 UTC | Jul 11, 02:15 UTC | 35m |
| 2026-07-10 | SBI5250 | - | Jul 10, 05:30 UTC | Jul 10, 15:05 UTC | 9h 35m |
| 2026-07-09 | SBI5250 | - | Jul 9, 06:30 UTC | Jul 10, 06:00 UTC | 23h 30m |
| 2026-07-08 | SBI6245 | - | Jul 8, 18:45 UTC | Jul 9, 06:35 UTC | 11h 50m |
| 2026-07-08 | SBI6245 | - | Jul 8, 06:15 UTC | Jul 9, 04:20 UTC | 22h 5m |
| 2026-07-06 | SBI6202 | - | Jul 6, 19:15 UTC | Jul 7, 06:45 UTC | 11h 30m |
| 2026-07-04 | SBI6319 | - | Jul 4, 13:40 UTC | Jul 4, 18:45 UTC | 5h 5m |
| 2026-07-04 | SBI6410 | - | Jul 4, 11:25 UTC | Jul 4, 11:40 UTC | 15m |
| 2026-07-04 | SBI6410 | - | Jul 4, 09:50 UTC | Jul 4, 10:05 UTC | 15m |
| 2026-07-03 | SBI6409 | - | Jul 3, 21:55 UTC | Jul 4, 07:10 UTC | 9h 15m |
| 2026-07-03 | SBI6311 | - | Jul 3, 19:45 UTC | Jul 3, 19:55 UTC | 10m |
| 2026-07-03 | SBI6327 | - | Jul 3, 07:15 UTC | Jul 3, 13:50 UTC | 6h 35m |
| 2026-07-02 | SBI6327 | - | Jul 2, 12:05 UTC | Jul 3, 08:35 UTC | 20h 30m |
| 2026-07-02 | SBI6327 | - | Jul 2, 11:50 UTC | Jul 3, 08:35 UTC | 20h 45m |
| 2026-07-01 | SBI6420 | - | Jul 1, 21:50 UTC | Jul 2, 12:30 UTC | 14h 40m |
| 2026-07-01 | SBI6311 | - | Jul 1, 19:35 UTC | Jul 1, 19:45 UTC | 10m |
| 2026-07-01 | SBI6327 | - | Jul 1, 06:55 UTC | Jul 1, 13:25 UTC | 6h 30m |
| 2026-06-30 | SBI6319 | - | Jun 30, 21:10 UTC | Jun 30, 21: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-73360 page for operator, model, and routing details .