sensors Mode-S transponder
152042
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73794 · AIRBUS A-321
- Hex
- 152042
- Octal
- 05220102
- Decimal
- 1,384,514
- Country
- RU
- Tail
- RA-73794
- Type
- A321
- Flights observed
- 38
- Distinct callsigns
- 19
- Country
- RU
- Last broadcast
- 22h ago
Last known position
Country allocation
The ICAO 24-bit address 152042 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 19 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| SVR371 | Ural Airlines | 6 | 2026-06-07 |
| SVR2427 | Ural Airlines | 5 | 2026-05-26 |
| SVR372 | Ural Airlines | 4 | 2026-06-08 |
| SVR651 | Ural Airlines | 3 | 2026-06-08 |
| SVR181 | Ural Airlines | 3 | 2026-06-01 |
| SVR8254 | Ural Airlines | 2 | 2026-04-30 |
| SVR365 | Ural Airlines | 2 | 2026-06-02 |
| SVR263 | Ural Airlines | 2 | 2026-05-30 |
| SVR628 | Ural Airlines | 1 | 2026-05-04 |
| SVR627 | Ural Airlines | 1 | 2026-05-04 |
| SVR388 | Ural Airlines | 1 | 2026-05-02 |
| SVR2969 | Ural Airlines | 1 | 2026-04-26 |
| SVR270 | Ural Airlines | 1 | 2026-06-03 |
| SVR2428 | Ural Airlines | 1 | 2026-05-27 |
| SVR2426 | Ural Airlines | 1 | 2026-05-21 |
| SVR168 | Ural Airlines | 1 | 2026-05-11 |
| SVR167 | Ural Airlines | 1 | 2026-05-11 |
| SVR154 | Ural Airlines | 1 | 2026-05-02 |
| SVR153 | Ural Airlines | 1 | 2026-06-04 |
Recent flights last 38
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-08 | SVR372 | KGD → DME | Jun 8, 20:50 UTC | Jun 9, 13:10 UTC | 16h 20m |
| 2026-06-08 | SVR651 | DME → BAX | Jun 8, 02:35 UTC | Jun 8, 21:05 UTC | 18h 30m |
| 2026-06-07 | SVR372 | KGD → DME | Jun 7, 10:30 UTC | Jun 8, 02:35 UTC | 16h 5m |
| 2026-06-07 | SVR371 | DME → KGD | Jun 7, 08:15 UTC | Jun 7, 08:45 UTC | 30m |
| 2026-06-06 | SVR371 | DME → KGD | Jun 6, 10:45 UTC | Jun 6, 11:55 UTC | 1h 10m |
| 2026-06-04 | SVR153 | DME → MRV | Jun 4, 20:55 UTC | Jun 5, 10:20 UTC | 13h 25m |
| 2026-06-03 | SVR270 | SVX → DME | Jun 3, 16:00 UTC | Jun 3, 16:50 UTC | 50m |
| 2026-06-02 | SVR365 | SVX → IKT | Jun 2, 17:15 UTC | Jun 3, 16:30 UTC | 23h 15m |
| 2026-06-02 | SVR365 | SVX → IKT | Jun 2, 11:30 UTC | Jun 2, 17:55 UTC | 6h 25m |
| 2026-06-01 | SVR181 | LED → AER | Jun 1, 06:35 UTC | Jun 1, 19:05 UTC | 12h 30m |
| 2026-05-31 | SVR181 | LED → AER | May 31, 23:45 UTC | Jun 1, 19:05 UTC | 19h 20m |
| 2026-05-31 | SVR181 | LED → AER | May 31, 15:55 UTC | Jun 1, 07:00 UTC | 15h 5m |
| 2026-05-30 | SVR263 | DME → SVX | May 30, 18:50 UTC | May 31, 16:15 UTC | 21h 25m |
| 2026-05-30 | SVR263 | DME → SVX | May 30, 18:20 UTC | May 31, 16:15 UTC | 21h 55m |
| 2026-05-27 | SVR2428 | DYU → ZIA | May 27, 11:15 UTC | May 27, 19:40 UTC | 8h 25m |
| 2026-05-26 | SVR2427 | ZIA → DYU | May 26, 11:30 UTC | May 26, 11:50 UTC | 20m |
| 2026-05-21 | SVR2426 | LBD → ZIA | May 21, 07:50 UTC | May 21, 12:00 UTC | 4h 10m |
| 2026-05-19 | SVR2427 | ZIA → DYU | May 19, 11:00 UTC | May 19, 23:00 UTC | 12h 0m |
| 2026-05-17 | SVR2427 | ZIA → DYU | May 17, 11:10 UTC | May 18, 00:00 UTC | 12h 50m |
| 2026-05-14 | SVR2427 | ZIA → DYU | May 14, 10:40 UTC | May 14, 23:20 UTC | 12h 40m |
| 2026-05-13 | SVR2427 | ZIA → DYU | May 13, 11:15 UTC | May 13, 11:35 UTC | 20m |
| 2026-05-11 | SVR168 | KGD → DME | May 11, 18:05 UTC | May 11, 20:00 UTC | 1h 55m |
| 2026-05-11 | SVR167 | DME → KGD | May 11, 15:35 UTC | May 11, 16:25 UTC | 50m |
| 2026-05-11 | SVR371 | DME → KGD | May 11, 08:00 UTC | May 11, 08:40 UTC | 40m |
| 2026-05-10 | SVR371 | DME → KGD | May 10, 12:00 UTC | May 11, 08:40 UTC | 20h 40m |
| 2026-05-10 | SVR371 | DME → KGD | May 10, 09:35 UTC | May 11, 08:30 UTC | 22h 55m |
| 2026-05-08 | SVR372 | KGD → DME | May 8, 10:29 UTC | May 8, 12:00 UTC | 1h 30m |
| 2026-05-05 | SVR651 | DME → BAX | May 5, 20:20 UTC | May 5, 20:55 UTC | 35m |
| 2026-05-04 | SVR628 | KGD → DME | May 4, 12:45 UTC | May 4, 14:10 UTC | 1h 25m |
| 2026-05-04 | SVR627 | DME → KGD | May 4, 10:20 UTC | May 4, 11:10 UTC | 50m |
| 2026-05-02 | SVR154 | MRV → DME | May 2, 12:05 UTC | May 2, 12:15 UTC | 10m |
| 2026-05-02 | SVR388 | OMS → DME | May 2, 02:45 UTC | May 2, 03:20 UTC | 35m |
| 2026-04-30 | SVR651 | DME → BAX | Apr 30, 20:40 UTC | Apr 30, 21:05 UTC | 25m |
| 2026-04-30 | SVR8254 | DYU → DME | Apr 30, 05:45 UTC | Apr 30, 11:50 UTC | 6h 5m |
| 2026-04-29 | SVR8254 | DYU → DME | Apr 29, 15:45 UTC | Apr 30, 11:50 UTC | 20h 5m |
| 2026-04-28 | SVR372 | KGD → DME | Apr 28, 10:20 UTC | Apr 28, 16:55 UTC | 6h 35m |
| 2026-04-28 | SVR371 | DME → KGD | Apr 28, 08:10 UTC | Apr 28, 08:45 UTC | 35m |
| 2026-04-26 | SVR2969 | DME → TJU | Apr 26, 04:05 UTC | Apr 26, 04:15 UTC | 10m |
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-73794 page for operator, model, and routing details .