sensors Mode-S transponder
15204B
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73803 · AIRBUS A-320
- Hex
- 15204B
- Octal
- 05220113
- Decimal
- 1,384,523
- Country
- RU
- Tail
- RA-73803
- Type
- A320
- Flights observed
- 116
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- 3h ago
Last known position
Country allocation
The ICAO 24-bit address 15204B 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 |
|---|---|---|---|
| RA73803 | - | 13 | 2026-07-05 |
| SVR093 | - | 6 | 2026-07-16 |
| SVR627 | - | 5 | 2026-07-13 |
| SVR628 | Ural Airlines | 4 | 2026-05-29 |
| SVR624 | - | 4 | 2026-06-19 |
| SVR321 | Ural Airlines | 4 | 2026-05-12 |
| SVR150 | Ural Airlines | 4 | 2026-06-06 |
| SVR105 | - | 4 | 2026-07-17 |
| SVR9138 | - | 3 | 2026-06-11 |
| SVR2929 | Ural Airlines | 3 | 2026-05-27 |
| SVR274 | - | 3 | 2026-07-04 |
| SVR270 | Ural Airlines | 3 | 2026-04-26 |
| SVR263 | Ural Airlines | 3 | 2026-04-29 |
| SVR174 | - | 3 | 2026-06-30 |
| SVR9384 | - | 2 | 2026-05-15 |
| SVR9169 | - | 2 | 2026-06-08 |
| SVR392 | - | 2 | 2026-06-25 |
| SVR391 | - | 2 | 2026-06-25 |
| SVR2662 | Ural Airlines | 2 | 2026-04-26 |
| SVR266 | Ural Airlines | 2 | 2026-05-19 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-17 | SVR105 | - | Jul 17, 20:04 UTC | Jul 17, 23:14 UTC | 3h 10m |
| 2026-07-17 | SVR1344 | MCX → DME | Jul 17, 16:55 UTC | Jul 17, 17:09 UTC | 15m |
| 2026-07-17 | SVR1343 | DME → MCX | Jul 17, 10:55 UTC | Jul 17, 11:35 UTC | 40m |
| 2026-07-16 | SVR093 | - | Jul 16, 20:39 UTC | Jul 17, 08:04 UTC | 11h 25m |
| 2026-07-15 | SVR261 | - | Jul 15, 08:00 UTC | Jul 15, 09:20 UTC | 1h 20m |
| 2026-07-14 | SVR105 | - | Jul 14, 18:10 UTC | Jul 15, 05:10 UTC | 10h 59m |
| 2026-07-14 | SVR105 | - | Jul 14, 06:10 UTC | Jul 15, 04:45 UTC | 22h 34m |
| 2026-07-13 | SVR105 | - | Jul 13, 21:25 UTC | Jul 14, 20:45 UTC | 23h 20m |
| 2026-07-13 | SVR627 | - | Jul 13, 10:35 UTC | Jul 13, 11:50 UTC | 1h 15m |
| 2026-07-11 | SVR1333 | - | Jul 11, 03:05 UTC | Jul 11, 05:45 UTC | 2h 40m |
| 2026-07-08 | SVR106 | - | Jul 8, 04:55 UTC | Jul 8, 05:35 UTC | 40m |
| 2026-07-07 | SVR106 | - | Jul 7, 10:15 UTC | Jul 8, 05:35 UTC | 19h 20m |
| 2026-07-05 | RA73803 | - | Jul 5, 10:35 UTC | Jul 5, 11:05 UTC | 30m |
| 2026-07-04 | SVR627 | - | Jul 4, 16:00 UTC | Jul 4, 16:40 UTC | 40m |
| 2026-07-04 | SVR274 | - | Jul 4, 12:40 UTC | Jul 4, 12:55 UTC | 15m |
| 2026-07-03 | SVR173 | - | Jul 3, 16:00 UTC | Jul 3, 16:15 UTC | 15m |
| 2026-07-03 | SVR2642 | - | Jul 3, 07:25 UTC | Jul 3, 07:35 UTC | 10m |
| 2026-07-03 | SVR2642 | - | Jul 3, 05:45 UTC | Jul 3, 05:55 UTC | 10m |
| 2026-07-01 | SVR2641 | LED → LBD | Jul 1, 17:10 UTC | Jul 1, 17:30 UTC | 20m |
| 2026-06-30 | SVR174 | - | Jun 30, 14:55 UTC | Jun 30, 15:10 UTC | 15m |
| 2026-06-27 | SVR1334 | - | Jun 27, 10:19 UTC | Jun 27, 10:34 UTC | 15m |
| 2026-06-25 | SVR156 | - | Jun 25, 15:54 UTC | Jun 26, 09:45 UTC | 17h 50m |
| 2026-06-25 | SVR2879 | - | Jun 25, 14:09 UTC | Jun 26, 09:45 UTC | 19h 35m |
| 2026-06-25 | SVR392 | - | Jun 25, 10:25 UTC | Jun 25, 11:35 UTC | 1h 10m |
| 2026-06-25 | SVR391 | - | Jun 25, 07:49 UTC | Jun 25, 08:40 UTC | 50m |
| 2026-06-23 | SVR209 | - | Jun 23, 12:35 UTC | Jun 23, 23:34 UTC | 11h 0m |
| 2026-06-21 | RA73803 | - | Jun 21, 09:29 UTC | Jun 21, 13:04 UTC | 3h 35m |
| 2026-06-19 | SVR624 | - | Jun 19, 00:45 UTC | Jun 19, 15:44 UTC | 15h 0m |
| 2026-06-18 | SVR624 | - | Jun 18, 09:25 UTC | Jun 19, 07:25 UTC | 21h 59m |
| 2026-06-16 | SVR1338 | KEJ → AER | Jun 16, 04:05 UTC | Jun 16, 10:00 UTC | 5h 55m |
| 2026-06-16 | SVR1337 | AER → KEJ | Jun 16, 02:04 UTC | Jun 16, 02:40 UTC | 35m |
| 2026-06-13 | SVR2990 | DYU → KZN | Jun 13, 10:35 UTC | Jun 13, 10:50 UTC | 15m |
| 2026-06-11 | SVR9138 | - | Jun 11, 17:25 UTC | Jun 12, 02:30 UTC | 9h 6m |
| 2026-06-11 | SVR9138 | - | Jun 11, 05:35 UTC | Jun 12, 02:30 UTC | 20h 55m |
| 2026-06-10 | SVR9138 | - | Jun 10, 23:30 UTC | Jun 11, 20:40 UTC | 21h 10m |
| 2026-06-10 | SVR174 | KHV → SVX | Jun 10, 16:00 UTC | Jun 10, 16:10 UTC | 10m |
| 2026-06-09 | RA73803 | - | Jun 9, 17:15 UTC | Jun 10, 10:10 UTC | 16h 55m |
| 2026-06-09 | RA73803 | - | Jun 9, 13:40 UTC | Jun 10, 10:10 UTC | 20h 30m |
| 2026-06-09 | RA73803 | - | Jun 9, 10:50 UTC | Jun 10, 10:10 UTC | 23h 20m |
| 2026-06-09 | RA73803 | - | Jun 9, 10:20 UTC | Jun 10, 02:20 UTC | 16h 0m |
| 2026-06-08 | RA73803 | - | Jun 8, 19:55 UTC | Jun 9, 17:55 UTC | 22h 0m |
| 2026-06-08 | SVR9169 | - | Jun 8, 17:50 UTC | Jun 9, 14:00 UTC | 20h 10m |
| 2026-06-08 | SVR9169 | - | Jun 8, 03:50 UTC | Jun 8, 20:35 UTC | 16h 45m |
| 2026-06-06 | SVR150 | GDZ → SVX | Jun 6, 08:00 UTC | Jun 6, 08:45 UTC | 45m |
| 2026-06-05 | SVR150 | GDZ → SVX | Jun 5, 09:45 UTC | Jun 6, 08:45 UTC | 23h 0m |
| 2026-06-04 | SVR265 | DME → SVX | Jun 4, 16:45 UTC | Jun 5, 10:00 UTC | 17h 15m |
| 2026-06-04 | SVR220 | AER → SVX | Jun 4, 10:50 UTC | Jun 4, 11:25 UTC | 35m |
| 2026-06-04 | SVR219 | SVX → AER | Jun 4, 07:30 UTC | Jun 4, 08:35 UTC | 1h 5m |
| 2026-06-02 | SVR624 | SVX → HTA | Jun 2, 18:10 UTC | Jun 2, 18:25 UTC | 15m |
| 2026-06-02 | SVR624 | SVX → HTA | Jun 2, 16:40 UTC | Jun 2, 17:00 UTC | 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-73803 page for operator, model, and routing details .