sensors Mode-S transponder
151DF9
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73209 · BOEING 737-800
- Hex
- 151DF9
- Octal
- 05216771
- Decimal
- 1,383,929
- Country
- RU
- Tail
- RA-73209
- Type
- B738
- Flights observed
- 205
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- 5h ago
Last known position
Country allocation
The ICAO 24-bit address 151DF9 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 |
|---|---|---|---|
| SDM5954 | - | 24 | 2026-07-04 |
| SDM5972 | - | 23 | 2026-07-03 |
| SDM5978 | - | 19 | 2026-07-11 |
| SDM5974 | - | 17 | 2026-07-03 |
| SDM5980 | - | 11 | 2026-07-02 |
| SDM5976 | Rossiya - Russian Airlines | 9 | 2026-05-31 |
| SDM5963 | - | 9 | 2026-07-12 |
| SDM6954 | - | 7 | 2026-07-14 |
| SDM6953 | - | 7 | 2026-07-09 |
| SDM5973 | - | 7 | 2026-07-01 |
| SDM5956 | - | 7 | 2026-07-05 |
| SDM5964 | Rossiya - Russian Airlines | 6 | 2026-05-23 |
| SDM5966 | Rossiya - Russian Airlines | 5 | 2026-05-30 |
| SDM6002 | Rossiya - Russian Airlines | 4 | 2026-05-19 |
| SDM5962 | Rossiya - Russian Airlines | 4 | 2026-06-02 |
| SDM5953 | - | 4 | 2026-07-11 |
| SDM6312 | - | 3 | 2026-07-07 |
| SDM6310 | Rossiya - Russian Airlines | 3 | 2026-05-17 |
| SDM5977 | - | 3 | 2026-07-11 |
| SDM6642 | Rossiya - Russian Airlines | 2 | 2026-06-08 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | SDM6954 | - | Jul 14, 08:55 UTC | Jul 14, 17:35 UTC | 8h 40m |
| 2026-07-13 | SDM6152 | KGD → SVO | Jul 13, 12:20 UTC | Jul 14, 07:25 UTC | 19h 5m |
| 2026-07-13 | SDM6152 | KGD → SVO | Jul 13, 11:55 UTC | Jul 14, 07:25 UTC | 19h 30m |
| 2026-07-12 | SDM5963 | - | Jul 12, 14:40 UTC | Jul 13, 10:00 UTC | 19h 20m |
| 2026-07-11 | SDM5963 | - | Jul 11, 22:40 UTC | Jul 12, 20:10 UTC | 21h 30m |
| 2026-07-11 | SDM5963 | - | Jul 11, 18:20 UTC | Jul 12, 16:10 UTC | 21h 50m |
| 2026-07-11 | SDM5977 | - | Jul 11, 18:10 UTC | Jul 12, 16:10 UTC | 22h 0m |
| 2026-07-11 | SDM5978 | - | Jul 11, 06:05 UTC | Jul 11, 23:45 UTC | 17h 40m |
| 2026-07-11 | SDM5978 | - | Jul 11, 02:20 UTC | Jul 11, 23:45 UTC | 21h 25m |
| 2026-07-11 | SDM5953 | - | Jul 11, 01:05 UTC | Jul 11, 23:45 UTC | 22h 40m |
| 2026-07-10 | SDM6309 | - | Jul 10, 06:55 UTC | Jul 10, 07:30 UTC | 35m |
| 2026-07-09 | SDM6954 | - | Jul 9, 10:20 UTC | Jul 10, 07:30 UTC | 21h 10m |
| 2026-07-09 | SDM6954 | - | Jul 9, 09:05 UTC | Jul 10, 07:30 UTC | 22h 25m |
| 2026-07-09 | SDM6953 | - | Jul 9, 05:55 UTC | Jul 9, 07:30 UTC | 1h 35m |
| 2026-07-09 | SDM6953 | SVO → SVO | Jul 9, 02:55 UTC | Jul 9, 03:25 UTC | 30m |
| 2026-07-08 | SDM6954 | - | Jul 8, 08:25 UTC | Jul 8, 10:10 UTC | 1h 45m |
| 2026-07-07 | SDM6312 | - | Jul 7, 19:20 UTC | Jul 8, 07:00 UTC | 11h 40m |
| 2026-07-07 | SDM6312 | - | Jul 7, 08:35 UTC | Jul 8, 07:00 UTC | 22h 25m |
| 2026-07-07 | SDM6953 | - | Jul 7, 06:45 UTC | Jul 7, 07:20 UTC | 35m |
| 2026-07-06 | SDM6953 | - | Jul 6, 10:20 UTC | Jul 7, 07:20 UTC | 21h 0m |
| 2026-07-06 | SDM6954 | - | Jul 6, 08:35 UTC | Jul 7, 07:20 UTC | 22h 45m |
| 2026-07-06 | SDM6953 | - | Jul 6, 06:20 UTC | Jul 6, 07:05 UTC | 45m |
| 2026-07-05 | SDM5956 | - | Jul 5, 14:35 UTC | Jul 5, 17:15 UTC | 2h 40m |
| 2026-07-04 | SDM5954 | - | Jul 4, 16:20 UTC | Jul 5, 11:55 UTC | 19h 35m |
| 2026-07-04 | SDM5954 | - | Jul 4, 14:40 UTC | Jul 5, 11:55 UTC | 21h 15m |
| 2026-07-04 | SDM5954 | - | Jul 4, 13:45 UTC | Jul 5, 11:55 UTC | 22h 10m |
| 2026-07-04 | SDM5954 | - | Jul 4, 03:05 UTC | Jul 4, 21:30 UTC | 18h 25m |
| 2026-07-04 | SDM5954 | - | Jul 4, 00:20 UTC | Jul 4, 21:30 UTC | 21h 10m |
| 2026-07-03 | SDM5954 | - | Jul 3, 23:15 UTC | Jul 4, 21:30 UTC | 22h 15m |
| 2026-07-03 | SDM5972 | - | Jul 3, 10:20 UTC | Jul 4, 05:50 UTC | 19h 30m |
| 2026-07-03 | SDM5972 | - | Jul 3, 09:05 UTC | Jul 4, 05:50 UTC | 20h 45m |
| 2026-07-03 | SDM5972 | - | Jul 3, 06:20 UTC | Jul 4, 05:50 UTC | 23h 30m |
| 2026-07-03 | SDM5974 | - | Jul 3, 04:50 UTC | Jul 4, 04:15 UTC | 23h 25m |
| 2026-07-02 | SDM5980 | - | Jul 2, 17:30 UTC | Jul 3, 11:40 UTC | 18h 10m |
| 2026-07-02 | SDM5980 | - | Jul 2, 14:20 UTC | Jul 3, 11:40 UTC | 21h 20m |
| 2026-07-02 | SDM5980 | - | Jul 2, 12:50 UTC | Jul 3, 11:40 UTC | 22h 50m |
| 2026-07-01 | SDM5973 | - | Jul 1, 13:25 UTC | Jul 1, 21:50 UTC | 8h 25m |
| 2026-06-30 | SDM5973 | - | Jun 30, 22:20 UTC | Jul 1, 21:50 UTC | 23h 30m |
| 2026-06-30 | SDM5973 | - | Jun 30, 20:55 UTC | Jul 1, 20:15 UTC | 23h 20m |
| 2026-06-30 | SDM5973 | - | Jun 30, 18:20 UTC | Jul 1, 16:45 UTC | 22h 25m |
| 2026-06-30 | SDM5974 | - | Jun 30, 17:00 UTC | Jul 1, 16:15 UTC | 23h 15m |
| 2026-06-30 | SDM5974 | - | Jun 30, 05:10 UTC | Jun 30, 23:50 UTC | 18h 40m |
| 2026-06-30 | SDM5974 | - | Jun 30, 02:20 UTC | Jun 30, 23:50 UTC | 21h 30m |
| 2026-06-30 | SDM5974 | - | Jun 30, 00:25 UTC | Jun 30, 23:50 UTC | 23h 25m |
| 2026-06-29 | SDM5972 | - | Jun 29, 10:20 UTC | Jun 30, 07:55 UTC | 21h 36m |
| 2026-06-29 | SDM5972 | - | Jun 29, 08:19 UTC | Jun 30, 07:55 UTC | 23h 36m |
| 2026-06-29 | SDM5978 | - | Jun 29, 08:14 UTC | Jun 30, 06:15 UTC | 22h 1m |
| 2026-06-29 | SDM5978 | - | Jun 29, 04:20 UTC | Jun 30, 02:25 UTC | 22h 6m |
| 2026-06-29 | SDM5978 | - | Jun 29, 04:00 UTC | Jun 30, 02:15 UTC | 22h 16m |
| 2026-06-28 | SDM5978 | - | Jun 28, 16:19 UTC | Jun 29, 10:55 UTC | 18h 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-73209 page for operator, model, and routing details .