sensors Mode-S transponder
151E32
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73266 · BOEING 737-800
- Hex
- 151E32
- Octal
- 05217062
- Decimal
- 1,383,986
- Country
- RU
- Tail
- RA-73266
- Type
- B738
- Flights observed
- 84
- Distinct callsigns
- 19
- Country
- RU
- Last broadcast
- 4h ago
Last known position
Country allocation
The ICAO 24-bit address 151E32 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 19 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| DRU543 | Alrosa Mirny Air Enterprise | 19 | 2026-05-28 |
| DRU544 | Alrosa Mirny Air Enterprise | 15 | 2026-05-28 |
| DRU589 | Alrosa Mirny Air Enterprise | 8 | 2026-05-07 |
| DRU597 | Alrosa Mirny Air Enterprise | 7 | 2026-05-01 |
| DRU590 | Alrosa Mirny Air Enterprise | 7 | 2026-05-29 |
| DRU552 | Alrosa Mirny Air Enterprise | 5 | 2026-05-28 |
| DRU551 | Alrosa Mirny Air Enterprise | 5 | 2026-05-25 |
| DRU598 | Alrosa Mirny Air Enterprise | 4 | 2026-05-03 |
| DRU624 | Alrosa Mirny Air Enterprise | 2 | 2026-05-03 |
| DRU623 | Alrosa Mirny Air Enterprise | 2 | 2026-05-02 |
| DRU571 | Alrosa Mirny Air Enterprise | 2 | 2026-05-05 |
| DRU9850 | - | 1 | 2026-04-29 |
| DRU9842 | Alrosa Mirny Air Enterprise | 1 | 2026-05-29 |
| DRU9828 | - | 1 | 2026-04-25 |
| DRU9827 | - | 1 | 2026-04-27 |
| DRU9824 | - | 1 | 2026-04-26 |
| DRU572 | Alrosa Mirny Air Enterprise | 1 | 2026-05-05 |
| DRU541 | Alrosa Mirny Air Enterprise | 1 | 2026-04-25 |
| 544 | - | 1 | 2026-05-13 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | DRU590 | OVB → MJZ | May 29, 19:55 UTC | May 29, 20:20 UTC | 25m |
| 2026-05-29 | DRU9842 | OVB → IKT | May 29, 12:50 UTC | May 29, 18:15 UTC | 5h 25m |
| 2026-05-28 | DRU552 | PYJ → OVB | May 28, 20:40 UTC | May 29, 03:50 UTC | 7h 10m |
| 2026-05-28 | DRU544 | VKO → OVB | May 28, 12:50 UTC | May 28, 16:10 UTC | 3h 20m |
| 2026-05-28 | DRU543 | OVB → VKO | May 28, 08:05 UTC | May 28, 10:05 UTC | 2h 0m |
| 2026-05-27 | DRU552 | PYJ → OVB | May 27, 20:45 UTC | May 28, 03:50 UTC | 7h 5m |
| 2026-05-26 | DRU544 | VKO → OVB | May 26, 12:54 UTC | May 27, 03:45 UTC | 14h 50m |
| 2026-05-26 | DRU543 | OVB → VKO | May 26, 06:34 UTC | May 26, 10:25 UTC | 3h 50m |
| 2026-05-25 | DRU551 | OVB → PYJ | May 25, 20:30 UTC | May 26, 03:45 UTC | 7h 15m |
| 2026-05-25 | DRU544 | VKO → OVB | May 25, 13:10 UTC | May 25, 15:00 UTC | 1h 50m |
| 2026-05-25 | DRU543 | OVB → VKO | May 25, 08:05 UTC | May 25, 10:10 UTC | 2h 5m |
| 2026-05-24 | DRU551 | OVB → PYJ | May 24, 20:35 UTC | May 25, 03:35 UTC | 7h 0m |
| 2026-05-22 | DRU544 | VKO → OVB | May 22, 13:00 UTC | May 23, 07:05 UTC | 18h 4m |
| 2026-05-22 | DRU543 | OVB → VKO | May 22, 06:30 UTC | May 22, 10:00 UTC | 3h 30m |
| 2026-05-21 | DRU552 | PYJ → OVB | May 21, 20:55 UTC | May 22, 03:45 UTC | 6h 50m |
| 2026-05-21 | DRU544 | VKO → OVB | May 21, 14:00 UTC | May 21, 15:50 UTC | 1h 50m |
| 2026-05-21 | DRU543 | OVB → VKO | May 21, 06:35 UTC | May 21, 10:15 UTC | 3h 40m |
| 2026-05-20 | DRU551 | OVB → PYJ | May 20, 20:55 UTC | May 21, 03:45 UTC | 6h 50m |
| 2026-05-19 | DRU551 | OVB → PYJ | May 19, 20:45 UTC | May 20, 03:55 UTC | 7h 10m |
| 2026-05-18 | DRU544 | VKO → OVB | May 18, 13:15 UTC | May 19, 03:40 UTC | 14h 24m |
| 2026-05-18 | DRU543 | OVB → VKO | May 18, 08:01 UTC | May 18, 10:00 UTC | 2h 0m |
| 2026-05-17 | DRU544 | VKO → OVB | May 17, 13:01 UTC | May 18, 03:45 UTC | 14h 45m |
| 2026-05-15 | DRU543 | OVB → VKO | May 15, 06:30 UTC | May 15, 10:05 UTC | 3h 35m |
| 2026-05-14 | DRU590 | OVB → MJZ | May 14, 19:45 UTC | May 15, 02:40 UTC | 6h 55m |
| 2026-05-14 | DRU544 | VKO → OVB | May 14, 12:55 UTC | May 14, 14:45 UTC | 1h 50m |
| 2026-05-14 | DRU543 | OVB → VKO | May 14, 06:40 UTC | May 14, 10:20 UTC | 3h 40m |
| 2026-05-13 | DRU590 | OVB → MJZ | May 13, 19:45 UTC | May 14, 02:35 UTC | 6h 50m |
| 2026-05-13 | 544 | - | May 13, 13:10 UTC | May 13, 15:05 UTC | 1h 55m |
| 2026-05-13 | DRU543 | OVB → VKO | May 13, 08:55 UTC | May 13, 11:15 UTC | 2h 20m |
| 2026-05-12 | DRU590 | OVB → MJZ | May 12, 19:40 UTC | May 13, 02:40 UTC | 7h 0m |
| 2026-05-12 | DRU544 | VKO → OVB | May 12, 13:10 UTC | May 12, 15:01 UTC | 1h 50m |
| 2026-05-12 | DRU543 | OVB → VKO | May 12, 08:15 UTC | May 12, 10:30 UTC | 2h 15m |
| 2026-05-10 | DRU552 | PYJ → OVB | May 10, 20:50 UTC | May 11, 04:05 UTC | 7h 15m |
| 2026-05-10 | DRU544 | VKO → OVB | May 10, 12:59 UTC | May 10, 14:40 UTC | 1h 40m |
| 2026-05-07 | DRU543 | OVB → VKO | May 7, 17:10 UTC | May 7, 17:20 UTC | 10m |
| 2026-05-07 | DRU543 | OVB → VKO | May 7, 11:30 UTC | May 7, 12:00 UTC | 30m |
| 2026-05-07 | DRU543 | OVB → VKO | May 7, 06:35 UTC | May 7, 09:15 UTC | 2h 40m |
| 2026-05-07 | DRU589 | MJZ → OVB | May 7, 02:10 UTC | May 7, 02:45 UTC | 35m |
| 2026-05-06 | DRU589 | MJZ → OVB | May 6, 04:50 UTC | May 7, 02:45 UTC | 21h 54m |
| 2026-05-06 | DRU589 | MJZ → OVB | May 6, 02:05 UTC | May 6, 02:40 UTC | 35m |
| 2026-05-05 | DRU572 | MJZ → PYJ | May 5, 04:35 UTC | May 5, 04:45 UTC | 10m |
| 2026-05-05 | DRU571 | MJZ → IKT | May 5, 02:30 UTC | May 5, 02:45 UTC | 15m |
| 2026-05-03 | DRU598 | VKO → MJZ | May 3, 17:40 UTC | May 3, 19:40 UTC | 2h 0m |
| 2026-05-03 | DRU624 | LED → VKO | May 3, 13:35 UTC | May 3, 14:55 UTC | 1h 20m |
| 2026-05-02 | DRU623 | VKO → LED | May 2, 08:05 UTC | May 2, 09:10 UTC | 1h 5m |
| 2026-05-01 | DRU597 | MJZ → VKO | May 1, 19:55 UTC | May 2, 06:25 UTC | 10h 30m |
| 2026-04-30 | DRU589 | MJZ → OVB | Apr 30, 19:45 UTC | May 1, 02:45 UTC | 7h 0m |
| 2026-04-30 | DRU544 | VKO → OVB | Apr 30, 13:05 UTC | Apr 30, 14:50 UTC | 1h 45m |
| 2026-04-29 | DRU9850 | - | Apr 29, 20:05 UTC | Apr 30, 11:35 UTC | 15h 29m |
| 2026-04-28 | DRU551 | OVB → PYJ | Apr 28, 20:40 UTC | Apr 29, 03:45 UTC | 7h 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-73266 page for operator, model, and routing details .