sensors Mode-S transponder
15204C
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73804 · AIRBUS A-320
- Hex
- 15204C
- Octal
- 05220114
- Decimal
- 1,384,524
- Country
- RU
- Tail
- RA-73804
- Type
- A320
- Flights observed
- 58
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 15204C 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 |
|---|---|---|---|
| SVR270 | Ural Airlines | 5 | 2026-05-25 |
| SVR266 | Ural Airlines | 5 | 2026-05-05 |
| SVR628 | Ural Airlines | 4 | 2026-05-16 |
| SVR321 | Ural Airlines | 4 | 2026-05-14 |
| SVR105 | Ural Airlines | 4 | 2026-05-01 |
| SVR624 | Ural Airlines | 3 | 2026-05-09 |
| SVR271 | Ural Airlines | 3 | 2026-05-22 |
| SVR220 | Ural Airlines | 3 | 2026-05-19 |
| SVR219 | Ural Airlines | 3 | 2026-05-15 |
| SVR9166 | - | 2 | 2026-05-11 |
| SVR627 | Ural Airlines | 2 | 2026-04-15 |
| SVR392 | Ural Airlines | 2 | 2026-05-22 |
| SVR280 | Ural Airlines | 2 | 2026-04-17 |
| RA73804 | - | 2 | 2026-05-25 |
| SVR9138 | - | 1 | 2026-05-27 |
| SVR9137 | - | 1 | 2026-05-29 |
| SVR623 | Ural Airlines | 1 | 2026-05-09 |
| SVR391 | Ural Airlines | 1 | 2026-05-03 |
| SVR387 | - | 1 | 2026-04-13 |
| SVR366 | Ural Airlines | 1 | 2026-05-26 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | SVR9137 | - | May 29, 01:30 UTC | May 29, 02:15 UTC | 45m |
| 2026-05-27 | SVR9138 | - | May 27, 08:00 UTC | May 27, 22:10 UTC | 14h 10m |
| 2026-05-26 | SVR366 | VVO → IKT | May 26, 10:29 UTC | May 27, 08:40 UTC | 22h 11m |
| 2026-05-25 | SVR270 | SVX → DME | May 25, 16:55 UTC | May 26, 10:39 UTC | 17h 45m |
| 2026-05-25 | SVR270 | SVX → DME | May 25, 12:25 UTC | May 26, 10:39 UTC | 22h 14m |
| 2026-05-25 | RA73804 | - | May 25, 06:00 UTC | May 25, 06:55 UTC | 55m |
| 2026-05-24 | RA73804 | - | May 24, 10:50 UTC | May 25, 06:55 UTC | 20h 5m |
| 2026-05-24 | SVR094 | HTA → DME | May 24, 06:25 UTC | May 24, 07:10 UTC | 45m |
| 2026-05-22 | SVR271 | DME → SVX | May 22, 22:30 UTC | May 22, 22:45 UTC | 15m |
| 2026-05-22 | SVR192 | LED → DME | May 22, 20:55 UTC | May 22, 21:05 UTC | 10m |
| 2026-05-22 | SVR392 | KGD → LED | May 22, 11:50 UTC | May 22, 12:40 UTC | 50m |
| 2026-05-20 | SVR205 | SVX → MRV | May 20, 10:35 UTC | May 20, 11:35 UTC | 1h 0m |
| 2026-05-19 | SVR220 | AER → SVX | May 19, 11:40 UTC | May 19, 17:25 UTC | 5h 45m |
| 2026-05-18 | SVR220 | AER → SVX | May 18, 15:10 UTC | May 19, 12:35 UTC | 21h 24m |
| 2026-05-18 | SVR220 | AER → SVX | May 18, 14:45 UTC | May 19, 12:35 UTC | 21h 49m |
| 2026-05-18 | SVR272 | SVX → DME | May 18, 05:30 UTC | May 18, 06:01 UTC | 30m |
| 2026-05-16 | SVR628 | KGD → DME | May 16, 12:45 UTC | May 16, 21:25 UTC | 8h 40m |
| 2026-05-15 | SVR628 | KGD → DME | May 15, 16:25 UTC | May 16, 14:16 UTC | 21h 51m |
| 2026-05-15 | SVR219 | SVX → AER | May 15, 07:20 UTC | May 15, 17:05 UTC | 9h 44m |
| 2026-05-14 | SVR219 | SVX → AER | May 14, 18:05 UTC | May 15, 17:00 UTC | 22h 54m |
| 2026-05-14 | SVR321 | SVX → AER | May 14, 14:15 UTC | May 15, 08:20 UTC | 18h 5m |
| 2026-05-14 | SVR321 | SVX → AER | May 14, 09:20 UTC | May 15, 08:20 UTC | 23h 0m |
| 2026-05-14 | SVR321 | SVX → AER | May 14, 03:05 UTC | May 14, 19:00 UTC | 15h 55m |
| 2026-05-13 | SVR321 | SVX → AER | May 13, 17:05 UTC | May 14, 15:15 UTC | 22h 10m |
| 2026-05-11 | SVR9166 | - | May 11, 13:05 UTC | May 12, 08:05 UTC | 19h 1m |
| 2026-05-10 | SVR9166 | - | May 10, 17:34 UTC | May 11, 16:05 UTC | 22h 30m |
| 2026-05-09 | SVR623 | HTA → SVX | May 9, 23:05 UTC | May 10, 17:55 UTC | 18h 50m |
| 2026-05-09 | SVR624 | SVX → HTA | May 9, 22:39 UTC | May 10, 17:55 UTC | 19h 15m |
| 2026-05-09 | SVR624 | SVX → HTA | May 9, 16:05 UTC | May 9, 18:20 UTC | 2h 15m |
| 2026-05-09 | SVR174 | KHV → SVX | May 9, 12:40 UTC | May 9, 13:15 UTC | 35m |
| 2026-05-08 | SVR2890 | OSS → SVX | May 8, 03:44 UTC | May 8, 03:55 UTC | 10m |
| 2026-05-05 | SVR266 | SVX → DME | May 5, 16:20 UTC | May 5, 21:35 UTC | 5h 15m |
| 2026-05-04 | SVR266 | SVX → DME | May 4, 17:50 UTC | May 5, 17:00 UTC | 23h 11m |
| 2026-05-04 | SVR624 | SVX → HTA | May 4, 16:20 UTC | May 4, 16:40 UTC | 20m |
| 2026-05-04 | SVR392 | KGD → LED | May 4, 11:05 UTC | May 4, 11:50 UTC | 45m |
| 2026-05-03 | SVR391 | LED → KGD | May 3, 17:00 UTC | May 4, 09:00 UTC | 16h 0m |
| 2026-05-01 | SVR105 | DME → IKT | May 1, 18:15 UTC | May 2, 02:00 UTC | 7h 45m |
| 2026-05-01 | SVR105 | DME → IKT | May 1, 01:20 UTC | May 1, 20:55 UTC | 19h 35m |
| 2026-04-30 | SVR106 | IKT → DME | Apr 30, 23:55 UTC | May 1, 00:05 UTC | 10m |
| 2026-04-30 | SVR105 | DME → IKT | Apr 30, 01:20 UTC | Apr 30, 20:40 UTC | 19h 20m |
| 2026-04-29 | SVR105 | DME → IKT | Apr 29, 17:05 UTC | Apr 30, 02:05 UTC | 8h 59m |
| 2026-04-27 | SVR270 | SVX → DME | Apr 27, 16:05 UTC | Apr 27, 16:50 UTC | 45m |
| 2026-04-27 | SVR219 | SVX → AER | Apr 27, 09:00 UTC | Apr 27, 09:25 UTC | 25m |
| 2026-04-26 | SVR266 | SVX → DME | Apr 26, 05:40 UTC | Apr 26, 16:45 UTC | 11h 5m |
| 2026-04-25 | SVR266 | SVX → DME | Apr 25, 19:05 UTC | Apr 26, 16:45 UTC | 21h 40m |
| 2026-04-25 | SVR273 | DME → SVX | Apr 25, 08:50 UTC | Apr 26, 05:40 UTC | 20h 50m |
| 2026-04-24 | SVR270 | SVX → DME | Apr 24, 16:00 UTC | Apr 25, 09:00 UTC | 17h 0m |
| 2026-04-21 | SVR271 | DME → SVX | Apr 21, 21:25 UTC | Apr 21, 23:00 UTC | 1h 35m |
| 2026-04-19 | SVR266 | SVX → DME | Apr 19, 14:00 UTC | Apr 19, 14:10 UTC | 10m |
| 2026-04-17 | SVR280 | AER → DME | Apr 17, 14:45 UTC | Apr 17, 15:00 UTC | 14m |
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-73804 page for operator, model, and routing details .