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
- 155
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- 6h ago
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 |
|---|---|---|---|
| SBI6327 | - | 8 | 2026-07-03 |
| SBI6419 | - | 7 | 2026-06-30 |
| SBI6311 | - | 7 | 2026-07-03 |
| SBI5250 | - | 7 | 2026-07-10 |
| SBI6409 | - | 6 | 2026-07-03 |
| SBI6318 | S7 Airlines (Siberia Airlines) | 5 | 2026-05-08 |
| SBI6317 | S7 Airlines (Siberia Airlines) | 5 | 2026-05-08 |
| SBI6328 | S7 Airlines (Siberia Airlines) | 4 | 2026-05-06 |
| SBI6312 | S7 Airlines (Siberia Airlines) | 4 | 2026-05-06 |
| SBI6310 | - | 4 | 2026-06-27 |
| SBI6309 | - | 4 | 2026-06-26 |
| SBI6245 | - | 4 | 2026-07-08 |
| SBI5863 | - | 4 | 2026-07-11 |
| SBI5732 | S7 Airlines (Siberia Airlines) | 4 | 2026-05-18 |
| SBI6420 | - | 3 | 2026-07-01 |
| SBI6415 | S7 Airlines (Siberia Airlines) | 3 | 2026-04-15 |
| SBI6410 | - | 3 | 2026-07-04 |
| SBI6306 | S7 Airlines (Siberia Airlines) | 3 | 2026-04-21 |
| SBI5889 | - | 3 | 2026-06-20 |
| SBI5864 | - | 3 | 2026-07-11 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | SBI6413 | - | Jul 14, 08:05 UTC | Jul 14, 08:45 UTC | 40m |
| 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 |
| 2026-06-30 | SBI6419 | - | Jun 30, 05:30 UTC | Jun 30, 18:55 UTC | 13h 25m |
| 2026-06-29 | SBI6420 | - | Jun 29, 12:09 UTC | Jun 30, 12:00 UTC | 23h 51m |
| 2026-06-29 | SBI6419 | - | Jun 29, 06:05 UTC | Jun 30, 06:00 UTC | 23h 56m |
| 2026-06-29 | SBI6419 | - | Jun 29, 05:30 UTC | Jun 29, 12:49 UTC | 7h 20m |
| 2026-06-28 | SBI6419 | - | Jun 28, 14:04 UTC | Jun 29, 12:49 UTC | 22h 45m |
| 2026-06-28 | SBI6419 | - | Jun 28, 13:49 UTC | Jun 29, 06:14 UTC | 16h 25m |
| 2026-06-28 | SBI6419 | - | Jun 28, 10:04 UTC | Jun 29, 06:14 UTC | 20h 10m |
| 2026-06-28 | SBI6409 | - | Jun 28, 07:40 UTC | Jun 28, 07:54 UTC | 15m |
| 2026-06-28 | SBI6409 | - | Jun 28, 06:24 UTC | Jun 28, 07:09 UTC | 45m |
| 2026-06-27 | SBI6310 | - | Jun 27, 10:25 UTC | Jun 28, 07:09 UTC | 20h 45m |
| 2026-06-26 | SBI6309 | - | Jun 26, 21:50 UTC | Jun 27, 08:39 UTC | 10h 50m |
| 2026-06-26 | SBI6311 | - | Jun 26, 19:45 UTC | Jun 26, 19:55 UTC | 10m |
| 2026-06-25 | SBI6420 | UFA → IKT | Jun 25, 05:29 UTC | Jun 25, 14:14 UTC | 8h 45m |
| 2026-06-24 | SBI6419 | - | Jun 24, 13:50 UTC | Jun 25, 06:09 UTC | 16h 20m |
| 2026-06-24 | SBI6409 | - | Jun 24, 06:04 UTC | Jun 25, 06:00 UTC | 23h 55m |
| 2026-06-23 | SBI6409 | - | Jun 23, 22:19 UTC | Jun 24, 13:50 UTC | 15h 30m |
| 2026-06-22 | SBI5205 | - | Jun 22, 14:05 UTC | Jun 23, 01:59 UTC | 11h 55m |
| 2026-06-21 | SBI5212 | - | Jun 21, 20:00 UTC | Jun 22, 04:49 UTC | 8h 50m |
| 2026-06-20 | SBI5264 | YKS → OVB | Jun 20, 18:10 UTC | Jun 21, 02:24 UTC | 8h 15m |
| 2026-06-20 | SBI5889 | - | Jun 20, 09:05 UTC | Jun 20, 09:24 UTC | 20m |
| 2026-06-18 | SBI5207 | OVB → VVO | Jun 18, 19:05 UTC | Jun 19, 07:14 UTC | 12h 9m |
| 2026-06-18 | SBI5890 | IST → OVB | Jun 18, 10:55 UTC | Jun 18, 11:25 UTC | 30m |
| 2026-06-18 | SBI5889 | OVB → IST | Jun 18, 08:45 UTC | Jun 18, 09:05 UTC | 20m |
| 2026-06-17 | SBI5240 | - | Jun 17, 07:20 UTC | Jun 18, 01:10 UTC | 17h 50m |
| 2026-06-16 | SBI5248 | NER → OVB | Jun 16, 20:05 UTC | Jun 17, 04:35 UTC | 8h 30m |
| 2026-06-15 | SBI5242 | MJZ → OVB | Jun 15, 11:39 UTC | Jun 16, 04:39 UTC | 17h 0m |
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 .