sensors Mode-S transponder

15205E

ICAO 24-bit transponder address · allocated to Russia

Currently assigned to RA-73822 · AIRBUS A-320neo

Hex
15205E
Octal
05220136
Decimal
1,384,542
Country
RU
Tail
RA-73822
Type
A20N
No current signal · last broadcast 1h ago
Flights observed
44
Distinct callsigns
13
Country
RU
Last broadcast
1h ago

Last known position

Most recent position reported by Mode-S 15205E.

Country allocation

The ICAO 24-bit address 15205E 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 13 distinct

Callsign Airline Flights Last seen
SVR350 Ural Airlines 12 2026-05-23
SVR623 Ural Airlines 6 2026-05-24
SVR572 Ural Airlines 5 2026-05-30
SVR624 Ural Airlines 4 2026-05-10
SVR174 Ural Airlines 4 2026-05-24
SVR349 Ural Airlines 3 2026-05-28
SVR266 Ural Airlines 3 2026-05-30
SVR627 Ural Airlines 2 2026-06-02
SVR504 Ural Airlines 1 2026-06-02
SVR300 Ural Airlines 1 2026-05-06
SVR299 Ural Airlines 1 2026-05-07
SVR205 Ural Airlines 1 2026-04-24
SVR173 Ural Airlines 1 2026-04-22

Recent flights last 44

DateFlightRouteTakeoffLandingDuration
2026-06-02 SVR504 KGD → SVX Jun 2, 16:05 UTCJun 2, 18:40 UTC2h 35m
2026-06-02 SVR627 DME → KGD Jun 2, 09:05 UTCJun 2, 14:10 UTC5h 5m
2026-05-30 SVR266 SVX → DME May 30, 15:20 UTCMay 30, 22:25 UTC7h 5m
2026-05-30 SVR266 SVX → DME May 30, 14:15 UTCMay 30, 14:25 UTC10m
2026-05-30 SVR572 VVO → SVX May 30, 08:20 UTCMay 30, 08:40 UTC20m
2026-05-28 SVR349 DME → BQS May 28, 19:20 UTCMay 29, 08:20 UTC13h 0m
2026-05-24 SVR623 HTA → SVX May 24, 23:00 UTCMay 25, 09:30 UTC10h 30m
2026-05-24 SVR174 KHV → SVX May 24, 13:15 UTCMay 24, 14:05 UTC50m
2026-05-23 SVR350 BQS → DME May 23, 08:45 UTCMay 23, 09:25 UTC40m
2026-05-22 SVR350 BQS → DME May 22, 08:50 UTCMay 22, 09:30 UTC40m
2026-05-21 SVR627 DME → KGD May 21, 10:35 UTCMay 21, 11:10 UTC35m
2026-05-20 SVR350 BQS → DME May 20, 08:15 UTCMay 20, 08:35 UTC20m
2026-05-19 SVR350 BQS → DME May 19, 09:35 UTCMay 20, 08:35 UTC23h 1m
2026-05-18 SVR349 DME → BQS May 18, 19:30 UTCMay 19, 09:45 UTC14h 15m
2026-05-18 SVR349 DME → BQS May 18, 13:10 UTCMay 19, 09:45 UTC20h 34m
2026-05-15 SVR350 BQS → DME May 15, 19:40 UTCMay 16, 09:40 UTC14h 1m
2026-05-15 SVR350 BQS → DME May 15, 14:50 UTCMay 16, 09:40 UTC18h 51m
2026-05-12 SVR266 SVX → DME May 12, 14:40 UTCMay 13, 08:25 UTC17h 45m
2026-05-10 SVR624 SVX → HTA May 10, 22:25 UTCMay 11, 00:05 UTC1h 40m
2026-05-07 SVR299 DME → SVX May 7, 16:10 UTCMay 7, 16:35 UTC25m
2026-05-06 SVR300 SVX → DME May 6, 11:50 UTCMay 6, 12:20 UTC30m
2026-05-02 SVR350 BQS → DME May 2, 19:40 UTCMay 3, 09:30 UTC13h 49m
2026-05-02 SVR350 BQS → DME May 2, 09:35 UTCMay 3, 09:30 UTC23h 54m
2026-05-02 SVR350 BQS → DME May 2, 09:25 UTCMay 2, 20:00 UTC10h 35m
2026-05-01 SVR350 BQS → DME May 1, 19:40 UTCMay 2, 09:45 UTC14h 5m
2026-04-27 SVR623 HTA → SVX Apr 27, 17:30 UTCApr 28, 09:35 UTC16h 5m
2026-04-24 SVR205 SVX → MRV Apr 24, 10:20 UTCApr 24, 11:25 UTC1h 5m
2026-04-23 SVR174 KHV → SVX Apr 23, 12:45 UTCApr 23, 18:05 UTC5h 20m
2026-04-22 SVR173 SVX → KHV Apr 22, 16:40 UTCApr 22, 16:50 UTC10m
2026-04-21 SVR174 KHV → SVX Apr 21, 12:01 UTCApr 21, 23:40 UTC11h 40m
2026-04-21 SVR572 VVO → SVX Apr 21, 09:45 UTCApr 21, 09:55 UTC10m
2026-04-20 SVR350 BQS → DME Apr 20, 07:50 UTCApr 20, 08:15 UTC25m
2026-04-19 SVR350 BQS → DME Apr 19, 07:50 UTCApr 19, 09:05 UTC1h 15m
2026-04-18 SVR572 VVO → SVX Apr 18, 09:40 UTCApr 18, 09:55 UTC15m
2026-04-18 SVR572 VVO → SVX Apr 18, 07:55 UTCApr 18, 08:30 UTC35m
2026-04-16 SVR623 HTA → SVX Apr 16, 09:10 UTCApr 16, 09:39 UTC30m
2026-04-16 SVR623 HTA → SVX Apr 16, 08:15 UTCApr 16, 09:05 UTC50m
2026-04-16 SVR623 HTA → SVX Apr 16, 05:09 UTCApr 16, 05:20 UTC10m
2026-04-16 SVR623 HTA → SVX Apr 16, 04:40 UTCApr 16, 05:05 UTC25m
2026-04-15 SVR624 SVX → HTA Apr 15, 22:35 UTCApr 15, 23:00 UTC25m
2026-04-15 SVR624 SVX → HTA Apr 15, 18:15 UTCApr 15, 18:35 UTC20m
2026-04-13 SVR624 - Apr 13, 22:15 UTCApr 13, 22:45 UTC30m
2026-04-13 SVR174 - Apr 13, 12:20 UTCApr 13, 13:40 UTC1h 20m
2026-04-13 SVR572 - Apr 13, 10:20 UTCApr 13, 10:30 UTC10m

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-73822 page for operator, model, and routing details .

Mode-S 15205E frequently asked

What is Mode-S code 15205E?
15205E is an ICAO 24-bit transponder address. Allocated to Russia. Assigned to RA-73822.
Where is Mode-S 15205E registered?
Mode-S code 15205E is allocated to Russia (RU). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 15205E broadcasting right now?
No active broadcast right now. Last signal was 1h ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 15205E, octal 05220136, decimal 1,384,542.
What flights does 15205E operate?
Mode-S 15205E has broadcast 13 distinct callsigns, including SVR350, SVR623, SVR572, SVR624, SVR174.