sensors Mode-S transponder
152040
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73792 · AIRBUS A-321
- Hex
- 152040
- Octal
- 05220100
- Decimal
- 1,384,512
- Country
- RU
- Tail
- RA-73792
- Type
- A321
- Flights observed
- 39
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- 18h ago
Last known position
Country allocation
The ICAO 24-bit address 152040 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 |
|---|---|---|---|
| SVR1387 | Ural Airlines | 4 | 2026-05-28 |
| SVR372 | Ural Airlines | 3 | 2026-05-13 |
| SVR371 | Ural Airlines | 3 | 2026-05-21 |
| SVR2909 | Ural Airlines | 3 | 2026-04-18 |
| SVR168 | Ural Airlines | 3 | 2026-05-12 |
| SVR153 | Ural Airlines | 3 | 2026-05-10 |
| SVR651 | Ural Airlines | 2 | 2026-05-23 |
| SVR2969 | Ural Airlines | 2 | 2026-05-28 |
| SVR279 | Ural Airlines | 2 | 2026-05-09 |
| SVR2426 | Ural Airlines | 2 | 2026-06-02 |
| SVR154 | Ural Airlines | 2 | 2026-05-11 |
| SVR652 | Ural Airlines | 1 | 2026-05-24 |
| SVR628 | Ural Airlines | 1 | 2026-05-18 |
| SVR427 | Ural Airlines | 1 | 2026-05-15 |
| SVR387 | Ural Airlines | 1 | 2026-05-09 |
| SVR2910 | Ural Airlines | 1 | 2026-04-19 |
| SVR280 | Ural Airlines | 1 | 2026-05-27 |
| SVR271 | Ural Airlines | 1 | 2026-04-30 |
| SVR2428 | Ural Airlines | 1 | 2026-05-30 |
| SVR2427 | Ural Airlines | 1 | 2026-05-29 |
Recent flights last 39
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-02 | SVR2426 | LBD → ZIA | Jun 2, 07:05 UTC | Jun 2, 07:35 UTC | 30m |
| 2026-06-01 | SVR2426 | LBD → ZIA | Jun 1, 05:35 UTC | Jun 1, 06:05 UTC | 30m |
| 2026-05-30 | SVR2428 | DYU → ZIA | May 30, 19:05 UTC | May 30, 19:40 UTC | 35m |
| 2026-05-29 | SVR2427 | ZIA → DYU | May 29, 10:40 UTC | May 29, 11:45 UTC | 1h 5m |
| 2026-05-28 | SVR2969 | DME → TJU | May 28, 20:25 UTC | May 28, 20:50 UTC | 25m |
| 2026-05-28 | SVR1387 | DME → OGZ | May 28, 07:35 UTC | May 28, 07:50 UTC | 15m |
| 2026-05-27 | SVR280 | AER → DME | May 27, 14:45 UTC | May 27, 22:00 UTC | 7h 15m |
| 2026-05-25 | SVR2969 | DME → TJU | May 25, 20:09 UTC | May 25, 20:30 UTC | 20m |
| 2026-05-24 | SVR652 | BAX → DME | May 24, 02:40 UTC | May 24, 02:50 UTC | 10m |
| 2026-05-23 | SVR651 | DME → BAX | May 23, 19:25 UTC | May 23, 19:50 UTC | 25m |
| 2026-05-21 | SVR371 | DME → KGD | May 21, 07:50 UTC | May 21, 08:30 UTC | 40m |
| 2026-05-18 | SVR628 | KGD → DME | May 18, 12:35 UTC | May 18, 15:05 UTC | 2h 30m |
| 2026-05-15 | SVR427 | DME → GRV | May 15, 08:40 UTC | May 15, 09:00 UTC | 20m |
| 2026-05-13 | SVR372 | KGD → DME | May 13, 17:10 UTC | May 14, 06:40 UTC | 13h 30m |
| 2026-05-13 | SVR371 | DME → KGD | May 13, 15:00 UTC | May 13, 15:30 UTC | 30m |
| 2026-05-12 | SVR168 | KGD → DME | May 12, 18:05 UTC | May 13, 15:30 UTC | 21h 25m |
| 2026-05-12 | SVR168 | KGD → DME | May 12, 17:35 UTC | May 13, 15:30 UTC | 21h 55m |
| 2026-05-12 | SVR372 | KGD → DME | May 12, 10:20 UTC | May 12, 12:25 UTC | 2h 5m |
| 2026-05-11 | SVR154 | MRV → DME | May 11, 12:05 UTC | May 11, 12:15 UTC | 10m |
| 2026-05-10 | SVR153 | DME → MRV | May 10, 07:55 UTC | May 10, 08:15 UTC | 20m |
| 2026-05-09 | SVR387 | DME → OMS | May 9, 21:14 UTC | May 9, 21:45 UTC | 30m |
| 2026-05-09 | SVR279 | DME → AER | May 9, 11:20 UTC | May 9, 11:40 UTC | 20m |
| 2026-05-04 | SVR168 | KGD → DME | May 4, 17:55 UTC | May 4, 19:20 UTC | 1h 26m |
| 2026-05-04 | SVR167 | DME → KGD | May 4, 15:45 UTC | May 4, 16:25 UTC | 40m |
| 2026-05-03 | SVR372 | KGD → DME | May 3, 10:55 UTC | May 3, 12:55 UTC | 2h 0m |
| 2026-05-03 | SVR371 | DME → KGD | May 3, 08:50 UTC | May 3, 09:25 UTC | 35m |
| 2026-04-30 | SVR271 | DME → SVX | Apr 30, 21:15 UTC | Apr 30, 21:45 UTC | 30m |
| 2026-04-30 | SVR154 | MRV → DME | Apr 30, 12:10 UTC | Apr 30, 12:25 UTC | 15m |
| 2026-04-30 | SVR153 | DME → MRV | Apr 30, 08:05 UTC | Apr 30, 08:20 UTC | 15m |
| 2026-04-29 | SVR651 | DME → BAX | Apr 29, 19:45 UTC | Apr 29, 20:05 UTC | 20m |
| 2026-04-29 | SVR153 | DME → MRV | Apr 29, 08:10 UTC | Apr 29, 08:20 UTC | 10m |
| 2026-04-28 | SVR279 | DME → AER | Apr 28, 13:30 UTC | Apr 28, 13:55 UTC | 25m |
| 2026-04-19 | SVR2910 | OSS → DME | Apr 19, 01:10 UTC | Apr 19, 01:45 UTC | 35m |
| 2026-04-18 | SVR2909 | DME → OSS | Apr 18, 17:00 UTC | Apr 18, 17:35 UTC | 35m |
| 2026-04-16 | SVR1387 | DME → OGZ | Apr 16, 07:34 UTC | Apr 16, 08:00 UTC | 25m |
| 2026-04-15 | SVR1387 | DME → OGZ | Apr 15, 08:35 UTC | Apr 15, 08:45 UTC | 10m |
| 2026-04-15 | SVR1387 | DME → OGZ | Apr 15, 07:35 UTC | Apr 15, 07:55 UTC | 20m |
| 2026-04-14 | SVR2909 | - | Apr 14, 17:45 UTC | Apr 14, 17:55 UTC | 10m |
| 2026-04-14 | SVR2909 | - | Apr 14, 16:50 UTC | Apr 14, 17:05 UTC | 15m |
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-73792 page for operator, model, and routing details .