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
- 91
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- 15h ago
Current 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 |
|---|---|---|---|
| SVR624 | - | 9 | 2026-07-08 |
| SVR628 | - | 6 | 2026-07-01 |
| SVR270 | Ural Airlines | 5 | 2026-05-25 |
| SVR266 | Ural Airlines | 5 | 2026-05-05 |
| SVR106 | - | 5 | 2026-07-06 |
| SVR627 | - | 4 | 2026-07-11 |
| SVR623 | - | 4 | 2026-06-17 |
| SVR321 | Ural Airlines | 4 | 2026-05-14 |
| SVR271 | Ural Airlines | 4 | 2026-06-04 |
| SVR105 | Ural Airlines | 4 | 2026-05-01 |
| RA73804 | - | 4 | 2026-07-04 |
| SVR9165 | - | 3 | 2026-06-30 |
| SVR220 | Ural Airlines | 3 | 2026-05-19 |
| SVR219 | Ural Airlines | 3 | 2026-05-15 |
| SVR9166 | - | 2 | 2026-05-11 |
| SVR392 | Ural Airlines | 2 | 2026-05-22 |
| SVR391 | - | 2 | 2026-06-18 |
| SVR280 | Ural Airlines | 2 | 2026-04-17 |
| SVR174 | - | 2 | 2026-06-24 |
| SVR9655 | - | 1 | 2026-06-28 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | SVR548 | - | Jul 13, 09:50 UTC | Jul 13, 16:50 UTC | 7h 0m |
| 2026-07-11 | SVR627 | - | Jul 11, 09:25 UTC | Jul 11, 10:40 UTC | 1h 15m |
| 2026-07-08 | SVR624 | - | Jul 8, 00:25 UTC | Jul 8, 07:00 UTC | 6h 35m |
| 2026-07-06 | SVR106 | - | Jul 6, 14:35 UTC | Jul 7, 03:55 UTC | 13h 20m |
| 2026-07-04 | RA73804 | - | Jul 4, 10:40 UTC | Jul 4, 14:10 UTC | 3h 30m |
| 2026-07-02 | SVR624 | - | Jul 2, 22:50 UTC | Jul 2, 23:25 UTC | 35m |
| 2026-07-01 | SVR628 | - | Jul 1, 15:05 UTC | Jul 1, 17:00 UTC | 1h 55m |
| 2026-06-30 | SVR9165 | - | Jun 30, 07:05 UTC | Jul 1, 01:15 UTC | 18h 10m |
| 2026-06-30 | SVR9165 | - | Jun 30, 06:55 UTC | Jul 1, 01:15 UTC | 18h 20m |
| 2026-06-28 | SVR9655 | - | Jun 28, 21:40 UTC | Jun 28, 22:15 UTC | 35m |
| 2026-06-28 | SVR106 | - | Jun 28, 01:10 UTC | Jun 28, 22:15 UTC | 21h 5m |
| 2026-06-24 | SVR624 | - | Jun 24, 23:34 UTC | Jun 25, 00:14 UTC | 40m |
| 2026-06-24 | SVR624 | - | Jun 24, 18:15 UTC | Jun 24, 18:25 UTC | 10m |
| 2026-06-24 | SVR174 | - | Jun 24, 16:09 UTC | Jun 24, 16:24 UTC | 15m |
| 2026-06-19 | SVR209 | - | Jun 19, 12:34 UTC | Jun 19, 13:04 UTC | 30m |
| 2026-06-18 | SVR391 | - | Jun 18, 16:45 UTC | Jun 18, 18:00 UTC | 1h 15m |
| 2026-06-17 | SVR623 | - | Jun 17, 14:45 UTC | Jun 18, 05:10 UTC | 14h 25m |
| 2026-06-17 | SVR623 | - | Jun 17, 05:05 UTC | Jun 18, 05:00 UTC | 23h 55m |
| 2026-06-17 | SVR623 | - | Jun 17, 04:50 UTC | Jun 17, 23:20 UTC | 18h 30m |
| 2026-06-16 | SVR624 | - | Jun 16, 23:05 UTC | Jun 17, 23:00 UTC | 23h 55m |
| 2026-06-15 | SVR210 | KRR → SVX | Jun 15, 15:50 UTC | Jun 15, 15:59 UTC | 10m |
| 2026-06-14 | SVR9165 | - | Jun 14, 13:25 UTC | Jun 15, 02:20 UTC | 12h 54m |
| 2026-06-12 | SVR109 | DME → KRR | Jun 12, 11:10 UTC | Jun 12, 11:35 UTC | 25m |
| 2026-06-11 | SVR149 | SVX → GDZ | Jun 11, 05:55 UTC | Jun 11, 07:00 UTC | 1h 5m |
| 2026-06-10 | SVR2968 | DYU → KRR | Jun 10, 06:05 UTC | Jun 10, 06:55 UTC | 50m |
| 2026-06-05 | SVR8253 | DME → DYU | Jun 5, 23:10 UTC | Jun 6, 16:20 UTC | 17h 10m |
| 2026-06-04 | SVR271 | DME → SVX | Jun 4, 21:05 UTC | Jun 4, 21:25 UTC | 20m |
| 2026-06-04 | SVR628 | KGD → DME | Jun 4, 16:00 UTC | Jun 4, 17:50 UTC | 1h 50m |
| 2026-06-04 | SVR627 | DME → KGD | Jun 4, 13:50 UTC | Jun 4, 14:25 UTC | 35m |
| 2026-06-03 | SVR106 | IKT → DME | Jun 3, 01:10 UTC | Jun 3, 08:40 UTC | 7h 30m |
| 2026-06-02 | SVR106 | IKT → DME | Jun 2, 03:45 UTC | Jun 3, 01:55 UTC | 22h 10m |
| 2026-05-30 | SVR624 | SVX → HTA | May 30, 22:25 UTC | May 30, 23:00 UTC | 35m |
| 2026-05-30 | RA73804 | - | May 30, 10:45 UTC | May 30, 17:55 UTC | 7h 10m |
| 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 |
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 .