sensors Mode-S transponder
151DDE
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73182 · BOEING 737-800
- Hex
- 151DDE
- Octal
- 05216736
- Decimal
- 1,383,902
- Country
- RU
- Tail
- RA-73182
- Type
- B738
- Flights observed
- 207
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- Jul 26, 14:05 UTC
Last known position
Country allocation
The ICAO 24-bit address 151DDE 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 |
|---|---|---|---|
| SBI3032 | - | 20 | 2026-07-17 |
| SBI3022 | - | 13 | 2026-06-27 |
| SBI3031 | - | 11 | 2026-07-16 |
| SBI3034 | - | 10 | 2026-06-20 |
| SBI3017 | S7 Airlines (Siberia Airlines) | 10 | 2026-05-25 |
| SBI3746 | S7 Airlines (Siberia Airlines) | 8 | 2026-07-24 |
| SBI3745 | - | 8 | 2026-07-12 |
| SBI3021 | S7 Airlines (Siberia Airlines) | 8 | 2026-07-26 |
| SBI3018 | - | 7 | 2026-07-04 |
| SBI2606 | S7 Airlines (Siberia Airlines) | 6 | 2026-07-24 |
| SBI2582 | - | 6 | 2026-06-29 |
| SBI2572 | - | 6 | 2026-07-06 |
| SBI2565 | - | 6 | 2026-06-25 |
| SBI3748 | S7 Airlines (Siberia Airlines) | 5 | 2026-07-02 |
| SBI2571 | - | 5 | 2026-07-05 |
| SBI1214 | S7 Airlines (Siberia Airlines) | 5 | 2026-06-08 |
| SBI2593 | - | 4 | 2026-06-21 |
| SBI5115 | S7 Airlines (Siberia Airlines) | 3 | 2026-06-06 |
| SBI3749 | - | 3 | 2026-06-25 |
| SBI3747 | S7 Airlines (Siberia Airlines) | 3 | 2026-07-02 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | SBI3021 | DME → IKT | Jul 26, 13:20 UTC | Jul 26, 14:05 UTC | 45m |
| 2026-07-26 | SBI3042 | BTK → DME | Jul 26, 08:05 UTC | Jul 26, 08:20 UTC | 15m |
| 2026-07-25 | SBI2153 | DME → OGZ | Jul 25, 09:00 UTC | Jul 25, 09:15 UTC | 15m |
| 2026-07-24 | SBI3746 | AYT → DME | Jul 24, 13:10 UTC | Jul 25, 03:40 UTC | 14h 30m |
| 2026-07-24 | SBI2606 | KEJ → DME | Jul 24, 01:05 UTC | Jul 24, 11:50 UTC | 10h 45m |
| 2026-07-23 | SBI2605 | DME → KEJ | Jul 23, 23:10 UTC | Jul 23, 23:45 UTC | 35m |
| 2026-07-22 | SBI5236 | IKT → OVB | Jul 22, 11:10 UTC | Jul 22, 21:10 UTC | 10h 0m |
| 2026-07-22 | SBI5236 | IKT → OVB | Jul 22, 00:45 UTC | Jul 22, 21:10 UTC | 20h 25m |
| 2026-07-20 | SBI5565 | - | Jul 20, 07:45 UTC | Jul 20, 14:15 UTC | 6h 30m |
| 2026-07-19 | SBI5303 | - | Jul 19, 23:55 UTC | Jul 20, 05:20 UTC | 5h 25m |
| 2026-07-19 | SBI1074 | KUF → DME | Jul 19, 14:20 UTC | Jul 19, 14:35 UTC | 15m |
| 2026-07-18 | SBI3021 | - | Jul 18, 13:25 UTC | Jul 19, 06:45 UTC | 17h 20m |
| 2026-07-18 | SBI2606 | KEJ → DME | Jul 18, 02:40 UTC | Jul 18, 14:05 UTC | 11h 26m |
| 2026-07-17 | SBI2514 | OVB → DME | Jul 17, 05:35 UTC | Jul 18, 01:30 UTC | 19h 55m |
| 2026-07-17 | SBI2514 | OVB → DME | Jul 17, 05:04 UTC | Jul 18, 01:30 UTC | 20h 25m |
| 2026-07-17 | SBI3032 | - | Jul 17, 02:34 UTC | Jul 18, 01:30 UTC | 22h 55m |
| 2026-07-16 | SBI3032 | - | Jul 16, 21:35 UTC | Jul 17, 17:05 UTC | 19h 30m |
| 2026-07-16 | SBI3032 | - | Jul 16, 21:25 UTC | Jul 17, 17:05 UTC | 19h 40m |
| 2026-07-16 | SBI3031 | - | Jul 16, 18:05 UTC | Jul 16, 18:19 UTC | 15m |
| 2026-07-16 | SBI8991 | - | Jul 16, 05:45 UTC | Jul 16, 05:55 UTC | 10m |
| 2026-07-15 | SBI5264 | - | Jul 15, 18:35 UTC | Jul 16, 02:55 UTC | 8h 20m |
| 2026-07-14 | SBI5232 | - | Jul 14, 21:55 UTC | Jul 15, 02:50 UTC | 4h 54m |
| 2026-07-14 | SBI1004 | - | Jul 14, 09:15 UTC | Jul 14, 09:40 UTC | 25m |
| 2026-07-13 | SBI1005 | - | Jul 13, 15:15 UTC | Jul 13, 15:25 UTC | 10m |
| 2026-07-13 | SBI2145 | - | Jul 13, 08:40 UTC | Jul 13, 09:00 UTC | 20m |
| 2026-07-12 | SBI3746 | AYT → DME | Jul 12, 12:05 UTC | Jul 13, 03:10 UTC | 15h 5m |
| 2026-07-12 | SBI3745 | - | Jul 12, 00:40 UTC | Jul 12, 10:50 UTC | 10h 10m |
| 2026-07-11 | SBI3746 | AYT → DME | Jul 11, 12:10 UTC | Jul 11, 13:50 UTC | 1h 40m |
| 2026-07-11 | SBI3745 | - | Jul 11, 10:15 UTC | Jul 11, 10:40 UTC | 25m |
| 2026-07-09 | SBI3032 | - | Jul 9, 21:25 UTC | Jul 10, 03:15 UTC | 5h 50m |
| 2026-07-09 | SBI5264 | - | Jul 9, 02:10 UTC | Jul 9, 21:55 UTC | 19h 45m |
| 2026-07-08 | SBI5263 | OVB → YKS | Jul 8, 18:30 UTC | Jul 9, 02:40 UTC | 8h 10m |
| 2026-07-06 | SBI2572 | - | Jul 6, 00:05 UTC | Jul 6, 15:30 UTC | 15h 25m |
| 2026-07-05 | SBI2571 | - | Jul 5, 03:35 UTC | Jul 6, 01:00 UTC | 21h 25m |
| 2026-07-05 | SBI2571 | - | Jul 5, 02:55 UTC | Jul 6, 01:00 UTC | 22h 5m |
| 2026-07-04 | SBI3018 | - | Jul 4, 22:00 UTC | Jul 5, 03:40 UTC | 5h 40m |
| 2026-07-04 | SBI3040 | - | Jul 4, 03:50 UTC | Jul 5, 03:30 UTC | 23h 40m |
| 2026-07-03 | SBI3039 | - | Jul 3, 22:40 UTC | Jul 4, 04:35 UTC | 5h 55m |
| 2026-07-02 | SBI3748 | AYT → DME | Jul 2, 14:20 UTC | Jul 2, 16:05 UTC | 1h 45m |
| 2026-07-02 | SBI3747 | DME → AYT | Jul 2, 12:10 UTC | Jul 2, 12:45 UTC | 35m |
| 2026-07-02 | SBI3032 | - | Jul 2, 06:55 UTC | Jul 2, 07:05 UTC | 10m |
| 2026-07-01 | SBI3032 | - | Jul 1, 21:50 UTC | Jul 2, 03:25 UTC | 5h 35m |
| 2026-06-30 | SBI3748 | AYT → DME | Jun 30, 14:25 UTC | Jun 30, 16:15 UTC | 1h 50m |
| 2026-06-29 | SBI2582 | - | Jun 29, 22:24 UTC | Jun 30, 13:10 UTC | 14h 46m |
| 2026-06-27 | SBI3022 | - | Jun 27, 13:24 UTC | Jun 28, 05:29 UTC | 16h 5m |
| 2026-06-27 | SBI3022 | - | Jun 27, 06:59 UTC | Jun 28, 05:29 UTC | 22h 30m |
| 2026-06-26 | SBI3021 | - | Jun 26, 23:30 UTC | Jun 27, 14:09 UTC | 14h 40m |
| 2026-06-25 | SBI2565 | - | Jun 25, 20:59 UTC | Jun 25, 21:10 UTC | 10m |
| 2026-06-25 | SBI3750 | IST → DME | Jun 25, 13:55 UTC | Jun 25, 14:29 UTC | 35m |
| 2026-06-25 | SBI3749 | - | Jun 25, 12:04 UTC | Jun 25, 12:19 UTC | 15m |
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-73182 page for operator, model, and routing details .