sensors Mode-S transponder
151DE5
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73189 · BOEING 737-800
- Hex
- 151DE5
- Octal
- 05216745
- Decimal
- 1,383,909
- Country
- RU
- Tail
- RA-73189
- Type
- B738
- Flights observed
- 95
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- 6h ago
Last known position
Country allocation
The ICAO 24-bit address 151DE5 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 |
|---|---|---|---|
| SDM6875 | - | 23 | 2026-06-26 |
| SDM6876 | - | 17 | 2026-06-28 |
| SDM6726 | - | 7 | 2026-07-05 |
| SDM6725 | - | 6 | 2026-07-16 |
| SDM6985 | - | 4 | 2026-07-12 |
| SDM6623 | Rossiya - Russian Airlines | 4 | 2026-06-25 |
| SDM6551 | - | 4 | 2026-06-12 |
| SDM6476 | - | 4 | 2026-07-12 |
| SDM6896 | Rossiya - Russian Airlines | 3 | 2026-06-07 |
| SDM6895 | Rossiya - Russian Airlines | 3 | 2026-06-07 |
| SDM6986 | - | 2 | 2026-07-05 |
| SDM6791 | - | 2 | 2026-07-18 |
| SDM6783 | - | 2 | 2026-06-14 |
| SDM6747 | Rossiya - Russian Airlines | 2 | 2026-06-07 |
| SDM6552 | - | 2 | 2026-06-29 |
| SDM6987 | Rossiya - Russian Airlines | 1 | 2026-05-05 |
| SDM6826 | - | 1 | 2026-07-01 |
| SDM6821 | Rossiya - Russian Airlines | 1 | 2026-04-19 |
| SDM6792 | - | 1 | 2026-07-06 |
| SDM6784 | Rossiya - Russian Airlines | 1 | 2026-06-14 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-18 | SDM6791 | - | Jul 18, 02:50 UTC | Jul 18, 09:10 UTC | 6h 20m |
| 2026-07-16 | SDM6725 | - | Jul 16, 12:49 UTC | Jul 16, 22:45 UTC | 9h 55m |
| 2026-07-12 | SDM6476 | - | Jul 12, 14:20 UTC | Jul 12, 18:01 UTC | 3h 40m |
| 2026-07-12 | SDM6985 | - | Jul 12, 01:45 UTC | Jul 12, 12:25 UTC | 10h 40m |
| 2026-07-11 | SDM6637 | - | Jul 11, 14:25 UTC | Jul 11, 14:35 UTC | 10m |
| 2026-07-06 | SDM6792 | - | Jul 6, 18:35 UTC | Jul 7, 08:10 UTC | 13h 35m |
| 2026-07-06 | SDM6791 | - | Jul 6, 04:00 UTC | Jul 6, 19:15 UTC | 15h 15m |
| 2026-07-05 | SDM6726 | - | Jul 5, 21:40 UTC | Jul 6, 19:15 UTC | 21h 35m |
| 2026-07-05 | SDM6726 | - | Jul 5, 15:55 UTC | Jul 6, 04:40 UTC | 12h 45m |
| 2026-07-05 | SDM6986 | - | Jul 5, 02:30 UTC | Jul 5, 13:25 UTC | 10h 55m |
| 2026-07-04 | SDM6985 | - | Jul 4, 08:30 UTC | Jul 5, 03:20 UTC | 18h 50m |
| 2026-07-04 | SDM6985 | - | Jul 4, 03:20 UTC | Jul 5, 03:15 UTC | 23h 55m |
| 2026-07-02 | SDM6725 | - | Jul 2, 15:00 UTC | Jul 3, 01:05 UTC | 10h 5m |
| 2026-07-01 | SDM6826 | - | Jul 1, 13:25 UTC | Jul 1, 23:10 UTC | 9h 45m |
| 2026-06-29 | SDM6552 | - | Jun 29, 13:59 UTC | Jun 29, 23:39 UTC | 9h 40m |
| 2026-06-28 | SDM6876 | - | Jun 28, 23:54 UTC | Jun 29, 23:14 UTC | 23h 20m |
| 2026-06-28 | SDM6876 | - | Jun 28, 09:45 UTC | Jun 29, 01:00 UTC | 15h 15m |
| 2026-06-27 | SDM6876 | - | Jun 27, 11:20 UTC | Jun 28, 10:44 UTC | 23h 25m |
| 2026-06-26 | SDM6875 | - | Jun 26, 22:44 UTC | Jun 27, 11:55 UTC | 13h 10m |
| 2026-06-26 | SDM6875 | - | Jun 26, 11:34 UTC | Jun 27, 11:14 UTC | 23h 40m |
| 2026-06-25 | SDM6623 | KJA → SYX | Jun 25, 12:04 UTC | Jun 25, 19:59 UTC | 7h 55m |
| 2026-06-25 | SDM6476 | - | Jun 25, 06:00 UTC | Jun 25, 06:14 UTC | 15m |
| 2026-06-25 | SDM6476 | - | Jun 25, 02:10 UTC | Jun 25, 05:25 UTC | 3h 15m |
| 2026-06-23 | SDM6875 | - | Jun 23, 11:59 UTC | Jun 24, 00:05 UTC | 12h 5m |
| 2026-06-22 | SDM6875 | - | Jun 22, 21:59 UTC | Jun 23, 16:24 UTC | 18h 25m |
| 2026-06-21 | SDM6726 | - | Jun 21, 05:44 UTC | Jun 21, 22:34 UTC | 16h 50m |
| 2026-06-18 | SDM6726 | - | Jun 18, 14:55 UTC | Jun 18, 22:20 UTC | 7h 25m |
| 2026-06-15 | SDM6875 | KJA → AER | Jun 15, 10:00 UTC | Jun 15, 21:55 UTC | 11h 55m |
| 2026-06-14 | SDM6875 | KJA → AER | Jun 14, 21:20 UTC | Jun 15, 21:14 UTC | 23h 55m |
| 2026-06-14 | SDM6784 | OSS → KJA | Jun 14, 15:25 UTC | Jun 15, 10:45 UTC | 19h 19m |
| 2026-06-14 | SDM6783 | - | Jun 14, 14:25 UTC | Jun 15, 10:45 UTC | 20h 20m |
| 2026-06-12 | SDM6552 | - | Jun 12, 09:45 UTC | Jun 13, 02:15 UTC | 16h 30m |
| 2026-06-12 | SDM6551 | - | Jun 12, 06:05 UTC | Jun 13, 02:15 UTC | 20h 10m |
| 2026-06-11 | SDM6551 | - | Jun 11, 19:20 UTC | Jun 12, 18:40 UTC | 23h 20m |
| 2026-06-11 | SDM6551 | - | Jun 11, 12:10 UTC | Jun 12, 10:15 UTC | 22h 6m |
| 2026-06-11 | SDM6551 | - | Jun 11, 09:45 UTC | Jun 12, 06:45 UTC | 21h 1m |
| 2026-06-11 | SDM6475 | LED → KJA | Jun 11, 08:35 UTC | Jun 12, 06:45 UTC | 22h 11m |
| 2026-06-11 | SDM6476 | KJA → LED | Jun 11, 02:20 UTC | Jun 11, 06:30 UTC | 4h 10m |
| 2026-06-07 | SDM6748 | KZN → KJA | Jun 7, 22:00 UTC | Jun 8, 10:10 UTC | 12h 10m |
| 2026-06-07 | SDM6747 | KJA → KZN | Jun 7, 14:30 UTC | Jun 8, 10:10 UTC | 19h 40m |
| 2026-06-07 | SDM6747 | KJA → KZN | Jun 7, 11:25 UTC | Jun 8, 10:10 UTC | 22h 45m |
| 2026-06-07 | SDM6896 | FRU → KJA | Jun 7, 10:40 UTC | Jun 8, 04:40 UTC | 18h 0m |
| 2026-06-07 | SDM6896 | FRU → KJA | Jun 7, 07:20 UTC | Jun 8, 04:40 UTC | 21h 20m |
| 2026-06-07 | SDM6895 | KJA → FRU | Jun 7, 05:55 UTC | Jun 8, 04:40 UTC | 22h 45m |
| 2026-06-06 | SDM6895 | KJA → FRU | Jun 6, 22:15 UTC | Jun 7, 15:10 UTC | 16h 55m |
| 2026-06-06 | SDM6623 | KJA → SYX | Jun 6, 19:30 UTC | Jun 6, 19:40 UTC | 10m |
| 2026-06-05 | SDM6876 | AER → KJA | Jun 5, 23:30 UTC | Jun 6, 19:40 UTC | 20h 10m |
| 2026-06-05 | SDM6876 | AER → KJA | Jun 5, 20:00 UTC | Jun 6, 00:35 UTC | 4h 35m |
| 2026-06-05 | SDM6875 | KJA → AER | Jun 5, 11:00 UTC | Jun 5, 15:25 UTC | 4h 25m |
| 2026-06-04 | SDM6875 | KJA → AER | Jun 4, 19:40 UTC | Jun 5, 15:25 UTC | 19h 45m |
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-73189 page for operator, model, and routing details .