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