sensors Mode-S transponder
151F0D
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73485 · BOEING 737-900
- Hex
- 151F0D
- Octal
- 05217415
- Decimal
- 1,384,205
- Country
- RU
- Tail
- RA-73485
- Type
- B739
- Flights observed
- 114
- Distinct callsigns
- 12
- Country
- RU
- Last broadcast
- 9h ago
Last known position
Country allocation
The ICAO 24-bit address 151F0D 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 |
|---|---|---|---|
| SDM6310 | Rossiya - Russian Airlines | 22 | 2026-05-28 |
| SDM6309 | Rossiya - Russian Airlines | 19 | 2026-05-28 |
| SDM6314 | Rossiya - Russian Airlines | 18 | 2026-05-29 |
| SDM6312 | Rossiya - Russian Airlines | 14 | 2026-05-29 |
| SDM6313 | Rossiya - Russian Airlines | 11 | 2026-05-29 |
| SDM6662 | Rossiya - Russian Airlines | 10 | 2026-05-28 |
| SDM6311 | Rossiya - Russian Airlines | 7 | 2026-05-29 |
| SDM6661 | Rossiya - Russian Airlines | 6 | 2026-05-26 |
| SDM6365 | Rossiya - Russian Airlines | 4 | 2026-05-28 |
| SDM6520 | Rossiya - Russian Airlines | 1 | 2026-05-22 |
| SDM6366 | Rossiya - Russian Airlines | 1 | 2026-04-25 |
| SDM6079 | - | 1 | 2026-04-18 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | SDM6312 | KGD → SVO | May 29, 19:00 UTC | May 29, 20:35 UTC | 1h 35m |
| 2026-05-29 | SDM6311 | SVO → KGD | May 29, 15:30 UTC | May 29, 17:25 UTC | 1h 55m |
| 2026-05-29 | SDM6314 | KGD → SVO | May 29, 12:00 UTC | May 29, 13:40 UTC | 1h 40m |
| 2026-05-29 | SDM6313 | SVO → KGD | May 29, 08:55 UTC | May 29, 09:40 UTC | 45m |
| 2026-05-29 | SDM6313 | SVO → KGD | May 29, 07:45 UTC | May 29, 08:05 UTC | 20m |
| 2026-05-28 | SDM6365 | SVO → TJM | May 28, 22:20 UTC | May 29, 02:25 UTC | 4h 5m |
| 2026-05-28 | SDM6365 | SVO → TJM | May 28, 21:00 UTC | May 28, 21:40 UTC | 40m |
| 2026-05-28 | SDM6662 | KGD → SVO | May 28, 17:35 UTC | May 28, 18:45 UTC | 1h 10m |
| 2026-05-28 | SDM6310 | KGD → SVO | May 28, 09:15 UTC | May 28, 15:40 UTC | 6h 25m |
| 2026-05-28 | SDM6309 | SVO → KGD | May 28, 06:50 UTC | May 28, 07:25 UTC | 35m |
| 2026-05-27 | SDM6662 | KGD → SVO | May 27, 17:35 UTC | May 27, 22:40 UTC | 5h 5m |
| 2026-05-26 | SDM6661 | SVO → KGD | May 26, 22:05 UTC | May 27, 15:30 UTC | 17h 26m |
| 2026-05-26 | SDM6314 | KGD → SVO | May 26, 12:05 UTC | May 27, 02:14 UTC | 14h 10m |
| 2026-05-25 | SDM6313 | SVO → KGD | May 25, 21:49 UTC | May 26, 10:10 UTC | 12h 20m |
| 2026-05-25 | SDM6661 | SVO → KGD | May 25, 13:35 UTC | May 25, 16:00 UTC | 2h 25m |
| 2026-05-25 | SDM6310 | KGD → SVO | May 25, 09:50 UTC | May 25, 11:25 UTC | 1h 35m |
| 2026-05-25 | SDM6309 | SVO → KGD | May 25, 02:10 UTC | May 25, 07:45 UTC | 5h 35m |
| 2026-05-24 | SDM6662 | KGD → SVO | May 24, 17:45 UTC | May 24, 19:40 UTC | 1h 55m |
| 2026-05-24 | SDM6661 | SVO → KGD | May 24, 13:30 UTC | May 24, 15:35 UTC | 2h 5m |
| 2026-05-24 | SDM6310 | KGD → SVO | May 24, 10:05 UTC | May 24, 11:40 UTC | 1h 35m |
| 2026-05-24 | SDM6309 | SVO → KGD | May 24, 07:05 UTC | May 24, 07:45 UTC | 40m |
| 2026-05-23 | SDM6312 | KGD → SVO | May 23, 19:30 UTC | May 23, 21:00 UTC | 1h 30m |
| 2026-05-23 | SDM6311 | SVO → KGD | May 23, 15:20 UTC | May 23, 17:25 UTC | 2h 5m |
| 2026-05-23 | SDM6314 | KGD → SVO | May 23, 11:30 UTC | May 23, 13:45 UTC | 2h 15m |
| 2026-05-22 | SDM6313 | SVO → KGD | May 22, 22:05 UTC | May 23, 10:05 UTC | 11h 59m |
| 2026-05-22 | SDM6520 | LED → SVO | May 22, 18:05 UTC | May 22, 18:35 UTC | 30m |
| 2026-05-21 | SDM6314 | KGD → SVO | May 21, 11:45 UTC | May 21, 22:55 UTC | 11h 10m |
| 2026-05-21 | SDM6313 | SVO → KGD | May 21, 09:15 UTC | May 21, 09:55 UTC | 40m |
| 2026-05-20 | SDM6313 | SVO → KGD | May 20, 13:20 UTC | May 21, 09:55 UTC | 20h 35m |
| 2026-05-20 | SDM6314 | KGD → SVO | May 20, 12:10 UTC | May 21, 09:55 UTC | 21h 45m |
| 2026-05-20 | SDM6313 | SVO → KGD | May 20, 09:30 UTC | May 20, 10:10 UTC | 40m |
| 2026-05-19 | SDM6310 | KGD → SVO | May 19, 09:30 UTC | May 19, 15:55 UTC | 6h 25m |
| 2026-05-19 | SDM6309 | SVO → KGD | May 19, 07:15 UTC | May 19, 07:45 UTC | 30m |
| 2026-05-17 | SDM6662 | KGD → SVO | May 17, 17:40 UTC | May 17, 20:20 UTC | 2h 40m |
| 2026-05-17 | SDM6661 | SVO → KGD | May 17, 15:01 UTC | May 17, 15:45 UTC | 45m |
| 2026-05-15 | SDM6662 | KGD → SVO | May 15, 19:05 UTC | May 15, 20:10 UTC | 1h 5m |
| 2026-05-15 | SDM6310 | KGD → SVO | May 15, 10:00 UTC | May 15, 16:55 UTC | 6h 54m |
| 2026-05-14 | SDM6662 | KGD → SVO | May 14, 17:50 UTC | May 15, 07:50 UTC | 14h 0m |
| 2026-05-14 | SDM6310 | KGD → SVO | May 14, 09:50 UTC | May 14, 15:45 UTC | 5h 55m |
| 2026-05-13 | SDM6662 | KGD → SVO | May 13, 21:30 UTC | May 14, 07:35 UTC | 10h 5m |
| 2026-05-13 | SDM6310 | KGD → SVO | May 13, 13:45 UTC | May 13, 19:50 UTC | 6h 5m |
| 2026-05-12 | SDM6662 | KGD → SVO | May 12, 17:35 UTC | May 13, 07:45 UTC | 14h 10m |
| 2026-05-12 | SDM6310 | KGD → SVO | May 12, 09:40 UTC | May 12, 15:50 UTC | 6h 10m |
| 2026-05-12 | SDM6309 | SVO → KGD | May 12, 06:55 UTC | May 12, 07:30 UTC | 35m |
| 2026-05-11 | SDM6314 | KGD → SVO | May 11, 01:25 UTC | May 11, 17:45 UTC | 16h 21m |
| 2026-05-10 | SDM6310 | KGD → SVO | May 10, 09:35 UTC | May 10, 15:45 UTC | 6h 10m |
| 2026-05-10 | SDM6309 | SVO → KGD | May 10, 07:04 UTC | May 10, 07:45 UTC | 40m |
| 2026-05-09 | SDM6661 | SVO → KGD | May 9, 14:20 UTC | May 9, 15:35 UTC | 1h 15m |
| 2026-05-09 | SDM6309 | SVO → KGD | May 9, 05:30 UTC | May 9, 07:45 UTC | 2h 15m |
| 2026-05-08 | SDM6312 | KGD → SVO | May 8, 19:35 UTC | May 8, 20:40 UTC | 1h 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-73485 page for operator, model, and routing details .