sensors Mode-S transponder
151F12
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73490 · AIRBUS A-321
- Hex
- 151F12
- Octal
- 05217422
- Decimal
- 1,384,210
- Country
- RU
- Tail
- RA-73490
- Type
- A321
- Flights observed
- 191
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- 20h ago
Last known position
Country allocation
The ICAO 24-bit address 151F12 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 |
|---|---|---|---|
| SBI5005 | - | 20 | 2026-07-09 |
| SBI5210 | - | 15 | 2026-07-10 |
| SBI5224 | - | 14 | 2026-07-07 |
| SBI5006 | S7 Airlines (Siberia Airlines) | 14 | 2026-07-09 |
| SBI3236 | S7 Airlines (Siberia Airlines) | 14 | 2026-07-04 |
| SBI3235 | - | 10 | 2026-06-30 |
| SBI2504 | S7 Airlines (Siberia Airlines) | 10 | 2026-05-22 |
| SBI5223 | - | 8 | 2026-07-11 |
| SBI5592 | - | 7 | 2026-07-11 |
| SBI5591 | - | 7 | 2026-07-11 |
| SBI5007 | S7 Airlines (Siberia Airlines) | 7 | 2026-07-05 |
| SBI2513 | S7 Airlines (Siberia Airlines) | 6 | 2026-06-14 |
| SBI2502 | S7 Airlines (Siberia Airlines) | 6 | 2026-06-12 |
| SBI5545 | S7 Airlines (Siberia Airlines) | 5 | 2026-05-29 |
| SBI2572 | - | 5 | 2026-07-13 |
| SBI5546 | S7 Airlines (Siberia Airlines) | 4 | 2026-06-17 |
| SBI5541 | S7 Airlines (Siberia Airlines) | 4 | 2026-05-31 |
| SBI5209 | S7 Airlines (Siberia Airlines) | 4 | 2026-05-24 |
| SBI2519 | - | 4 | 2026-07-05 |
| SBI5566 | S7 Airlines (Siberia Airlines) | 2 | 2026-06-04 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | SBI2572 | - | Jul 13, 01:15 UTC | Jul 13, 05:45 UTC | 4h 30m |
| 2026-07-12 | SBI2572 | - | Jul 12, 10:10 UTC | Jul 13, 05:45 UTC | 19h 35m |
| 2026-07-11 | SBI5223 | - | Jul 11, 19:15 UTC | Jul 12, 10:25 UTC | 15h 10m |
| 2026-07-11 | SBI5592 | - | Jul 11, 11:50 UTC | Jul 11, 12:20 UTC | 30m |
| 2026-07-11 | SBI5591 | - | Jul 11, 09:40 UTC | Jul 11, 10:00 UTC | 20m |
| 2026-07-10 | SBI5210 | - | Jul 10, 17:55 UTC | Jul 11, 03:15 UTC | 9h 20m |
| 2026-07-10 | SBI5565 | - | Jul 10, 07:50 UTC | Jul 10, 13:25 UTC | 5h 35m |
| 2026-07-09 | SBI5211 | - | Jul 9, 19:35 UTC | Jul 10, 04:55 UTC | 9h 20m |
| 2026-07-09 | SBI5006 | LED → OVB | Jul 9, 13:10 UTC | Jul 9, 14:15 UTC | 1h 5m |
| 2026-07-09 | SBI5005 | - | Jul 9, 10:05 UTC | Jul 9, 10:25 UTC | 20m |
| 2026-07-07 | SBI5245 | - | Jul 7, 18:45 UTC | Jul 8, 02:40 UTC | 7h 55m |
| 2026-07-07 | SBI5006 | LED → OVB | Jul 7, 13:05 UTC | Jul 7, 13:30 UTC | 25m |
| 2026-07-07 | SBI5224 | - | Jul 7, 01:25 UTC | Jul 7, 02:00 UTC | 35m |
| 2026-07-05 | SBI5229 | - | Jul 5, 22:25 UTC | Jul 6, 03:25 UTC | 5h 0m |
| 2026-07-05 | SBI5008 | - | Jul 5, 16:30 UTC | Jul 5, 16:55 UTC | 25m |
| 2026-07-05 | SBI5007 | OVB → LED | Jul 5, 14:30 UTC | Jul 5, 14:50 UTC | 20m |
| 2026-07-05 | SBI2519 | - | Jul 5, 06:00 UTC | Jul 5, 13:45 UTC | 7h 45m |
| 2026-07-04 | SBI3236 | ASB → DME | Jul 4, 16:35 UTC | Jul 4, 16:50 UTC | 15m |
| 2026-07-04 | SBI3236 | ASB → DME | Jul 4, 08:55 UTC | Jul 4, 15:50 UTC | 6h 55m |
| 2026-07-02 | SBI5224 | - | Jul 2, 19:00 UTC | Jul 3, 01:30 UTC | 6h 30m |
| 2026-07-02 | SBI5006 | LED → OVB | Jul 2, 12:55 UTC | Jul 2, 13:20 UTC | 25m |
| 2026-07-02 | SBI5005 | - | Jul 2, 10:05 UTC | Jul 2, 10:20 UTC | 15m |
| 2026-06-30 | SBI3235 | - | Jun 30, 08:00 UTC | Jun 30, 08:35 UTC | 35m |
| 2026-06-28 | SBI2572 | - | Jun 28, 04:59 UTC | Jun 28, 20:45 UTC | 15h 45m |
| 2026-06-28 | SBI2572 | - | Jun 28, 00:35 UTC | Jun 28, 20:45 UTC | 20h 10m |
| 2026-06-28 | SBI2572 | - | Jun 28, 00:15 UTC | Jun 28, 20:45 UTC | 20h 30m |
| 2026-06-27 | SBI3235 | - | Jun 27, 08:39 UTC | Jun 27, 08:55 UTC | 15m |
| 2026-06-25 | SBI5224 | - | Jun 25, 18:55 UTC | Jun 26, 01:29 UTC | 6h 35m |
| 2026-06-25 | SBI5005 | - | Jun 25, 09:29 UTC | Jun 25, 14:20 UTC | 4h 50m |
| 2026-06-24 | SBI3236 | ASB → DME | Jun 24, 16:05 UTC | Jun 24, 16:29 UTC | 25m |
| 2026-06-24 | SBI3235 | - | Jun 24, 07:59 UTC | Jun 24, 14:20 UTC | 6h 20m |
| 2026-06-23 | SBI3236 | ASB → DME | Jun 23, 16:39 UTC | Jun 23, 16:50 UTC | 10m |
| 2026-06-23 | SBI3235 | - | Jun 23, 08:15 UTC | Jun 23, 14:49 UTC | 6h 35m |
| 2026-06-21 | SBI5224 | - | Jun 21, 08:30 UTC | Jun 22, 01:55 UTC | 17h 25m |
| 2026-06-20 | SBI5212 | - | Jun 20, 19:49 UTC | Jun 21, 04:44 UTC | 8h 55m |
| 2026-06-20 | SBI5006 | LED → OVB | Jun 20, 12:54 UTC | Jun 20, 13:14 UTC | 20m |
| 2026-06-20 | SBI5005 | - | Jun 20, 09:44 UTC | Jun 20, 11:25 UTC | 1h 40m |
| 2026-06-19 | SBI5246 | - | Jun 19, 08:29 UTC | Jun 20, 02:29 UTC | 18h 0m |
| 2026-06-17 | SBI5546 | OSS → OVB | Jun 17, 08:45 UTC | Jun 17, 13:55 UTC | 5h 10m |
| 2026-06-14 | SBI2513 | DME → OVB | Jun 14, 20:30 UTC | Jun 14, 20:45 UTC | 15m |
| 2026-06-14 | SBI3235 | DME → ASB | Jun 14, 10:05 UTC | Jun 14, 17:05 UTC | 7h 0m |
| 2026-06-13 | SBI5007 | OVB → LED | Jun 13, 14:00 UTC | Jun 13, 14:20 UTC | 20m |
| 2026-06-13 | SBI5007 | OVB → LED | Jun 13, 01:10 UTC | Jun 13, 13:15 UTC | 12h 4m |
| 2026-06-12 | SBI5007 | OVB → LED | Jun 12, 12:50 UTC | Jun 13, 05:10 UTC | 16h 20m |
| 2026-06-12 | SBI2519 | DME → OVB | Jun 12, 06:05 UTC | Jun 13, 01:10 UTC | 19h 5m |
| 2026-06-12 | SBI2519 | DME → OVB | Jun 12, 05:15 UTC | Jun 12, 05:25 UTC | 10m |
| 2026-06-12 | SBI2502 | OVB → DME | Jun 12, 02:40 UTC | Jun 12, 02:50 UTC | 10m |
| 2026-06-11 | SBI5555 | OVB → LBD | Jun 11, 07:00 UTC | Jun 11, 12:30 UTC | 5h 30m |
| 2026-06-10 | SBI5210 | BQS → OVB | Jun 10, 18:50 UTC | Jun 11, 03:40 UTC | 8h 50m |
| 2026-06-09 | SBI5592 | EVN → OVB | Jun 9, 12:05 UTC | Jun 10, 03:10 UTC | 15h 5m |
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-73490 page for operator, model, and routing details .