sensors Mode-S transponder
151DF2
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73202 · AIRBUS A-319
- Hex
- 151DF2
- Octal
- 05216762
- Decimal
- 1,383,922
- Country
- RU
- Tail
- RA-73202
- Type
- A319
- Flights observed
- 162
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- Jul 26, 06:35 UTC
Last known position
Country allocation
The ICAO 24-bit address 151DF2 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 |
|---|---|---|---|
| SDM6783 | - | 11 | 2026-06-29 |
| SDM6331 | Rossiya - Russian Airlines | 11 | 2026-07-24 |
| SDM6924 | Rossiya - Russian Airlines | 8 | 2026-07-24 |
| SDM6926 | Rossiya - Russian Airlines | 7 | 2026-06-14 |
| SDM6721 | - | 7 | 2026-07-01 |
| SDM6332 | Rossiya - Russian Airlines | 6 | 2026-05-26 |
| SDM6925 | Rossiya - Russian Airlines | 5 | 2026-06-03 |
| SDM6923 | - | 5 | 2026-07-10 |
| SDM6895 | - | 5 | 2026-06-28 |
| SDM6795 | - | 4 | 2026-06-30 |
| SDM6450 | Rossiya - Russian Airlines | 4 | 2026-05-29 |
| SDM6326 | - | 4 | 2026-07-05 |
| SDM6325 | - | 4 | 2026-07-05 |
| SDM6784 | - | 3 | 2026-06-28 |
| SDM6726 | - | 3 | 2026-06-23 |
| SDM6572 | - | 3 | 2026-07-03 |
| SDM6571 | - | 3 | 2026-06-22 |
| SDM6472 | Rossiya - Russian Airlines | 3 | 2026-07-22 |
| SDM6442 | Rossiya - Russian Airlines | 3 | 2026-05-29 |
| SDM6946 | Rossiya - Russian Airlines | 2 | 2026-04-19 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | SDM6860 | MRV → LED | Jul 26, 04:40 UTC | Jul 26, 06:35 UTC | 1h 56m |
| 2026-07-24 | SDM6331 | LED → KGD | Jul 24, 18:35 UTC | Jul 24, 19:00 UTC | 25m |
| 2026-07-24 | SDM6924 | EVN → EVN | Jul 24, 15:55 UTC | Jul 24, 16:20 UTC | 25m |
| 2026-07-24 | SDM6924 | EVN → EVN | Jul 24, 12:40 UTC | Jul 24, 13:10 UTC | 30m |
| 2026-07-23 | SDM6924 | EVN → EVN | Jul 23, 12:10 UTC | Jul 23, 18:35 UTC | 6h 25m |
| 2026-07-22 | SDM6467 | LED → TJM | Jul 22, 23:50 UTC | Jul 23, 10:25 UTC | 10h 35m |
| 2026-07-22 | SDM6472 | OMS → LED | Jul 22, 02:35 UTC | Jul 23, 00:10 UTC | 21h 35m |
| 2026-07-22 | SDM6472 | OMS → LED | Jul 22, 02:15 UTC | Jul 23, 00:10 UTC | 21h 55m |
| 2026-07-19 | SDM6524 | - | Jul 19, 12:10 UTC | Jul 20, 05:45 UTC | 17h 35m |
| 2026-07-18 | SDM6471 | LED → OMS | Jul 18, 21:15 UTC | Jul 19, 10:20 UTC | 13h 5m |
| 2026-07-18 | SDM6353 | LED → LED | Jul 18, 08:35 UTC | Jul 18, 08:55 UTC | 20m |
| 2026-07-17 | SDM6544 | OVB → LED | Jul 17, 23:10 UTC | Jul 18, 05:35 UTC | 6h 26m |
| 2026-07-17 | SDM6087 | - | Jul 17, 19:09 UTC | Jul 17, 19:40 UTC | 30m |
| 2026-07-17 | SDM6043 | SVO → LED | Jul 17, 12:15 UTC | Jul 17, 13:15 UTC | 1h 0m |
| 2026-07-17 | SDM6433 | SVO → ASF | Jul 17, 05:50 UTC | Jul 17, 06:20 UTC | 30m |
| 2026-07-15 | SDM6043 | SVO → LED | Jul 15, 12:30 UTC | Jul 15, 13:25 UTC | 55m |
| 2026-07-15 | SDM6433 | - | Jul 15, 06:00 UTC | Jul 15, 06:35 UTC | 35m |
| 2026-07-11 | SDM6112 | - | Jul 11, 00:05 UTC | Jul 11, 09:20 UTC | 9h 15m |
| 2026-07-10 | SDM6331 | - | Jul 10, 13:00 UTC | Jul 10, 19:00 UTC | 6h 0m |
| 2026-07-10 | SDM6923 | - | Jul 10, 08:40 UTC | Jul 10, 09:00 UTC | 20m |
| 2026-07-09 | SDM6923 | - | Jul 9, 12:35 UTC | Jul 10, 09:00 UTC | 20h 25m |
| 2026-07-09 | SDM6924 | - | Jul 9, 12:25 UTC | Jul 10, 09:00 UTC | 20h 35m |
| 2026-07-09 | SDM6524 | - | Jul 9, 02:50 UTC | Jul 9, 10:50 UTC | 8h 0m |
| 2026-07-06 | SDM6476 | - | Jul 6, 05:25 UTC | Jul 6, 08:50 UTC | 3h 25m |
| 2026-07-05 | SDM6326 | - | Jul 5, 19:55 UTC | Jul 5, 20:55 UTC | 1h 0m |
| 2026-07-05 | SDM6325 | - | Jul 5, 03:40 UTC | Jul 5, 17:50 UTC | 14h 10m |
| 2026-07-04 | SDM6441 | - | Jul 4, 21:35 UTC | Jul 5, 17:50 UTC | 20h 15m |
| 2026-07-03 | SDM6572 | - | Jul 3, 13:30 UTC | Jul 3, 17:15 UTC | 3h 45m |
| 2026-07-01 | SDM6721 | - | Jul 1, 15:10 UTC | Jul 1, 20:55 UTC | 5h 45m |
| 2026-06-30 | SDM6721 | - | Jun 30, 21:00 UTC | Jul 1, 20:30 UTC | 23h 30m |
| 2026-06-30 | SDM6721 | - | Jun 30, 16:35 UTC | Jul 1, 16:30 UTC | 23h 55m |
| 2026-06-30 | SDM6795 | - | Jun 30, 15:50 UTC | Jun 30, 22:10 UTC | 6h 20m |
| 2026-06-29 | SDM6795 | - | Jun 29, 20:35 UTC | Jun 30, 17:30 UTC | 20h 56m |
| 2026-06-29 | SDM6783 | - | Jun 29, 14:09 UTC | Jun 29, 21:09 UTC | 7h 0m |
| 2026-06-28 | SDM6784 | - | Jun 28, 19:49 UTC | Jun 29, 14:50 UTC | 19h 0m |
| 2026-06-28 | SDM6783 | - | Jun 28, 14:34 UTC | Jun 29, 14:29 UTC | 23h 55m |
| 2026-06-28 | SDM6895 | - | Jun 28, 05:29 UTC | Jun 28, 21:04 UTC | 15h 35m |
| 2026-06-27 | SDM6895 | - | Jun 27, 22:35 UTC | Jun 28, 21:04 UTC | 22h 30m |
| 2026-06-27 | SDM6895 | - | Jun 27, 21:15 UTC | Jun 28, 20:29 UTC | 23h 15m |
| 2026-06-27 | SDM6895 | - | Jun 27, 16:35 UTC | Jun 28, 15:29 UTC | 22h 55m |
| 2026-06-27 | SDM6895 | - | Jun 27, 15:55 UTC | Jun 28, 14:30 UTC | 22h 35m |
| 2026-06-26 | SDM6795 | - | Jun 26, 20:34 UTC | Jun 27, 17:20 UTC | 20h 45m |
| 2026-06-26 | SDM6795 | - | Jun 26, 19:45 UTC | Jun 27, 17:20 UTC | 21h 35m |
| 2026-06-26 | SDM6783 | - | Jun 26, 14:05 UTC | Jun 26, 21:04 UTC | 7h 0m |
| 2026-06-25 | SDM6783 | - | Jun 25, 20:14 UTC | Jun 26, 15:29 UTC | 19h 15m |
| 2026-06-25 | SDM6621 | - | Jun 25, 18:24 UTC | Jun 25, 18:39 UTC | 15m |
| 2026-06-24 | SDM6722 | - | Jun 24, 15:00 UTC | Jun 24, 20:49 UTC | 5h 50m |
| 2026-06-23 | SDM6722 | - | Jun 23, 22:34 UTC | Jun 24, 20:49 UTC | 22h 15m |
| 2026-06-23 | SDM6726 | - | Jun 23, 21:24 UTC | Jun 24, 20:30 UTC | 23h 5m |
| 2026-06-23 | SDM6726 | - | Jun 23, 16:35 UTC | Jun 24, 16:24 UTC | 23h 50m |
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-73202 page for operator, model, and routing details .