sensors Mode-S transponder
151F11
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73489 · BOEING 737-800
- Hex
- 151F11
- Octal
- 05217421
- Decimal
- 1,384,209
- Country
- RU
- Tail
- RA-73489
- Type
- B738
- Flights observed
- 117
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 151F11 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 |
|---|---|---|---|
| SBI6409 | - | 14 | 2026-07-08 |
| SBI5246 | S7 Airlines (Siberia Airlines) | 9 | 2026-05-06 |
| SBI6419 | - | 8 | 2026-07-09 |
| SBI5204 | S7 Airlines (Siberia Airlines) | 7 | 2026-06-07 |
| SBI5203 | S7 Airlines (Siberia Airlines) | 6 | 2026-06-17 |
| SBI5103 | S7 Airlines (Siberia Airlines) | 6 | 2026-05-16 |
| SBI5242 | - | 5 | 2026-06-26 |
| SBI5208 | - | 5 | 2026-06-25 |
| SBI5211 | S7 Airlines (Siberia Airlines) | 4 | 2026-06-18 |
| SBI6420 | - | 3 | 2026-07-09 |
| SBI6415 | - | 3 | 2026-07-05 |
| SBI5245 | S7 Airlines (Siberia Airlines) | 3 | 2026-05-05 |
| SBI5241 | - | 3 | 2026-06-22 |
| SBI5240 | S7 Airlines (Siberia Airlines) | 3 | 2026-06-06 |
| SBI5207 | S7 Airlines (Siberia Airlines) | 3 | 2026-06-21 |
| SBI2510 | S7 Airlines (Siberia Airlines) | 3 | 2026-06-10 |
| SBI6410 | - | 2 | 2026-07-06 |
| SBI5263 | S7 Airlines (Siberia Airlines) | 2 | 2026-07-10 |
| SBI5229 | S7 Airlines (Siberia Airlines) | 2 | 2026-04-28 |
| SBI5212 | S7 Airlines (Siberia Airlines) | 2 | 2026-05-18 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | SBI5001 | - | Jul 13, 08:35 UTC | Jul 13, 08:45 UTC | 10m |
| 2026-07-12 | SBI5205 | - | Jul 12, 14:05 UTC | Jul 13, 01:40 UTC | 11h 35m |
| 2026-07-10 | SBI5263 | OVB → YKS | Jul 10, 19:00 UTC | Jul 11, 02:55 UTC | 7h 56m |
| 2026-07-09 | SBI6420 | - | Jul 9, 12:10 UTC | Jul 10, 04:15 UTC | 16h 5m |
| 2026-07-09 | SBI6420 | - | Jul 9, 06:20 UTC | Jul 10, 04:15 UTC | 21h 55m |
| 2026-07-09 | SBI6419 | - | Jul 9, 05:55 UTC | Jul 10, 04:15 UTC | 22h 20m |
| 2026-07-08 | SBI6409 | - | Jul 8, 06:20 UTC | Jul 9, 06:15 UTC | 23h 55m |
| 2026-07-08 | SBI6409 | - | Jul 8, 03:30 UTC | Jul 8, 07:00 UTC | 3h 30m |
| 2026-07-07 | SBI6409 | - | Jul 7, 11:00 UTC | Jul 8, 07:00 UTC | 20h 0m |
| 2026-07-07 | SBI6409 | - | Jul 7, 03:30 UTC | Jul 7, 07:00 UTC | 3h 30m |
| 2026-07-06 | SBI6410 | - | Jul 6, 10:30 UTC | Jul 6, 10:40 UTC | 10m |
| 2026-07-06 | SBI6409 | - | Jul 6, 03:30 UTC | Jul 6, 07:10 UTC | 3h 40m |
| 2026-07-05 | SBI6409 | - | Jul 5, 10:20 UTC | Jul 6, 07:10 UTC | 20h 50m |
| 2026-07-05 | SBI6409 | - | Jul 5, 10:10 UTC | Jul 6, 07:10 UTC | 21h 0m |
| 2026-07-05 | SBI6415 | - | Jul 5, 04:30 UTC | Jul 6, 04:00 UTC | 23h 30m |
| 2026-07-04 | SBI6415 | - | Jul 4, 12:20 UTC | Jul 5, 10:50 UTC | 22h 30m |
| 2026-07-04 | SBI6415 | - | Jul 4, 11:50 UTC | Jul 5, 10:15 UTC | 22h 25m |
| 2026-07-04 | SBI6419 | - | Jul 4, 05:20 UTC | Jul 4, 12:30 UTC | 7h 10m |
| 2026-07-03 | SBI6409 | - | Jul 3, 06:25 UTC | Jul 4, 06:10 UTC | 23h 45m |
| 2026-07-02 | SBI6409 | - | Jul 2, 13:25 UTC | Jul 3, 08:10 UTC | 18h 45m |
| 2026-07-02 | SBI6410 | - | Jul 2, 05:50 UTC | Jul 2, 13:50 UTC | 8h 0m |
| 2026-07-01 | SBI5225 | - | Jul 1, 08:55 UTC | Jul 2, 06:15 UTC | 21h 20m |
| 2026-06-30 | SBI5266 | - | Jun 30, 14:30 UTC | Jul 1, 01:50 UTC | 11h 20m |
| 2026-06-26 | SBI5242 | - | Jun 26, 21:59 UTC | Jun 27, 04:49 UTC | 6h 50m |
| 2026-06-25 | SBI5208 | - | Jun 25, 19:09 UTC | Jun 26, 06:54 UTC | 11h 45m |
| 2026-06-24 | SBI5208 | - | Jun 24, 19:39 UTC | Jun 25, 07:25 UTC | 11h 45m |
| 2026-06-23 | SBI5105 | OVB → AER | Jun 23, 10:55 UTC | Jun 24, 03:15 UTC | 16h 20m |
| 2026-06-22 | SBI5241 | - | Jun 22, 22:10 UTC | Jun 23, 04:39 UTC | 6h 30m |
| 2026-06-21 | SBI5207 | OVB → VVO | Jun 21, 18:39 UTC | Jun 21, 19:20 UTC | 40m |
| 2026-06-19 | SBI5241 | - | Jun 19, 22:09 UTC | Jun 20, 04:39 UTC | 6h 30m |
| 2026-06-18 | SBI5211 | OVB → BQS | Jun 18, 19:50 UTC | Jun 18, 20:20 UTC | 30m |
| 2026-06-17 | SBI5203 | OVB → VVO | Jun 17, 16:25 UTC | Jun 18, 04:25 UTC | 12h 0m |
| 2026-06-16 | SBI5242 | - | Jun 16, 22:05 UTC | Jun 17, 05:05 UTC | 7h 0m |
| 2026-06-15 | SBI5211 | OVB → BQS | Jun 15, 19:30 UTC | Jun 16, 04:55 UTC | 9h 25m |
| 2026-06-14 | SBI5208 | - | Jun 14, 19:05 UTC | Jun 15, 06:49 UTC | 11h 45m |
| 2026-06-13 | SBI5224 | - | Jun 13, 14:05 UTC | Jun 14, 01:30 UTC | 11h 25m |
| 2026-06-12 | SBI5208 | VVO → OVB | Jun 12, 18:50 UTC | Jun 13, 06:35 UTC | 11h 44m |
| 2026-06-11 | SBI5242 | MJZ → OVB | Jun 11, 21:30 UTC | Jun 12, 04:05 UTC | 6h 35m |
| 2026-06-11 | SBI5242 | MJZ → OVB | Jun 11, 04:25 UTC | Jun 12, 04:05 UTC | 23h 41m |
| 2026-06-10 | SBI5211 | OVB → BQS | Jun 10, 19:35 UTC | Jun 11, 04:55 UTC | 9h 20m |
| 2026-06-10 | SBI2509 | DME → OVB | Jun 10, 13:55 UTC | Jun 10, 14:05 UTC | 10m |
| 2026-06-10 | SBI2510 | OVB → DME | Jun 10, 11:50 UTC | Jun 10, 12:05 UTC | 15m |
| 2026-06-09 | SBI5207 | OVB → VVO | Jun 9, 18:50 UTC | Jun 10, 06:50 UTC | 12h 0m |
| 2026-06-08 | SBI5284 | PWE → OVB | Jun 8, 21:50 UTC | Jun 9, 10:20 UTC | 12h 30m |
| 2026-06-08 | SBI5129 | OVB → MRV | Jun 8, 10:50 UTC | Jun 8, 11:40 UTC | 50m |
| 2026-06-07 | SBI5204 | VVO → OVB | Jun 7, 16:30 UTC | Jun 8, 04:40 UTC | 12h 10m |
| 2026-06-07 | SBI5065 | OVB → KGD | Jun 7, 07:15 UTC | Jun 7, 07:55 UTC | 40m |
| 2026-06-06 | SBI5240 | IKT → OVB | Jun 6, 11:30 UTC | Jun 7, 01:04 UTC | 13h 35m |
| 2026-06-05 | SBI5242 | MJZ → OVB | Jun 5, 22:10 UTC | Jun 6, 04:45 UTC | 6h 35m |
| 2026-06-05 | SBI2509 | DME → OVB | Jun 5, 14:55 UTC | Jun 5, 15:30 UTC | 35m |
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-73489 page for operator, model, and routing details .