sensors Mode-S transponder
152076
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73846 · AIRBUS A-321
- Hex
- 152076
- Octal
- 05220166
- Decimal
- 1,384,566
- Country
- RU
- Tail
- RA-73846
- Type
- A321
- Flights observed
- 121
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- 8h ago
Last known position
Country allocation
The ICAO 24-bit address 152076 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 |
|---|---|---|---|
| SVR2461 | - | 14 | 2026-07-13 |
| SVR2617 | - | 13 | 2026-07-09 |
| SVR2168 | - | 13 | 2026-07-10 |
| SVR2618 | - | 9 | 2026-07-12 |
| SVR2462 | - | 7 | 2026-07-10 |
| SVR2448 | - | 6 | 2026-07-01 |
| SVR2634 | Ural Airlines | 5 | 2026-05-13 |
| SVR2132 | - | 5 | 2026-07-01 |
| SVR8446 | Ural Airlines | 3 | 2026-05-23 |
| SVR8445 | Ural Airlines | 3 | 2026-06-03 |
| SVR2909 | - | 3 | 2026-07-05 |
| SVR2460 | - | 3 | 2026-07-04 |
| SVR2167 | Ural Airlines | 3 | 2026-06-09 |
| SVR2131 | Ural Airlines | 3 | 2026-06-14 |
| SVR2910 | Ural Airlines | 2 | 2026-06-19 |
| SVR2710 | - | 2 | 2026-06-26 |
| SVR2633 | Ural Airlines | 2 | 2026-05-09 |
| SVR2459 | Ural Airlines | 2 | 2026-06-27 |
| SVR1562 | Ural Airlines | 2 | 2026-06-24 |
| UZTT | - | 1 | 2026-06-12 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | SVR2461 | - | Jul 13, 17:35 UTC | Jul 14, 04:10 UTC | 10h 35m |
| 2026-07-12 | SVR2618 | - | Jul 12, 14:35 UTC | Jul 12, 18:55 UTC | 4h 20m |
| 2026-07-10 | SVR2462 | - | Jul 10, 17:00 UTC | Jul 11, 06:30 UTC | 13h 30m |
| 2026-07-10 | SVR2461 | - | Jul 10, 16:05 UTC | Jul 10, 16:20 UTC | 15m |
| 2026-07-10 | SVR2168 | - | Jul 10, 13:00 UTC | Jul 10, 13:25 UTC | 25m |
| 2026-07-09 | SVR2168 | - | Jul 9, 17:10 UTC | Jul 10, 13:25 UTC | 20h 15m |
| 2026-07-09 | SVR2617 | - | Jul 9, 06:20 UTC | Jul 9, 17:15 UTC | 10h 55m |
| 2026-07-08 | SVR2461 | - | Jul 8, 17:00 UTC | Jul 9, 06:35 UTC | 13h 35m |
| 2026-07-06 | SVR2611 | - | Jul 6, 06:45 UTC | Jul 6, 18:10 UTC | 11h 25m |
| 2026-07-05 | SVR2909 | - | Jul 5, 13:40 UTC | Jul 6, 06:55 UTC | 17h 15m |
| 2026-07-05 | SVR2909 | - | Jul 5, 07:10 UTC | Jul 5, 18:20 UTC | 11h 10m |
| 2026-07-04 | SVR2128 | - | Jul 4, 17:00 UTC | Jul 5, 14:00 UTC | 21h 0m |
| 2026-07-04 | SVR2460 | - | Jul 4, 14:50 UTC | Jul 4, 15:00 UTC | 10m |
| 2026-07-03 | SVR2168 | - | Jul 3, 14:10 UTC | Jul 4, 06:50 UTC | 16h 40m |
| 2026-07-03 | SVR2168 | - | Jul 3, 07:00 UTC | Jul 3, 14:40 UTC | 7h 40m |
| 2026-07-02 | SVR2618 | - | Jul 2, 15:10 UTC | Jul 2, 15:40 UTC | 30m |
| 2026-07-02 | SVR2617 | - | Jul 2, 08:20 UTC | Jul 2, 08:35 UTC | 15m |
| 2026-07-02 | SVR2462 | - | Jul 2, 05:00 UTC | Jul 2, 05:10 UTC | 10m |
| 2026-07-02 | SVR2462 | - | Jul 2, 03:40 UTC | Jul 2, 04:00 UTC | 20m |
| 2026-07-01 | SVR2461 | - | Jul 1, 19:35 UTC | Jul 1, 20:05 UTC | 30m |
| 2026-07-01 | SVR2132 | - | Jul 1, 16:15 UTC | Jul 1, 16:40 UTC | 25m |
| 2026-07-01 | SVR2448 | - | Jul 1, 06:55 UTC | Jul 1, 07:05 UTC | 10m |
| 2026-06-30 | SVR2804 | FRU → DME | Jun 30, 11:20 UTC | Jun 30, 19:00 UTC | 7h 40m |
| 2026-06-27 | SVR2617 | - | Jun 27, 16:14 UTC | Jun 28, 06:15 UTC | 14h 0m |
| 2026-06-27 | SVR2459 | ZIA → NMA | Jun 27, 05:10 UTC | Jun 27, 16:20 UTC | 11h 10m |
| 2026-06-26 | SVR2909 | DME → OSS | Jun 26, 17:44 UTC | Jun 27, 16:20 UTC | 22h 35m |
| 2026-06-26 | SVR2710 | - | Jun 26, 09:55 UTC | Jun 27, 05:15 UTC | 19h 20m |
| 2026-06-25 | SVR2710 | - | Jun 25, 14:29 UTC | Jun 26, 10:35 UTC | 20h 5m |
| 2026-06-25 | SVR3556 | - | Jun 25, 01:19 UTC | Jun 25, 14:34 UTC | 13h 15m |
| 2026-06-24 | SVR1562 | AYT → MRV | Jun 24, 17:45 UTC | Jun 24, 23:40 UTC | 5h 55m |
| 2026-06-24 | SVR1562 | AYT → MRV | Jun 24, 10:10 UTC | Jun 24, 16:05 UTC | 5h 55m |
| 2026-06-24 | SVR1524 | AYT → OGZ | Jun 24, 02:00 UTC | Jun 24, 07:59 UTC | 6h 0m |
| 2026-06-23 | SVR3506 | - | Jun 23, 18:55 UTC | Jun 23, 20:19 UTC | 1h 25m |
| 2026-06-23 | SVR1897 | MCX → AYT | Jun 23, 16:50 UTC | Jun 23, 17:15 UTC | 25m |
| 2026-06-23 | SVR1898 | AYT → MCX | Jun 23, 10:44 UTC | Jun 23, 12:29 UTC | 1h 45m |
| 2026-06-23 | SVR3559 | DME → AYT | Jun 23, 07:40 UTC | Jun 23, 08:54 UTC | 1h 15m |
| 2026-06-19 | SVR2910 | OSS → DME | Jun 19, 09:30 UTC | Jun 19, 17:34 UTC | 8h 5m |
| 2026-06-18 | SVR2910 | OSS → DME | Jun 18, 13:15 UTC | Jun 19, 09:49 UTC | 20h 34m |
| 2026-06-16 | SVR2803 | - | Jun 16, 12:45 UTC | Jun 16, 13:00 UTC | 15m |
| 2026-06-15 | SVR167 | DME → KGD | Jun 15, 23:45 UTC | Jun 16, 00:35 UTC | 50m |
| 2026-06-15 | SVR2132 | SKD → ZIA | Jun 15, 17:20 UTC | Jun 15, 17:34 UTC | 15m |
| 2026-06-14 | SVR2131 | ZIA → SKD | Jun 14, 21:40 UTC | Jun 15, 16:40 UTC | 19h 0m |
| 2026-06-13 | SVR2460 | NMA → ZIA | Jun 13, 05:00 UTC | Jun 13, 17:30 UTC | 12h 30m |
| 2026-06-12 | SVR2460 | NMA → ZIA | Jun 12, 16:50 UTC | Jun 13, 12:35 UTC | 19h 44m |
| 2026-06-12 | UZTT | - | Jun 12, 03:35 UTC | Jun 12, 04:30 UTC | 55m |
| 2026-06-11 | SVR2618 | UGC → ZIA | Jun 11, 06:45 UTC | Jun 11, 12:50 UTC | 6h 5m |
| 2026-06-11 | SVR2617 | ZIA → UGC | Jun 11, 05:50 UTC | Jun 11, 06:05 UTC | 15m |
| 2026-06-10 | SVR2131 | ZIA → SKD | Jun 10, 09:05 UTC | Jun 10, 10:00 UTC | 55m |
| 2026-06-10 | SVR2462 | TAS → ZIA | Jun 10, 06:45 UTC | Jun 10, 07:00 UTC | 15m |
| 2026-06-09 | SVR2167 | ZIA → FEG | Jun 9, 08:35 UTC | Jun 9, 22:05 UTC | 13h 30m |
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-73846 page for operator, model, and routing details .