sensors Mode-S transponder
151EC0
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73408 · BOEING 737-800
- Hex
- 151EC0
- Octal
- 05217300
- Decimal
- 1,384,128
- Country
- RU
- Tail
- RA-73408
- Type
- B738
- Flights observed
- 142
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- 18h ago
Current position
Country allocation
The ICAO 24-bit address 151EC0 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 |
|---|---|---|---|
| SBI5863 | - | 15 | 2026-06-30 |
| SBI5864 | - | 9 | 2026-07-01 |
| SBI5725 | S7 Airlines (Siberia Airlines) | 7 | 2026-06-02 |
| SBI6409 | - | 6 | 2026-06-18 |
| SBI5726 | - | 6 | 2026-07-10 |
| SBI5240 | - | 6 | 2026-07-13 |
| SBI5239 | S7 Airlines (Siberia Airlines) | 6 | 2026-07-07 |
| SBI5890 | - | 5 | 2026-07-11 |
| SBI5889 | - | 5 | 2026-07-11 |
| SBI6328 | S7 Airlines (Siberia Airlines) | 4 | 2026-06-26 |
| SBI5204 | - | 4 | 2026-07-04 |
| SBI6415 | - | 3 | 2026-07-02 |
| SBI6309 | - | 3 | 2026-06-21 |
| SBI6245 | - | 3 | 2026-07-03 |
| SBI5728 | S7 Airlines (Siberia Airlines) | 3 | 2026-06-05 |
| SBI5565 | S7 Airlines (Siberia Airlines) | 3 | 2026-04-26 |
| SBI5246 | - | 3 | 2026-06-29 |
| SBI5241 | S7 Airlines (Siberia Airlines) | 3 | 2026-04-19 |
| SBI6331 | S7 Airlines (Siberia Airlines) | 2 | 2026-06-12 |
| SBI6327 | - | 2 | 2026-06-25 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | SBI5240 | - | Jul 13, 14:50 UTC | Jul 14, 01:10 UTC | 10h 20m |
| 2026-07-11 | SBI5890 | - | Jul 11, 12:00 UTC | Jul 11, 12:20 UTC | 20m |
| 2026-07-11 | SBI5889 | - | Jul 11, 10:00 UTC | Jul 11, 10:15 UTC | 15m |
| 2026-07-10 | SBI5240 | - | Jul 10, 15:15 UTC | Jul 11, 02:10 UTC | 10h 56m |
| 2026-07-10 | SBI5726 | - | Jul 10, 02:35 UTC | Jul 10, 06:15 UTC | 3h 40m |
| 2026-07-09 | SBI5890 | - | Jul 9, 11:05 UTC | Jul 9, 11:35 UTC | 30m |
| 2026-07-09 | SBI5889 | - | Jul 9, 09:05 UTC | Jul 9, 09:15 UTC | 10m |
| 2026-07-08 | SBI5890 | - | Jul 8, 10:55 UTC | Jul 8, 11:20 UTC | 25m |
| 2026-07-08 | SBI5889 | - | Jul 8, 08:35 UTC | Jul 8, 09:00 UTC | 25m |
| 2026-07-07 | SBI5239 | OVB → IKT | Jul 7, 14:40 UTC | Jul 8, 00:55 UTC | 10h 15m |
| 2026-07-06 | SBI5242 | - | Jul 6, 22:25 UTC | Jul 7, 04:45 UTC | 6h 20m |
| 2026-07-06 | SBI5001 | OVB → LED | Jul 6, 08:40 UTC | Jul 7, 04:45 UTC | 20h 5m |
| 2026-07-05 | SBI5203 | - | Jul 5, 16:20 UTC | Jul 6, 04:25 UTC | 12h 5m |
| 2026-07-05 | SBI5561 | - | Jul 5, 08:05 UTC | Jul 5, 13:40 UTC | 5h 35m |
| 2026-07-04 | SBI5204 | - | Jul 4, 19:25 UTC | Jul 5, 04:20 UTC | 8h 55m |
| 2026-07-04 | SBI6241 | VVO → PKX | Jul 4, 17:15 UTC | Jul 4, 17:30 UTC | 15m |
| 2026-07-03 | SBI6245 | - | Jul 3, 14:10 UTC | Jul 4, 08:00 UTC | 17h 50m |
| 2026-07-02 | SBI6416 | - | Jul 2, 18:05 UTC | Jul 3, 14:25 UTC | 20h 20m |
| 2026-07-02 | SBI6415 | - | Jul 2, 12:40 UTC | Jul 2, 18:40 UTC | 6h 0m |
| 2026-07-01 | SBI6415 | - | Jul 1, 18:30 UTC | Jul 2, 13:20 UTC | 18h 50m |
| 2026-07-01 | SBI5864 | - | Jul 1, 11:30 UTC | Jul 1, 13:20 UTC | 1h 50m |
| 2026-06-30 | SBI5863 | - | Jun 30, 18:50 UTC | Jul 1, 09:45 UTC | 14h 55m |
| 2026-06-29 | SBI5246 | - | Jun 29, 18:25 UTC | Jun 30, 02:35 UTC | 8h 11m |
| 2026-06-28 | SBI5264 | - | Jun 28, 19:09 UTC | Jun 29, 03:14 UTC | 8h 5m |
| 2026-06-27 | SBI5863 | - | Jun 27, 15:05 UTC | Jun 28, 10:00 UTC | 18h 55m |
| 2026-06-27 | SBI5204 | - | Jun 27, 04:24 UTC | Jun 27, 12:45 UTC | 8h 20m |
| 2026-06-26 | SBI6328 | OSS → IKT | Jun 26, 12:05 UTC | Jun 27, 08:44 UTC | 20h 40m |
| 2026-06-26 | SBI6328 | OSS → IKT | Jun 26, 11:45 UTC | Jun 27, 08:44 UTC | 21h 0m |
| 2026-06-26 | SBI6328 | OSS → IKT | Jun 26, 06:19 UTC | Jun 27, 05:04 UTC | 22h 45m |
| 2026-06-25 | SBI6327 | - | Jun 25, 12:35 UTC | Jun 26, 12:00 UTC | 23h 25m |
| 2026-06-24 | SBI6415 | - | Jun 24, 21:44 UTC | Jun 25, 13:20 UTC | 15h 35m |
| 2026-06-24 | SBI6311 | IKT → PKX | Jun 24, 19:34 UTC | Jun 24, 19:44 UTC | 10m |
| 2026-06-24 | SBI6328 | OSS → IKT | Jun 24, 06:15 UTC | Jun 24, 13:00 UTC | 6h 45m |
| 2026-06-22 | SBI6318 | - | Jun 22, 04:59 UTC | Jun 22, 05:54 UTC | 55m |
| 2026-06-21 | SBI6317 | - | Jun 21, 14:15 UTC | Jun 22, 03:30 UTC | 13h 15m |
| 2026-06-21 | SBI6309 | - | Jun 21, 12:14 UTC | Jun 21, 12:49 UTC | 35m |
| 2026-06-19 | SBI6327 | - | Jun 19, 06:24 UTC | Jun 19, 12:49 UTC | 6h 25m |
| 2026-06-18 | SBI6409 | - | Jun 18, 03:30 UTC | Jun 18, 07:10 UTC | 3h 40m |
| 2026-06-17 | SBI6409 | - | Jun 17, 06:05 UTC | Jun 18, 04:05 UTC | 22h 0m |
| 2026-06-17 | SBI6409 | - | Jun 17, 05:45 UTC | Jun 18, 04:00 UTC | 22h 15m |
| 2026-06-16 | SBI6409 | - | Jun 16, 14:09 UTC | Jun 17, 07:05 UTC | 16h 56m |
| 2026-06-16 | SBI6409 | - | Jun 16, 06:35 UTC | Jun 17, 06:00 UTC | 23h 26m |
| 2026-06-15 | SBI6318 | - | Jun 15, 05:00 UTC | Jun 15, 05:55 UTC | 55m |
| 2026-06-14 | SBI6310 | BKK → IKT | Jun 14, 14:00 UTC | Jun 15, 03:30 UTC | 13h 29m |
| 2026-06-14 | SBI6309 | IKT → BKK | Jun 14, 12:00 UTC | Jun 14, 12:35 UTC | 35m |
| 2026-06-12 | SBI6331 | IKT → YKS | Jun 12, 13:55 UTC | Jun 13, 06:20 UTC | 16h 24m |
| 2026-06-12 | SBI6331 | IKT → YKS | Jun 12, 04:30 UTC | Jun 12, 20:00 UTC | 15h 30m |
| 2026-06-11 | SBI6317 | IKT → OSS | Jun 11, 13:30 UTC | Jun 12, 02:40 UTC | 13h 11m |
| 2026-06-10 | SBI6309 | IKT → BKK | Jun 10, 21:55 UTC | Jun 11, 11:35 UTC | 13h 40m |
| 2026-06-10 | SBI6311 | IKT → PKX | Jun 10, 19:30 UTC | Jun 10, 19:45 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-73408 page for operator, model, and routing details .