sensors Mode-S transponder
151E31
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73265 · BOEING 737-800
- Hex
- 151E31
- Octal
- 05217061
- Decimal
- 1,383,985
- Country
- RU
- Tail
- RA-73265
- Type
- B738
- Flights observed
- 193
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- Jul 26, 21:00 UTC
Last known position
Country allocation
The ICAO 24-bit address 151E31 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 |
|---|---|---|---|
| DRU543 | - | 32 | 2026-07-02 |
| DRU589 | Alrosa Mirny Air Enterprise | 27 | 2026-07-22 |
| DRU544 | - | 23 | 2026-07-02 |
| DRU598 | Alrosa Mirny Air Enterprise | 20 | 2026-07-24 |
| DRU597 | Alrosa Mirny Air Enterprise | 19 | 2026-07-24 |
| DRU551 | Alrosa Mirny Air Enterprise | 12 | 2026-07-26 |
| DRU590 | - | 10 | 2026-06-28 |
| DRU604 | Alrosa Mirny Air Enterprise | 5 | 2026-07-17 |
| DRU603 | - | 5 | 2026-07-17 |
| DRU9850 | - | 4 | 2026-07-09 |
| DRU552 | Alrosa Mirny Air Enterprise | 4 | 2026-04-30 |
| DRU525 | - | 4 | 2026-07-16 |
| DRU9827 | - | 3 | 2026-07-06 |
| DRU541 | Alrosa Mirny Air Enterprise | 3 | 2026-05-09 |
| DRU526 | Alrosa Mirny Air Enterprise | 3 | 2026-07-16 |
| DRU9847 | - | 2 | 2026-07-04 |
| DRU9828 | - | 2 | 2026-06-06 |
| DRU9826 | - | 2 | 2026-07-06 |
| DRU9808 | - | 2 | 2026-07-05 |
| DRU624 | Alrosa Mirny Air Enterprise | 2 | 2026-07-12 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | DRU551 | OVB → PYJ | Jul 26, 20:30 UTC | Jul 26, 21:00 UTC | 30m |
| 2026-07-26 | 9841 | - | Jul 26, 13:20 UTC | Jul 26, 18:15 UTC | 4h 55m |
| 2026-07-24 | DRU598 | VKO → MJZ | Jul 24, 17:30 UTC | Jul 25, 11:15 UTC | 17h 45m |
| 2026-07-24 | DRU597 | MJZ → VKO | Jul 24, 03:35 UTC | Jul 24, 06:15 UTC | 2h 40m |
| 2026-07-22 | DRU598 | - | Jul 22, 17:35 UTC | Jul 22, 19:40 UTC | 2h 5m |
| 2026-07-22 | DRU589 | MJZ → OVB | Jul 22, 02:00 UTC | Jul 22, 02:35 UTC | 35m |
| 2026-07-20 | DRU598 | - | Jul 20, 17:30 UTC | Jul 20, 19:35 UTC | 2h 5m |
| 2026-07-19 | DRU597 | - | Jul 19, 17:35 UTC | Jul 20, 06:05 UTC | 12h 30m |
| 2026-07-17 | DRU597 | - | Jul 17, 19:49 UTC | Jul 18, 06:15 UTC | 10h 26m |
| 2026-07-17 | DRU604 | AER → OVB | Jul 17, 13:35 UTC | Jul 17, 14:04 UTC | 30m |
| 2026-07-17 | DRU603 | - | Jul 17, 11:10 UTC | Jul 17, 11:50 UTC | 40m |
| 2026-07-16 | DRU589 | MJZ → OVB | Jul 16, 20:29 UTC | Jul 17, 02:50 UTC | 6h 20m |
| 2026-07-16 | DRU526 | OVB → MJZ | Jul 16, 15:05 UTC | Jul 16, 15:35 UTC | 30m |
| 2026-07-16 | DRU525 | - | Jul 16, 11:40 UTC | Jul 16, 12:40 UTC | 1h 0m |
| 2026-07-15 | DRU589 | - | Jul 15, 23:10 UTC | Jul 16, 05:25 UTC | 6h 15m |
| 2026-07-15 | DRU604 | AER → OVB | Jul 15, 14:00 UTC | Jul 15, 14:30 UTC | 30m |
| 2026-07-15 | DRU603 | - | Jul 15, 11:45 UTC | Jul 15, 12:20 UTC | 35m |
| 2026-07-14 | DRU589 | - | Jul 14, 23:15 UTC | Jul 15, 05:45 UTC | 6h 30m |
| 2026-07-14 | DRU526 | OVB → MJZ | Jul 14, 17:45 UTC | Jul 14, 18:10 UTC | 25m |
| 2026-07-14 | DRU525 | - | Jul 14, 14:50 UTC | Jul 14, 15:25 UTC | 35m |
| 2026-07-14 | DRU525 | - | Jul 14, 09:55 UTC | Jul 14, 11:30 UTC | 1h 35m |
| 2026-07-13 | DRU598 | - | Jul 13, 18:35 UTC | Jul 14, 02:55 UTC | 8h 20m |
| 2026-07-13 | DRU598 | - | Jul 13, 17:40 UTC | Jul 13, 18:05 UTC | 25m |
| 2026-07-12 | DRU597 | - | Jul 12, 21:00 UTC | Jul 13, 09:15 UTC | 12h 15m |
| 2026-07-12 | DRU624 | LED → VKO | Jul 12, 18:01 UTC | Jul 12, 19:25 UTC | 1h 25m |
| 2026-07-11 | DRU623 | - | Jul 11, 08:15 UTC | Jul 11, 09:15 UTC | 1h 0m |
| 2026-07-11 | DRU597 | - | Jul 11, 05:45 UTC | Jul 11, 06:01 UTC | 15m |
| 2026-07-10 | DRU597 | - | Jul 10, 18:20 UTC | Jul 11, 05:05 UTC | 10h 46m |
| 2026-07-10 | DRU598 | - | Jul 10, 17:35 UTC | Jul 10, 17:45 UTC | 10m |
| 2026-07-10 | DRU9941 | - | Jul 10, 06:20 UTC | Jul 10, 13:30 UTC | 7h 10m |
| 2026-07-09 | DRU9850 | - | Jul 9, 11:35 UTC | Jul 9, 15:55 UTC | 4h 20m |
| 2026-07-08 | DRU598 | - | Jul 8, 18:30 UTC | Jul 9, 15:55 UTC | 21h 25m |
| 2026-07-08 | DRU598 | - | Jul 8, 17:50 UTC | Jul 9, 11:40 UTC | 17h 50m |
| 2026-07-08 | DRU597 | - | Jul 8, 06:15 UTC | Jul 8, 06:25 UTC | 10m |
| 2026-07-08 | DRU597 | - | Jul 8, 03:50 UTC | Jul 8, 05:20 UTC | 1h 30m |
| 2026-07-07 | DRU597 | - | Jul 7, 07:40 UTC | Jul 8, 05:20 UTC | 21h 40m |
| 2026-07-06 | DRU9826 | - | Jul 6, 22:20 UTC | Jul 7, 06:00 UTC | 7h 40m |
| 2026-07-06 | DRU9849 | - | Jul 6, 18:40 UTC | Jul 6, 19:40 UTC | 1h 0m |
| 2026-07-06 | DRU545 | - | Jul 6, 16:00 UTC | Jul 6, 16:50 UTC | 50m |
| 2026-07-06 | DRU9827 | - | Jul 6, 00:40 UTC | Jul 6, 06:45 UTC | 6h 5m |
| 2026-07-05 | DRU9808 | - | Jul 5, 04:40 UTC | Jul 5, 13:50 UTC | 9h 10m |
| 2026-07-04 | DRU9847 | - | Jul 4, 01:05 UTC | Jul 4, 07:30 UTC | 6h 25m |
| 2026-07-03 | DRU9808 | - | Jul 3, 09:30 UTC | Jul 3, 18:05 UTC | 8h 35m |
| 2026-07-03 | DRU9847 | - | Jul 3, 01:15 UTC | Jul 3, 07:30 UTC | 6h 15m |
| 2026-07-02 | DRU544 | - | Jul 2, 13:10 UTC | Jul 2, 15:05 UTC | 1h 55m |
| 2026-07-02 | DRU543 | - | Jul 2, 08:05 UTC | Jul 2, 10:10 UTC | 2h 5m |
| 2026-07-01 | DRU598 | - | Jul 1, 17:40 UTC | Jul 2, 02:50 UTC | 9h 10m |
| 2026-06-30 | DRU597 | - | Jun 30, 19:45 UTC | Jul 1, 06:20 UTC | 10h 35m |
| 2026-06-30 | DRU544 | - | Jun 30, 13:05 UTC | Jun 30, 15:00 UTC | 1h 55m |
| 2026-06-30 | DRU544 | - | Jun 30, 07:55 UTC | Jun 30, 09:50 UTC | 1h 55m |
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-73265 page for operator, model, and routing details .