sensors Mode-S transponder
15205A
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73818 · AIRBUS A-320
- Hex
- 15205A
- Octal
- 05220132
- Decimal
- 1,384,538
- Country
- RU
- Tail
- RA-73818
- Type
- A320
- Flights observed
- 81
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- 2h ago
Last known position
Country allocation
The ICAO 24-bit address 15205A 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 |
|---|---|---|---|
| SVR2318 | - | 6 | 2026-05-27 |
| SVR392 | - | 5 | 2026-07-10 |
| SVR391 | - | 4 | 2026-07-11 |
| SVR219 | Ural Airlines | 4 | 2026-05-15 |
| SVR623 | Ural Airlines | 3 | 2026-06-01 |
| SVR2734 | Ural Airlines | 3 | 2026-05-30 |
| SVR2720 | - | 3 | 2026-07-13 |
| SVR2719 | - | 3 | 2026-07-14 |
| SVR270 | Ural Airlines | 3 | 2026-05-23 |
| SVR263 | Ural Airlines | 3 | 2026-05-07 |
| SVR404 | Ural Airlines | 2 | 2026-04-15 |
| SVR2904 | Ural Airlines | 2 | 2026-05-28 |
| SVR2879 | Ural Airlines | 2 | 2026-06-10 |
| SVR2710 | Ural Airlines | 2 | 2026-05-24 |
| SVR205 | Ural Airlines | 2 | 2026-05-09 |
| SVR181 | - | 2 | 2026-07-12 |
| SVR9165 | - | 1 | 2026-06-19 |
| SVR9138 | - | 1 | 2026-04-28 |
| SVR9137 | - | 1 | 2026-04-28 |
| SVR624 | Ural Airlines | 1 | 2026-06-05 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | SVR2719 | - | Jul 14, 06:55 UTC | Jul 14, 14:00 UTC | 7h 5m |
| 2026-07-13 | SVR2720 | - | Jul 13, 11:25 UTC | Jul 14, 08:05 UTC | 20h 40m |
| 2026-07-12 | SVR181 | - | Jul 12, 09:40 UTC | Jul 12, 10:15 UTC | 35m |
| 2026-07-11 | SVR391 | - | Jul 11, 07:45 UTC | Jul 11, 08:40 UTC | 55m |
| 2026-07-10 | SVR392 | - | Jul 10, 14:00 UTC | Jul 10, 15:00 UTC | 1h 0m |
| 2026-07-10 | SVR391 | - | Jul 10, 07:20 UTC | Jul 10, 12:10 UTC | 4h 50m |
| 2026-07-09 | SVR392 | - | Jul 9, 19:05 UTC | Jul 9, 20:25 UTC | 1h 20m |
| 2026-07-07 | SVR2719 | - | Jul 7, 06:05 UTC | Jul 7, 13:40 UTC | 7h 35m |
| 2026-07-06 | SVR150 | - | Jul 6, 07:30 UTC | Jul 7, 06:25 UTC | 22h 55m |
| 2026-07-01 | SVR392 | - | Jul 1, 10:20 UTC | Jul 1, 11:35 UTC | 1h 15m |
| 2026-06-30 | SVR391 | - | Jun 30, 17:40 UTC | Jul 1, 08:55 UTC | 15h 15m |
| 2026-06-26 | SVR1338 | - | Jun 26, 03:50 UTC | Jun 26, 04:14 UTC | 25m |
| 2026-06-24 | SVR2612 | - | Jun 24, 14:15 UTC | Jun 24, 14:34 UTC | 20m |
| 2026-06-23 | SVR2167 | - | Jun 23, 17:15 UTC | Jun 24, 14:29 UTC | 21h 15m |
| 2026-06-23 | SVR2804 | FRU → DME | Jun 23, 13:55 UTC | Jun 23, 17:39 UTC | 3h 45m |
| 2026-06-22 | SVR2772 | SKD → DME | Jun 22, 01:05 UTC | Jun 22, 02:00 UTC | 55m |
| 2026-06-20 | SVR2633 | DME → EVN | Jun 20, 22:50 UTC | Jun 20, 23:10 UTC | 20m |
| 2026-06-19 | SVR9165 | - | Jun 19, 13:14 UTC | Jun 19, 13:54 UTC | 40m |
| 2026-06-15 | SVR2641 | LED → LBD | Jun 15, 15:55 UTC | Jun 15, 16:09 UTC | 15m |
| 2026-06-15 | SVR392 | - | Jun 15, 11:30 UTC | Jun 15, 12:39 UTC | 1h 10m |
| 2026-06-15 | SVR391 | - | Jun 15, 08:49 UTC | Jun 15, 09:40 UTC | 50m |
| 2026-06-14 | SVR181 | LED → AER | Jun 14, 09:55 UTC | Jun 14, 10:15 UTC | 20m |
| 2026-06-12 | SVR620 | CEK → AER | Jun 12, 08:50 UTC | Jun 12, 09:55 UTC | 1h 5m |
| 2026-06-11 | SVR1323 | CEK → KRR | Jun 11, 07:15 UTC | Jun 11, 07:50 UTC | 35m |
| 2026-06-10 | SVR2879 | LED → DYU | Jun 10, 14:30 UTC | Jun 10, 14:40 UTC | 10m |
| 2026-06-08 | SVR392 | KGD → LED | Jun 8, 10:20 UTC | Jun 8, 11:45 UTC | 1h 25m |
| 2026-06-07 | SVR149 | SVX → GDZ | Jun 7, 03:45 UTC | Jun 7, 18:55 UTC | 15h 10m |
| 2026-06-05 | SVR624 | SVX → HTA | Jun 5, 20:35 UTC | Jun 5, 20:55 UTC | 20m |
| 2026-06-03 | SVR2879 | LED → DYU | Jun 3, 14:55 UTC | Jun 3, 15:10 UTC | 15m |
| 2026-06-01 | SVR623 | HTA → SVX | Jun 1, 09:10 UTC | Jun 2, 04:05 UTC | 18h 55m |
| 2026-06-01 | SVR623 | HTA → SVX | Jun 1, 04:50 UTC | Jun 2, 04:05 UTC | 23h 15m |
| 2026-05-31 | SVR623 | HTA → SVX | May 31, 19:30 UTC | Jun 1, 16:20 UTC | 20h 50m |
| 2026-05-30 | SVR2642 | LBD → LED | May 30, 20:55 UTC | May 31, 19:40 UTC | 22h 45m |
| 2026-05-30 | SVR2734 | OSS → LED | May 30, 08:40 UTC | May 30, 21:05 UTC | 12h 25m |
| 2026-05-29 | SVR2734 | OSS → LED | May 29, 14:20 UTC | May 30, 08:50 UTC | 18h 30m |
| 2026-05-28 | SVR2904 | OSS → SVX | May 28, 03:10 UTC | May 28, 14:15 UTC | 11h 5m |
| 2026-05-27 | SVR2904 | OSS → SVX | May 27, 16:50 UTC | May 28, 14:15 UTC | 21h 25m |
| 2026-05-27 | SVR2318 | - | May 27, 06:44 UTC | May 28, 03:20 UTC | 20h 35m |
| 2026-05-27 | SVR2318 | - | May 27, 01:29 UTC | May 27, 16:55 UTC | 15h 26m |
| 2026-05-26 | SVR2318 | - | May 26, 22:15 UTC | May 27, 16:55 UTC | 18h 41m |
| 2026-05-26 | SVR2318 | - | May 26, 17:09 UTC | May 27, 08:00 UTC | 14h 50m |
| 2026-05-24 | SVR2710 | OSS → DME | May 24, 13:35 UTC | May 25, 04:10 UTC | 14h 35m |
| 2026-05-23 | SVR2710 | OSS → DME | May 23, 16:35 UTC | May 24, 14:15 UTC | 21h 40m |
| 2026-05-23 | SVR270 | SVX → DME | May 23, 16:25 UTC | May 24, 14:15 UTC | 21h 50m |
| 2026-05-22 | SVR270 | SVX → DME | May 22, 23:55 UTC | May 23, 17:05 UTC | 17h 9m |
| 2026-05-22 | SVR2873 | CEK → OSS | May 22, 18:15 UTC | May 23, 16:30 UTC | 22h 14m |
| 2026-05-22 | SVR2874 | OSS → CEK | May 22, 15:55 UTC | May 23, 13:20 UTC | 21h 24m |
| 2026-05-21 | SVR2805 | KJA → OSS | May 21, 15:35 UTC | May 21, 16:10 UTC | 35m |
| 2026-05-21 | SVR2806 | OSS → KJA | May 21, 02:45 UTC | May 21, 10:35 UTC | 7h 50m |
| 2026-05-20 | SVR2318 | - | May 20, 06:35 UTC | May 20, 16:55 UTC | 10h 20m |
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-73818 page for operator, model, and routing details .