sensors Mode-S transponder
15204E
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73806 · AIRBUS A-320
- Hex
- 15204E
- Octal
- 05220116
- Decimal
- 1,384,526
- Country
- RU
- Tail
- RA-73806
- Type
- A320
- Flights observed
- 47
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- 19h ago
Last known position
Country allocation
The ICAO 24-bit address 15204E 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 |
|---|---|---|---|
| SVR391 | Ural Airlines | 7 | 2026-05-14 |
| SVR392 | Ural Airlines | 5 | 2026-05-14 |
| SVR106 | Ural Airlines | 3 | 2026-05-29 |
| TVR392 | - | 2 | 2026-04-14 |
| SVR620 | Ural Airlines | 2 | 2026-04-25 |
| SVR548 | Ural Airlines | 2 | 2026-05-26 |
| SVR504 | Ural Airlines | 2 | 2026-05-07 |
| SVR2955 | Ural Airlines | 2 | 2026-05-09 |
| SVR2920 | Ural Airlines | 2 | 2026-04-18 |
| SVR628 | Ural Airlines | 1 | 2026-05-28 |
| SVR627 | Ural Airlines | 1 | 2026-05-28 |
| SVR2986 | Ural Airlines | 1 | 2026-05-02 |
| SVR2954 | Ural Airlines | 1 | 2026-05-05 |
| SVR2930 | Ural Airlines | 1 | 2026-04-24 |
| SVR2919 | Ural Airlines | 1 | 2026-04-18 |
| SVR2890 | Ural Airlines | 1 | 2026-05-14 |
| SVR2873 | Ural Airlines | 1 | 2026-04-30 |
| SVR2812 | Ural Airlines | 1 | 2026-04-28 |
| SVR272 | Ural Airlines | 1 | 2026-05-10 |
| SVR2641 | - | 1 | 2026-04-15 |
Recent flights last 47
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | SVR106 | IKT → DME | May 29, 20:10 UTC | May 30, 02:06 UTC | 5h 56m |
| 2026-05-29 | SVR105 | DME → IKT | May 29, 16:45 UTC | May 29, 17:10 UTC | 25m |
| 2026-05-28 | SVR628 | KGD → DME | May 28, 12:35 UTC | May 29, 04:45 UTC | 16h 10m |
| 2026-05-28 | SVR627 | DME → KGD | May 28, 08:55 UTC | May 28, 10:55 UTC | 2h 0m |
| 2026-05-26 | SVR548 | AER → LED | May 26, 08:50 UTC | May 26, 09:09 UTC | 20m |
| 2026-05-25 | SVR548 | AER → LED | May 25, 08:50 UTC | May 25, 09:25 UTC | 35m |
| 2026-05-20 | SVR174 | KHV → SVX | May 20, 13:20 UTC | May 20, 14:25 UTC | 1h 5m |
| 2026-05-19 | SVR167 | DME → KGD | May 19, 15:50 UTC | May 19, 16:25 UTC | 35m |
| 2026-05-18 | SVR106 | IKT → DME | May 18, 02:20 UTC | May 18, 04:40 UTC | 2h 20m |
| 2026-05-17 | SVR106 | IKT → DME | May 17, 05:35 UTC | May 18, 04:40 UTC | 23h 5m |
| 2026-05-17 | SVR262 | SVX → DME | May 17, 04:45 UTC | May 18, 02:55 UTC | 22h 10m |
| 2026-05-14 | SVR2890 | OSS → SVX | May 14, 21:35 UTC | May 15, 02:55 UTC | 5h 20m |
| 2026-05-14 | SVR392 | KGD → LED | May 14, 10:25 UTC | May 14, 11:40 UTC | 1h 15m |
| 2026-05-14 | SVR391 | LED → KGD | May 14, 07:45 UTC | May 14, 08:45 UTC | 1h 0m |
| 2026-05-13 | SVR391 | LED → KGD | May 13, 08:00 UTC | May 13, 08:55 UTC | 55m |
| 2026-05-11 | SVR223 | SVX → LED | May 11, 06:45 UTC | May 11, 07:40 UTC | 55m |
| 2026-05-10 | SVR272 | SVX → DME | May 10, 04:55 UTC | May 10, 06:04 UTC | 1h 10m |
| 2026-05-09 | SVR2955 | SVX → LBD | May 9, 20:10 UTC | May 10, 02:00 UTC | 5h 50m |
| 2026-05-09 | SVR220 | AER → SVX | May 9, 15:45 UTC | May 9, 15:55 UTC | 10m |
| 2026-05-09 | SVR219 | SVX → AER | May 9, 08:45 UTC | May 9, 10:25 UTC | 1h 40m |
| 2026-05-07 | SVR2955 | SVX → LBD | May 7, 21:40 UTC | May 8, 03:09 UTC | 5h 29m |
| 2026-05-07 | SVR504 | KGD → SVX | May 7, 16:20 UTC | May 7, 17:35 UTC | 1h 15m |
| 2026-05-06 | SVR2165 | SVX → OSS | May 6, 00:40 UTC | May 6, 06:20 UTC | 5h 40m |
| 2026-05-05 | SVR2954 | DYU → SVX | May 5, 04:25 UTC | May 6, 00:50 UTC | 20h 25m |
| 2026-05-03 | SVR093 | DME → HTA | May 3, 20:35 UTC | May 3, 21:00 UTC | 25m |
| 2026-05-02 | SVR504 | KGD → SVX | May 2, 09:50 UTC | May 2, 15:45 UTC | 5h 55m |
| 2026-05-02 | SVR2986 | FRU → SVX | May 2, 01:40 UTC | May 2, 06:55 UTC | 5h 15m |
| 2026-04-30 | SVR2873 | CEK → OSS | Apr 30, 12:05 UTC | May 1, 03:05 UTC | 15h 0m |
| 2026-04-28 | SVR2812 | DYU → CEK | Apr 28, 19:10 UTC | Apr 28, 19:20 UTC | 10m |
| 2026-04-25 | SVR620 | CEK → AER | Apr 25, 22:10 UTC | Apr 26, 11:15 UTC | 13h 5m |
| 2026-04-24 | SVR2930 | DYU → KJA | Apr 24, 11:45 UTC | Apr 24, 22:25 UTC | 10h 40m |
| 2026-04-22 | SVR620 | CEK → AER | Apr 22, 05:35 UTC | Apr 22, 06:40 UTC | 1h 5m |
| 2026-04-18 | SVR2920 | LBD → KJA | Apr 18, 08:40 UTC | Apr 18, 09:20 UTC | 40m |
| 2026-04-18 | SVR2919 | KJA → LBD | Apr 18, 02:20 UTC | Apr 18, 02:55 UTC | 35m |
| 2026-04-17 | SVR2920 | LBD → KJA | Apr 17, 23:20 UTC | Apr 18, 14:20 UTC | 15h 0m |
| 2026-04-17 | SVR392 | KGD → LED | Apr 17, 11:25 UTC | Apr 17, 12:50 UTC | 1h 25m |
| 2026-04-17 | SVR391 | LED → KGD | Apr 17, 09:20 UTC | Apr 17, 10:00 UTC | 40m |
| 2026-04-17 | SVR391 | LED → KGD | Apr 17, 09:05 UTC | Apr 17, 09:15 UTC | 10m |
| 2026-04-16 | SVR392 | KGD → LED | Apr 16, 11:09 UTC | Apr 16, 11:44 UTC | 35m |
| 2026-04-16 | SVR392 | KGD → LED | Apr 16, 10:25 UTC | Apr 16, 11:04 UTC | 40m |
| 2026-04-16 | SVR391 | LED → KGD | Apr 16, 07:54 UTC | Apr 16, 08:54 UTC | 1h 0m |
| 2026-04-15 | SVR2641 | LED → LED | Apr 15, 17:05 UTC | Apr 15, 17:15 UTC | 10m |
| 2026-04-14 | TVR392 | - | Apr 14, 10:50 UTC | Apr 14, 11:35 UTC | 45m |
| 2026-04-14 | TVR392 | - | Apr 14, 10:10 UTC | Apr 14, 11:05 UTC | 55m |
| 2026-04-14 | SVR391 | LED → KGD | Apr 14, 07:40 UTC | Apr 14, 08:40 UTC | 1h 0m |
| 2026-04-13 | SVR392 | - | Apr 13, 12:45 UTC | Apr 13, 14:10 UTC | 1h 25m |
| 2026-04-13 | SVR391 | - | Apr 13, 10:25 UTC | Apr 13, 11:10 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-73806 page for operator, model, and routing details .