sensors Mode-S transponder
152045
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73797 · AIRBUS A-321
- Hex
- 152045
- Octal
- 05220105
- Decimal
- 1,384,517
- Country
- RU
- Tail
- RA-73797
- Type
- A321
- Flights observed
- 80
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- 3d ago
Last known position
Country allocation
The ICAO 24-bit address 152045 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 |
|---|---|---|---|
| SVR2428 | Ural Airlines | 21 | 2026-05-04 |
| SVR372 | - | 6 | 2026-06-28 |
| SVR371 | - | 5 | 2026-06-25 |
| SVR168 | Ural Airlines | 5 | 2026-06-09 |
| SVR651 | - | 3 | 2026-07-04 |
| SVR2426 | Ural Airlines | 3 | 2026-04-21 |
| SVR2425 | Ural Airlines | 3 | 2026-04-20 |
| SVR167 | Ural Airlines | 3 | 2026-06-10 |
| SVR652 | Ural Airlines | 2 | 2026-06-07 |
| SVR628 | - | 2 | 2026-06-27 |
| SVR627 | - | 2 | 2026-06-27 |
| SVR404 | Ural Airlines | 2 | 2026-06-08 |
| SVR2448 | Ural Airlines | 2 | 2026-04-26 |
| SVR2441 | Ural Airlines | 2 | 2026-04-19 |
| SVR154 | - | 2 | 2026-07-11 |
| SVR1387 | Ural Airlines | 2 | 2026-06-23 |
| SVR1343 | Ural Airlines | 2 | 2026-06-09 |
| SVR073 | Ural Airlines | 2 | 2026-05-11 |
| SVR9656 | Ural Airlines | 1 | 2026-05-07 |
| SVR8254 | Ural Airlines | 1 | 2026-06-04 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-11 | SVR154 | - | Jul 11, 14:30 UTC | Jul 11, 14:40 UTC | 10m |
| 2026-07-04 | SVR651 | - | Jul 4, 19:35 UTC | Jul 4, 19:55 UTC | 20m |
| 2026-06-28 | SVR372 | - | Jun 28, 12:29 UTC | Jun 28, 18:05 UTC | 5h 35m |
| 2026-06-27 | SVR628 | - | Jun 27, 15:55 UTC | Jun 28, 10:15 UTC | 18h 20m |
| 2026-06-27 | SVR627 | - | Jun 27, 13:04 UTC | Jun 27, 13:55 UTC | 50m |
| 2026-06-26 | SVR372 | - | Jun 26, 11:05 UTC | Jun 26, 12:19 UTC | 1h 15m |
| 2026-06-25 | SVR371 | - | Jun 25, 20:14 UTC | Jun 26, 09:10 UTC | 12h 55m |
| 2026-06-23 | SVR1387 | DME → OGZ | Jun 23, 21:45 UTC | Jun 24, 11:54 UTC | 14h 10m |
| 2026-06-23 | SVR1387 | DME → OGZ | Jun 23, 14:44 UTC | Jun 24, 11:54 UTC | 21h 10m |
| 2026-06-21 | SVR2879 | LED → DYU | Jun 21, 17:29 UTC | Jun 21, 18:00 UTC | 30m |
| 2026-06-17 | SVR271 | - | Jun 17, 21:30 UTC | Jun 18, 18:50 UTC | 21h 20m |
| 2026-06-10 | SVR209 | SVX → KRR | Jun 10, 19:35 UTC | Jun 11, 13:15 UTC | 17h 40m |
| 2026-06-10 | SVR167 | DME → KGD | Jun 10, 15:05 UTC | Jun 10, 17:30 UTC | 2h 25m |
| 2026-06-10 | SVR372 | KGD → DME | Jun 10, 10:45 UTC | Jun 10, 12:45 UTC | 2h 0m |
| 2026-06-10 | SVR371 | DME → KGD | Jun 10, 07:55 UTC | Jun 10, 08:55 UTC | 1h 0m |
| 2026-06-10 | SVR1344 | MCX → DME | Jun 10, 02:35 UTC | Jun 10, 03:05 UTC | 30m |
| 2026-06-09 | SVR1343 | DME → MCX | Jun 9, 10:05 UTC | Jun 9, 10:20 UTC | 15m |
| 2026-06-09 | SVR168 | KGD → DME | Jun 9, 07:50 UTC | Jun 9, 08:00 UTC | 10m |
| 2026-06-08 | SVR404 | KGD → SVX | Jun 8, 19:55 UTC | Jun 9, 07:10 UTC | 11h 15m |
| 2026-06-08 | SVR404 | KGD → SVX | Jun 8, 03:25 UTC | Jun 8, 22:25 UTC | 19h 0m |
| 2026-06-07 | SVR652 | BAX → DME | Jun 7, 21:00 UTC | Jun 8, 03:55 UTC | 6h 55m |
| 2026-06-05 | SVR651 | DME → BAX | Jun 5, 06:00 UTC | Jun 5, 20:55 UTC | 14h 55m |
| 2026-06-04 | SVR8254 | DYU → DME | Jun 4, 09:25 UTC | Jun 4, 09:55 UTC | 30m |
| 2026-06-02 | SVR168 | KGD → DME | Jun 2, 18:05 UTC | Jun 3, 09:40 UTC | 15h 35m |
| 2026-06-02 | SVR372 | KGD → DME | Jun 2, 10:20 UTC | Jun 2, 16:15 UTC | 5h 55m |
| 2026-06-01 | SVR371 | DME → KGD | Jun 1, 20:35 UTC | Jun 2, 08:35 UTC | 12h 0m |
| 2026-05-31 | SVR651 | DME → BAX | May 31, 19:45 UTC | May 31, 21:00 UTC | 1h 15m |
| 2026-05-30 | SVR387 | DME → OMS | May 30, 21:00 UTC | May 30, 22:20 UTC | 1h 20m |
| 2026-05-26 | SVR168 | KGD → DME | May 26, 18:05 UTC | May 26, 19:45 UTC | 1h 40m |
| 2026-05-26 | SVR372 | KGD → DME | May 26, 10:25 UTC | May 26, 16:15 UTC | 5h 50m |
| 2026-05-26 | SVR371 | DME → KGD | May 26, 06:29 UTC | May 26, 08:34 UTC | 2h 5m |
| 2026-05-25 | SVR652 | BAX → DME | May 25, 21:09 UTC | May 26, 04:00 UTC | 6h 50m |
| 2026-05-24 | SVR2969 | DME → TJU | May 24, 20:55 UTC | May 24, 21:15 UTC | 20m |
| 2026-05-23 | SVR628 | KGD → DME | May 23, 14:00 UTC | May 23, 14:55 UTC | 55m |
| 2026-05-23 | SVR627 | DME → KGD | May 23, 11:15 UTC | May 23, 11:55 UTC | 40m |
| 2026-05-20 | SVR1388 | OGZ → DME | May 20, 13:45 UTC | May 20, 14:05 UTC | 20m |
| 2026-05-17 | SVR154 | MRV → DME | May 17, 13:05 UTC | May 17, 13:20 UTC | 15m |
| 2026-05-16 | SVR168 | KGD → DME | May 16, 17:55 UTC | May 17, 13:20 UTC | 19h 25m |
| 2026-05-16 | SVR167 | DME → KGD | May 16, 15:25 UTC | May 16, 16:25 UTC | 1h 0m |
| 2026-05-16 | SVR372 | KGD → DME | May 16, 10:20 UTC | May 16, 11:46 UTC | 1h 25m |
| 2026-05-15 | SVR371 | DME → KGD | May 15, 18:10 UTC | May 16, 08:31 UTC | 14h 21m |
| 2026-05-13 | SVR168 | KGD → DME | May 13, 19:45 UTC | May 13, 21:10 UTC | 1h 25m |
| 2026-05-13 | SVR167 | DME → KGD | May 13, 01:50 UTC | May 13, 18:25 UTC | 16h 35m |
| 2026-05-12 | SVR1343 | DME → MCX | May 12, 10:15 UTC | May 13, 01:50 UTC | 15h 35m |
| 2026-05-11 | SVR073 | DME → KGD | May 11, 05:30 UTC | May 11, 06:30 UTC | 1h 0m |
| 2026-05-10 | SVR074 | KGD → DME | May 10, 08:15 UTC | May 10, 16:30 UTC | 8h 15m |
| 2026-05-09 | SVR073 | DME → KGD | May 9, 15:55 UTC | May 10, 06:50 UTC | 14h 55m |
| 2026-05-07 | SVR9656 | HTA → DME | May 7, 20:20 UTC | May 8, 03:44 UTC | 7h 25m |
| 2026-05-04 | SVR2428 | DYU → ZIA | May 4, 18:30 UTC | May 4, 19:10 UTC | 41m |
| 2026-05-03 | SVR2428 | DYU → ZIA | May 3, 19:20 UTC | May 4, 19:10 UTC | 23h 51m |
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-73797 page for operator, model, and routing details .