sensors Mode-S transponder
15205D
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73821 · AIRBUS A-320
- Hex
- 15205D
- Octal
- 05220135
- Decimal
- 1,384,541
- Country
- RU
- Tail
- RA-73821
- Type
- A320
- Flights observed
- 39
- Distinct callsigns
- 11
- Country
- RU
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 15205D 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 11 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| SVR350 | Ural Airlines | 16 | 2026-05-24 |
| SVR623 | Ural Airlines | 5 | 2026-05-26 |
| SVR349 | Ural Airlines | 5 | 2026-05-23 |
| SVR300 | Ural Airlines | 4 | 2026-05-22 |
| SVR624 | Ural Airlines | 3 | 2026-04-28 |
| SVSR300 | - | 1 | 2026-05-21 |
| SVR572 | Ural Airlines | 1 | 2026-05-27 |
| SVR403 | Ural Airlines | 1 | 2026-05-03 |
| SVR299 | Ural Airlines | 1 | 2026-05-18 |
| SVR174 | Ural Airlines | 1 | 2026-04-28 |
| SVR173 | Ural Airlines | 1 | 2026-05-27 |
Recent flights last 39
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-27 | SVR572 | VVO → SVX | May 27, 15:50 UTC | May 28, 10:00 UTC | 18h 10m |
| 2026-05-27 | SVR173 | SVX → KHV | May 27, 14:50 UTC | May 28, 10:00 UTC | 19h 10m |
| 2026-05-26 | SVR623 | HTA → SVX | May 26, 22:39 UTC | May 27, 16:20 UTC | 17h 41m |
| 2026-05-26 | SVR623 | HTA → SVX | May 26, 16:45 UTC | May 27, 14:55 UTC | 22h 10m |
| 2026-05-24 | SVR350 | BQS → DME | May 24, 19:25 UTC | May 25, 09:30 UTC | 14h 5m |
| 2026-05-23 | SVR349 | DME → BQS | May 23, 19:20 UTC | May 23, 19:45 UTC | 25m |
| 2026-05-22 | SVR300 | SVX → DME | May 22, 12:00 UTC | May 22, 12:45 UTC | 45m |
| 2026-05-21 | SVSR300 | - | May 21, 12:05 UTC | May 21, 12:45 UTC | 40m |
| 2026-05-20 | SVR623 | HTA → SVX | May 20, 10:05 UTC | May 20, 10:15 UTC | 10m |
| 2026-05-19 | SVR623 | HTA → SVX | May 19, 23:25 UTC | May 20, 06:20 UTC | 6h 56m |
| 2026-05-18 | SVR299 | DME → SVX | May 18, 16:25 UTC | May 18, 16:35 UTC | 10m |
| 2026-05-15 | SVR350 | BQS → DME | May 15, 09:10 UTC | May 15, 09:55 UTC | 45m |
| 2026-05-13 | SVR300 | SVX → DME | May 13, 12:25 UTC | May 13, 12:35 UTC | 10m |
| 2026-05-11 | SVR349 | DME → BQS | May 11, 19:15 UTC | May 12, 08:30 UTC | 13h 15m |
| 2026-05-11 | SVR350 | BQS → DME | May 11, 09:20 UTC | May 12, 08:30 UTC | 23h 11m |
| 2026-05-11 | SVR350 | BQS → DME | May 11, 08:05 UTC | May 11, 19:45 UTC | 11h 40m |
| 2026-05-10 | SVR350 | BQS → DME | May 10, 19:19 UTC | May 11, 19:15 UTC | 23h 56m |
| 2026-05-10 | SVR349 | DME → BQS | May 10, 08:35 UTC | May 10, 19:45 UTC | 11h 10m |
| 2026-05-09 | SVR349 | DME → BQS | May 9, 19:19 UTC | May 10, 19:15 UTC | 23h 55m |
| 2026-05-09 | SVR349 | DME → BQS | May 9, 19:14 UTC | May 10, 09:00 UTC | 13h 45m |
| 2026-05-07 | SVR300 | SVX → DME | May 7, 10:40 UTC | May 7, 15:20 UTC | 4h 40m |
| 2026-05-06 | SVR350 | BQS → DME | May 6, 09:00 UTC | May 6, 09:45 UTC | 45m |
| 2026-05-04 | SVR623 | HTA → SVX | May 4, 04:39 UTC | May 4, 05:30 UTC | 50m |
| 2026-05-03 | SVR403 | SVX → KGD | May 3, 13:55 UTC | May 3, 14:40 UTC | 45m |
| 2026-04-28 | SVR624 | SVX → HTA | Apr 28, 16:20 UTC | Apr 28, 23:54 UTC | 7h 35m |
| 2026-04-28 | SVR174 | KHV → SVX | Apr 28, 12:55 UTC | Apr 28, 13:45 UTC | 50m |
| 2026-04-27 | SVR350 | BQS → DME | Apr 27, 08:50 UTC | Apr 27, 09:35 UTC | 45m |
| 2026-04-24 | SVR350 | BQS → DME | Apr 24, 19:40 UTC | Apr 25, 09:20 UTC | 13h 40m |
| 2026-04-24 | SVR350 | BQS → DME | Apr 24, 08:05 UTC | Apr 24, 19:55 UTC | 11h 50m |
| 2026-04-23 | SVR300 | SVX → DME | Apr 23, 11:55 UTC | Apr 24, 08:25 UTC | 20h 29m |
| 2026-04-22 | SVR350 | BQS → DME | Apr 22, 07:55 UTC | Apr 22, 08:25 UTC | 30m |
| 2026-04-21 | SVR350 | BQS → DME | Apr 21, 08:10 UTC | Apr 21, 08:40 UTC | 30m |
| 2026-04-17 | SVR624 | SVX → HTA | Apr 17, 23:40 UTC | Apr 17, 23:50 UTC | 10m |
| 2026-04-17 | SVR624 | SVX → HTA | Apr 17, 22:05 UTC | Apr 17, 22:40 UTC | 35m |
| 2026-04-15 | SVR350 | BQS → DME | Apr 15, 09:00 UTC | Apr 15, 09:20 UTC | 20m |
| 2026-04-15 | SVR350 | BQS → DME | Apr 15, 08:01 UTC | Apr 15, 08:55 UTC | 55m |
| 2026-04-14 | SVR350 | BQS → DME | Apr 14, 09:10 UTC | Apr 14, 09:30 UTC | 20m |
| 2026-04-14 | SVR350 | BQS → DME | Apr 14, 08:10 UTC | Apr 14, 09:05 UTC | 55m |
| 2026-04-13 | SVR350 | BQS → DME | Apr 13, 09:00 UTC | Apr 13, 09:45 UTC | 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-73821 page for operator, model, and routing details .