sensors Mode-S transponder
151F14
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73492 · AIRBUS A-320neo
- Hex
- 151F14
- Octal
- 05217424
- Decimal
- 1,384,212
- Country
- RU
- Tail
- RA-73492
- Type
- A20N
- Flights observed
- 128
- Distinct callsigns
- 14
- Country
- RU
- Last broadcast
- Jul 26, 20:25 UTC
Last known position
Country allocation
The ICAO 24-bit address 151F14 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 14 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| SBI3006 | S7 Airlines (Siberia Airlines) | 44 | 2026-07-24 |
| SBI3046 | - | 21 | 2026-07-16 |
| SBI3045 | - | 18 | 2026-07-16 |
| SBI3005 | S7 Airlines (Siberia Airlines) | 12 | 2026-07-26 |
| SBI3060 | - | 10 | 2026-06-30 |
| SBI3048 | S7 Airlines (Siberia Airlines) | 6 | 2026-07-22 |
| SBI3047 | S7 Airlines (Siberia Airlines) | 4 | 2026-07-21 |
| SBI3031 | - | 4 | 2026-06-22 |
| SBI3062 | S7 Airlines (Siberia Airlines) | 2 | 2026-05-31 |
| SBI3059 | S7 Airlines (Siberia Airlines) | 2 | 2026-06-01 |
| SBI3040 | - | 2 | 2026-07-12 |
| SBI3061 | S7 Airlines (Siberia Airlines) | 1 | 2026-05-26 |
| SBI3042 | - | 1 | 2026-06-28 |
| SBI3032 | - | 1 | 2026-06-23 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | SBI3005 | DME → YKS | Jul 26, 18:35 UTC | Jul 26, 20:25 UTC | 1h 50m |
| 2026-07-24 | SBI3006 | YKS → DME | Jul 24, 06:00 UTC | Jul 24, 20:40 UTC | 14h 40m |
| 2026-07-23 | SBI3006 | YKS → DME | Jul 23, 07:05 UTC | Jul 24, 07:00 UTC | 23h 55m |
| 2026-07-22 | SBI3006 | YKS → DME | Jul 22, 20:30 UTC | Jul 23, 07:25 UTC | 10h 55m |
| 2026-07-22 | SBI3048 | HTA → DME | Jul 22, 04:35 UTC | Jul 22, 20:35 UTC | 16h 0m |
| 2026-07-21 | SBI3047 | DME → HTA | Jul 21, 18:05 UTC | Jul 22, 05:20 UTC | 11h 15m |
| 2026-07-21 | SBI3047 | DME → HTA | Jul 21, 07:05 UTC | Jul 22, 05:20 UTC | 22h 15m |
| 2026-07-21 | SBI3006 | YKS → DME | Jul 21, 06:05 UTC | Jul 22, 05:00 UTC | 22h 55m |
| 2026-07-19 | SBI3006 | YKS → DME | Jul 19, 19:35 UTC | Jul 20, 08:30 UTC | 12h 55m |
| 2026-07-19 | SBI3006 | YKS → DME | Jul 19, 05:55 UTC | Jul 19, 19:45 UTC | 13h 50m |
| 2026-07-18 | SBI3005 | - | Jul 18, 19:50 UTC | Jul 19, 06:20 UTC | 10h 30m |
| 2026-07-16 | SBI3046 | - | Jul 16, 21:25 UTC | Jul 17, 06:35 UTC | 9h 10m |
| 2026-07-16 | SBI3045 | - | Jul 16, 18:00 UTC | Jul 16, 18:19 UTC | 20m |
| 2026-07-14 | SBI3046 | - | Jul 14, 21:20 UTC | Jul 15, 06:30 UTC | 9h 9m |
| 2026-07-13 | SBI3006 | - | Jul 13, 06:05 UTC | Jul 13, 21:45 UTC | 15h 40m |
| 2026-07-12 | SBI3006 | - | Jul 12, 20:35 UTC | Jul 13, 08:25 UTC | 11h 50m |
| 2026-07-12 | SBI3040 | - | Jul 12, 03:55 UTC | Jul 12, 20:40 UTC | 16h 45m |
| 2026-07-11 | SBI3040 | - | Jul 11, 22:15 UTC | Jul 12, 20:40 UTC | 22h 25m |
| 2026-07-08 | SBI3046 | - | Jul 8, 03:45 UTC | Jul 8, 20:55 UTC | 17h 10m |
| 2026-07-07 | SBI3046 | - | Jul 7, 18:05 UTC | Jul 8, 04:30 UTC | 10h 25m |
| 2026-07-04 | SBI3006 | - | Jul 4, 19:10 UTC | Jul 5, 07:35 UTC | 12h 25m |
| 2026-07-02 | SBI3045 | - | Jul 2, 21:20 UTC | Jul 3, 04:10 UTC | 6h 50m |
| 2026-07-02 | SBI3045 | - | Jul 2, 07:05 UTC | Jul 3, 04:10 UTC | 21h 5m |
| 2026-07-02 | SBI3006 | - | Jul 2, 05:55 UTC | Jul 3, 04:10 UTC | 22h 15m |
| 2026-07-01 | SBI3006 | - | Jul 1, 20:25 UTC | Jul 2, 07:25 UTC | 11h 0m |
| 2026-07-01 | SBI3046 | - | Jul 1, 01:30 UTC | Jul 1, 20:30 UTC | 19h 0m |
| 2026-06-30 | SBI3060 | - | Jun 30, 07:20 UTC | Jul 1, 02:10 UTC | 18h 50m |
| 2026-06-28 | SBI3047 | DME → HTA | Jun 28, 20:09 UTC | Jun 29, 05:24 UTC | 9h 15m |
| 2026-06-28 | SBI3042 | - | Jun 28, 07:34 UTC | Jun 28, 07:44 UTC | 10m |
| 2026-06-26 | SBI3006 | - | Jun 26, 05:55 UTC | Jun 26, 20:29 UTC | 14h 35m |
| 2026-06-25 | SBI3006 | - | Jun 25, 18:24 UTC | Jun 26, 07:20 UTC | 12h 55m |
| 2026-06-25 | SBI3006 | - | Jun 25, 09:05 UTC | Jun 26, 07:20 UTC | 22h 15m |
| 2026-06-25 | SBI3006 | - | Jun 25, 08:04 UTC | Jun 26, 07:00 UTC | 22h 55m |
| 2026-06-24 | SBI3005 | - | Jun 24, 22:00 UTC | Jun 25, 19:39 UTC | 21h 40m |
| 2026-06-23 | SBI3046 | - | Jun 23, 23:34 UTC | Jun 24, 22:29 UTC | 22h 55m |
| 2026-06-23 | SBI3032 | - | Jun 23, 02:55 UTC | Jun 24, 00:20 UTC | 21h 25m |
| 2026-06-22 | SBI3031 | - | Jun 22, 21:30 UTC | Jun 23, 18:10 UTC | 20h 40m |
| 2026-06-22 | SBI3031 | - | Jun 22, 18:19 UTC | Jun 23, 03:39 UTC | 9h 20m |
| 2026-06-22 | SBI3031 | - | Jun 22, 03:05 UTC | Jun 23, 03:00 UTC | 23h 55m |
| 2026-06-22 | SBI3031 | - | Jun 22, 02:30 UTC | Jun 22, 22:15 UTC | 19h 45m |
| 2026-06-21 | SBI3048 | HTA → DME | Jun 21, 16:59 UTC | Jun 22, 03:14 UTC | 10h 15m |
| 2026-06-21 | SBI3048 | HTA → DME | Jun 21, 07:04 UTC | Jun 22, 03:14 UTC | 20h 10m |
| 2026-06-21 | SBI3006 | - | Jun 21, 05:54 UTC | Jun 22, 03:14 UTC | 21h 20m |
| 2026-06-20 | SBI3006 | - | Jun 20, 19:40 UTC | Jun 21, 16:59 UTC | 21h 20m |
| 2026-06-20 | SBI3005 | - | Jun 20, 05:54 UTC | Jun 20, 20:34 UTC | 14h 40m |
| 2026-06-19 | SBI3005 | - | Jun 19, 19:34 UTC | Jun 20, 06:39 UTC | 11h 5m |
| 2026-06-17 | SBI3045 | DME → HTA | Jun 17, 14:20 UTC | Jun 17, 18:05 UTC | 3h 45m |
| 2026-06-15 | SBI3006 | - | Jun 15, 19:39 UTC | Jun 16, 07:25 UTC | 11h 45m |
| 2026-06-14 | SBI3048 | HTA → DME | Jun 14, 02:05 UTC | Jun 14, 18:45 UTC | 16h 41m |
| 2026-06-13 | SBI3048 | HTA → DME | Jun 13, 20:15 UTC | Jun 14, 18:45 UTC | 22h 31m |
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-73492 page for operator, model, and routing details .