sensors Mode-S transponder
151EE7
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73447 · BOEING 737-800
- Hex
- 151EE7
- Octal
- 05217347
- Decimal
- 1,384,167
- Country
- RU
- Tail
- RA-73447
- Type
- B738
- Flights observed
- 75
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- 2h ago
Last known position
Country allocation
The ICAO 24-bit address 151EE7 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 |
|---|---|---|---|
| SBI5204 | - | 11 | 2026-07-10 |
| SBI5208 | - | 6 | 2026-07-12 |
| SBI5103 | S7 Airlines (Siberia Airlines) | 5 | 2026-06-11 |
| SBI5203 | S7 Airlines (Siberia Airlines) | 4 | 2026-06-14 |
| SBI5105 | S7 Airlines (Siberia Airlines) | 4 | 2026-06-10 |
| SBI5248 | - | 3 | 2026-07-08 |
| SBI5240 | - | 3 | 2026-06-16 |
| SBI5207 | S7 Airlines (Siberia Airlines) | 3 | 2026-07-02 |
| SBI5206 | - | 3 | 2026-07-06 |
| SBI5264 | - | 2 | 2026-07-11 |
| SBI5242 | S7 Airlines (Siberia Airlines) | 2 | 2026-06-01 |
| SBI5226 | - | 2 | 2026-04-13 |
| SBI5212 | - | 2 | 2026-07-13 |
| SBI5045 | S7 Airlines (Siberia Airlines) | 2 | 2026-05-25 |
| SBI5001 | S7 Airlines (Siberia Airlines) | 2 | 2026-06-29 |
| SBI2510 | S7 Airlines (Siberia Airlines) | 2 | 2026-06-01 |
| SBI8992 | S7 Airlines (Siberia Airlines) | 1 | 2026-05-28 |
| SBI8970 | - | 1 | 2026-04-27 |
| SBI5348 | - | 1 | 2026-04-15 |
| SBI5347 | - | 1 | 2026-04-15 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | SBI5212 | - | Jul 13, 19:40 UTC | Jul 14, 04:50 UTC | 9h 10m |
| 2026-07-12 | SBI5208 | - | Jul 12, 19:05 UTC | Jul 13, 06:45 UTC | 11h 40m |
| 2026-07-11 | SBI5264 | - | Jul 11, 19:20 UTC | Jul 12, 03:40 UTC | 8h 20m |
| 2026-07-10 | SBI5204 | - | Jul 10, 16:30 UTC | Jul 11, 04:20 UTC | 11h 50m |
| 2026-07-09 | SBI5259 | - | Jul 9, 14:35 UTC | Jul 10, 02:00 UTC | 11h 25m |
| 2026-07-08 | SBI5248 | - | Jul 8, 04:05 UTC | Jul 8, 04:30 UTC | 25m |
| 2026-07-07 | SBI5247 | OVB → NER | Jul 7, 20:05 UTC | Jul 7, 20:40 UTC | 35m |
| 2026-07-06 | SBI5206 | - | Jul 6, 05:15 UTC | Jul 6, 05:40 UTC | 25m |
| 2026-07-05 | SBI5205 | - | Jul 5, 14:00 UTC | Jul 5, 14:35 UTC | 35m |
| 2026-07-03 | SBI5208 | - | Jul 3, 19:15 UTC | Jul 4, 07:20 UTC | 12h 5m |
| 2026-07-02 | SBI5207 | OVB → VVO | Jul 2, 18:50 UTC | Jul 3, 06:35 UTC | 11h 45m |
| 2026-07-01 | SBI5208 | - | Jul 1, 18:50 UTC | Jul 2, 07:00 UTC | 12h 10m |
| 2026-07-01 | SBI5068 | - | Jul 1, 06:20 UTC | Jul 1, 11:55 UTC | 5h 35m |
| 2026-06-30 | SBI5206 | - | Jun 30, 14:05 UTC | Jul 1, 02:05 UTC | 12h 0m |
| 2026-06-29 | SBI5283 | OVB → PWE | Jun 29, 22:00 UTC | Jun 30, 11:35 UTC | 13h 36m |
| 2026-06-29 | SBI5001 | OVB → LED | Jun 29, 08:44 UTC | Jun 29, 09:05 UTC | 20m |
| 2026-06-28 | SBI5241 | - | Jun 28, 21:14 UTC | Jun 29, 03:54 UTC | 6h 40m |
| 2026-06-27 | SBI5264 | - | Jun 27, 18:35 UTC | Jun 28, 02:34 UTC | 8h 0m |
| 2026-06-25 | SBI5204 | - | Jun 25, 16:35 UTC | Jun 26, 04:20 UTC | 11h 45m |
| 2026-06-25 | SBI5204 | - | Jun 25, 04:04 UTC | Jun 25, 04:25 UTC | 20m |
| 2026-06-23 | SBI5248 | NER → OVB | Jun 23, 14:15 UTC | Jun 24, 04:15 UTC | 14h 0m |
| 2026-06-22 | SBI5239 | OVB → IKT | Jun 22, 14:49 UTC | Jun 22, 15:24 UTC | 35m |
| 2026-06-21 | SBI5206 | - | Jun 21, 14:15 UTC | Jun 22, 01:55 UTC | 11h 40m |
| 2026-06-19 | SBI5263 | OVB → YKS | Jun 19, 18:44 UTC | Jun 19, 19:09 UTC | 25m |
| 2026-06-18 | SBI5204 | - | Jun 18, 16:55 UTC | Jun 19, 04:29 UTC | 11h 34m |
| 2026-06-16 | SBI5240 | - | Jun 16, 15:35 UTC | Jun 17, 01:45 UTC | 10h 11m |
| 2026-06-14 | SBI5203 | OVB → VVO | Jun 14, 16:30 UTC | Jun 15, 04:30 UTC | 12h 0m |
| 2026-06-12 | SBI5203 | OVB → VVO | Jun 12, 16:35 UTC | Jun 12, 17:10 UTC | 35m |
| 2026-06-11 | SBI5103 | OVB → AER | Jun 11, 16:10 UTC | Jun 12, 08:15 UTC | 16h 6m |
| 2026-06-11 | SBI5103 | OVB → AER | Jun 11, 11:50 UTC | Jun 12, 08:15 UTC | 20h 26m |
| 2026-06-10 | SBI5105 | OVB → AER | Jun 10, 10:45 UTC | Jun 10, 11:40 UTC | 55m |
| 2026-06-09 | SBI5204 | VVO → OVB | Jun 9, 16:55 UTC | Jun 10, 04:35 UTC | 11h 40m |
| 2026-06-09 | SBI5204 | VVO → OVB | Jun 9, 07:50 UTC | Jun 10, 04:35 UTC | 20h 45m |
| 2026-06-09 | SBI5103 | OVB → AER | Jun 9, 07:05 UTC | Jun 10, 04:35 UTC | 21h 30m |
| 2026-06-08 | SBI5240 | IKT → OVB | Jun 8, 14:50 UTC | Jun 9, 01:05 UTC | 10h 15m |
| 2026-06-07 | SBI5208 | VVO → OVB | Jun 7, 18:45 UTC | Jun 8, 06:35 UTC | 11h 50m |
| 2026-06-07 | SBI5104 | AER → OVB | Jun 7, 00:10 UTC | Jun 7, 00:34 UTC | 25m |
| 2026-06-06 | SBI5103 | OVB → AER | Jun 6, 07:20 UTC | Jun 6, 08:20 UTC | 1h 0m |
| 2026-06-05 | SBI5266 | GDX → OVB | Jun 5, 14:40 UTC | Jun 6, 01:50 UTC | 11h 10m |
| 2026-06-04 | SBI2505 | DME → OVB | Jun 4, 21:55 UTC | Jun 5, 10:45 UTC | 12h 50m |
| 2026-06-03 | SBI5207 | OVB → VVO | Jun 3, 18:55 UTC | Jun 3, 19:30 UTC | 35m |
| 2026-06-03 | SBI5001 | OVB → LED | Jun 3, 06:15 UTC | Jun 3, 08:35 UTC | 2h 20m |
| 2026-06-02 | SBI5248 | NER → OVB | Jun 2, 20:05 UTC | Jun 3, 04:05 UTC | 8h 0m |
| 2026-06-01 | SBI5242 | MJZ → OVB | Jun 1, 22:05 UTC | Jun 2, 04:40 UTC | 6h 35m |
| 2026-06-01 | SBI2510 | OVB → DME | Jun 1, 08:35 UTC | Jun 1, 08:45 UTC | 10m |
| 2026-05-31 | SBI5208 | VVO → OVB | May 31, 19:00 UTC | Jun 1, 06:40 UTC | 11h 40m |
| 2026-05-31 | SBI2510 | OVB → DME | May 31, 08:50 UTC | May 31, 15:10 UTC | 6h 20m |
| 2026-05-28 | SBI5204 | VVO → OVB | May 28, 16:25 UTC | May 29, 04:40 UTC | 12h 15m |
| 2026-05-28 | SBI8992 | OVB → IKT | May 28, 13:20 UTC | May 28, 14:00 UTC | 40m |
| 2026-05-26 | SBI5203 | OVB → VVO | May 26, 16:24 UTC | May 26, 16:59 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-73447 page for operator, model, and routing details .