sensors Mode-S transponder
152C97
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-76951 · ILYUSHIN Il-76/82
- Hex
- 152C97
- Octal
- 05226227
- Decimal
- 1,387,671
- Country
- RU
- Tail
- RA-76951
- Type
- IL76
- Flights observed
- 38
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- 2h ago
Last known position
Country allocation
The ICAO 24-bit address 152C97 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 |
|---|---|---|---|
| VDA716 | - | 5 | 2026-05-14 |
| VDA316 | - | 4 | 2026-05-01 |
| VDA616 | - | 3 | 2026-06-01 |
| VDA516 | - | 3 | 2026-05-11 |
| VDA7916 | Volga-Dnepr Airlines | 2 | 2026-05-29 |
| VDA4170 | - | 2 | 2026-04-30 |
| VDA4169 | Volga-Dnepr Airlines | 2 | 2026-04-29 |
| VDA208 | - | 2 | 2026-06-05 |
| VDA7917 | - | 1 | 2026-05-30 |
| VDA7915 | - | 1 | 2026-05-25 |
| VDA7159 | - | 1 | 2026-04-14 |
| VDA5159 | - | 1 | 2026-04-24 |
| VDA515 | - | 1 | 2026-05-10 |
| VDA4177 | - | 1 | 2026-05-09 |
| VDA4165 | - | 1 | 2026-04-21 |
| VDA4159 | - | 1 | 2026-04-14 |
| VDA4145 | Volga-Dnepr Airlines | 1 | 2026-05-23 |
| VDA4144 | Volga-Dnepr Airlines | 1 | 2026-05-22 |
| VDA3199 | - | 1 | 2026-04-22 |
| VDA3159 | - | 1 | 2026-04-30 |
Recent flights last 38
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-05 | VDA208 | SVO → SVO | Jun 5, 08:40 UTC | Jun 5, 08:50 UTC | 10m |
| 2026-06-04 | VDA208 | - | Jun 4, 11:50 UTC | Jun 4, 12:20 UTC | 30m |
| 2026-06-02 | VDA2079 | - | Jun 2, 14:15 UTC | Jun 2, 14:35 UTC | 20m |
| 2026-06-01 | VDA616 | - | Jun 1, 07:05 UTC | Jun 1, 07:40 UTC | 35m |
| 2026-05-30 | VDA7917 | - | May 30, 12:20 UTC | May 30, 15:40 UTC | 3h 20m |
| 2026-05-29 | VDA7916 | ATH → FCN | May 29, 03:15 UTC | May 29, 08:20 UTC | 5h 5m |
| 2026-05-27 | VDA7916 | ATH → FCN | May 27, 11:15 UTC | May 27, 11:50 UTC | 35m |
| 2026-05-25 | VDA7915 | - | May 25, 23:14 UTC | May 25, 23:45 UTC | 30m |
| 2026-05-24 | VDA616 | - | May 24, 11:55 UTC | May 24, 14:55 UTC | 3h 0m |
| 2026-05-24 | VDA616 | - | May 24, 07:25 UTC | May 24, 08:00 UTC | 35m |
| 2026-05-23 | VDA4145 | SVO → LEJ | May 23, 06:35 UTC | May 23, 06:50 UTC | 15m |
| 2026-05-22 | VDA4144 | KZN → SVO | May 22, 02:10 UTC | May 22, 08:35 UTC | 6h 25m |
| 2026-05-19 | VDA108 | - | May 19, 19:25 UTC | May 20, 01:40 UTC | 6h 15m |
| 2026-05-18 | VDA107 | - | May 18, 14:20 UTC | May 18, 18:20 UTC | 4h 0m |
| 2026-05-14 | VDA716 | - | May 14, 08:50 UTC | May 14, 09:10 UTC | 20m |
| 2026-05-14 | VDA716 | - | May 14, 05:20 UTC | May 14, 08:05 UTC | 2h 45m |
| 2026-05-13 | VDA716 | - | May 13, 08:45 UTC | May 14, 00:45 UTC | 16h 0m |
| 2026-05-11 | VDA516 | - | May 11, 07:25 UTC | May 11, 10:20 UTC | 2h 55m |
| 2026-05-11 | VDA516 | - | May 11, 03:45 UTC | May 11, 04:25 UTC | 40m |
| 2026-05-10 | VDA515 | - | May 10, 02:55 UTC | May 10, 03:20 UTC | 25m |
| 2026-05-09 | VDA4177 | - | May 9, 02:45 UTC | May 9, 11:15 UTC | 8h 30m |
| 2026-05-01 | VDA316 | - | May 1, 23:25 UTC | May 2, 02:40 UTC | 3h 16m |
| 2026-05-01 | VDA316 | - | May 1, 18:55 UTC | May 1, 19:25 UTC | 30m |
| 2026-04-30 | VDA316 | - | Apr 30, 19:50 UTC | May 1, 19:25 UTC | 23h 35m |
| 2026-04-30 | VDA3159 | - | Apr 30, 19:15 UTC | Apr 30, 19:50 UTC | 35m |
| 2026-04-30 | VDA4170 | - | Apr 30, 06:25 UTC | Apr 30, 13:10 UTC | 6h 45m |
| 2026-04-30 | VDA4170 | - | Apr 30, 05:30 UTC | Apr 30, 05:45 UTC | 15m |
| 2026-04-29 | VDA4169 | NUX → OVB | Apr 29, 10:20 UTC | Apr 29, 10:35 UTC | 15m |
| 2026-04-25 | VDA516 | - | Apr 25, 09:25 UTC | Apr 25, 10:00 UTC | 35m |
| 2026-04-24 | VDA5159 | - | Apr 24, 14:30 UTC | Apr 25, 10:00 UTC | 19h 30m |
| 2026-04-23 | VDA316 | - | Apr 23, 15:10 UTC | Apr 24, 07:35 UTC | 16h 25m |
| 2026-04-22 | VDA3199 | - | Apr 22, 15:15 UTC | Apr 23, 08:01 UTC | 16h 45m |
| 2026-04-22 | VDA4169 | - | Apr 22, 09:25 UTC | Apr 22, 09:40 UTC | 15m |
| 2026-04-21 | VDA4165 | - | Apr 21, 05:45 UTC | Apr 21, 06:15 UTC | 30m |
| 2026-04-16 | VDA716 | - | Apr 16, 03:14 UTC | Apr 16, 04:14 UTC | 1h 0m |
| 2026-04-15 | VDA716 | - | Apr 15, 07:30 UTC | Apr 15, 08:10 UTC | 40m |
| 2026-04-14 | VDA7159 | - | Apr 14, 15:55 UTC | Apr 14, 16:25 UTC | 30m |
| 2026-04-14 | VDA4159 | - | Apr 14, 10:30 UTC | Apr 14, 10:50 UTC | 20m |
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-76951 page for operator, model, and routing details .