sensors Mode-S transponder
152ADF
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-76511 · ILYUSHIN Il-76/82
- Hex
- 152ADF
- Octal
- 05225337
- Decimal
- 1,387,231
- Country
- RU
- Tail
- RA-76511
- Type
- IL76
- Flights observed
- 39
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- 17h ago
Last known position
Country allocation
The ICAO 24-bit address 152ADF 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 |
|---|---|---|---|
| VDA216 | - | 7 | 2026-06-04 |
| VDA716 | - | 4 | 2026-06-01 |
| VDA7870 | - | 2 | 2026-04-26 |
| VDA715 | - | 2 | 2026-04-19 |
| VDA608 | - | 2 | 2026-05-11 |
| VDA4182 | - | 2 | 2026-05-23 |
| VDA415 | - | 2 | 2026-05-02 |
| VDA316 | - | 2 | 2026-05-28 |
| VDA3159 | - | 2 | 2026-05-27 |
| VDA215 | - | 2 | 2026-06-02 |
| VDA7907 | - | 1 | 2026-05-22 |
| VDA7906 | - | 1 | 2026-05-20 |
| VDA7869 | - | 1 | 2026-04-25 |
| VDA7161 | - | 1 | 2026-04-21 |
| VDA7159 | - | 1 | 2026-05-31 |
| VDA6159 | - | 1 | 2026-05-25 |
| VDA6079 | - | 1 | 2026-05-10 |
| VDA516 | - | 1 | 2026-05-30 |
| VDA515 | - | 1 | 2026-05-29 |
| VDA416 | - | 1 | 2026-04-24 |
Recent flights last 39
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-04 | VDA216 | - | Jun 4, 07:40 UTC | Jun 4, 08:15 UTC | 35m |
| 2026-06-02 | VDA215 | - | Jun 2, 12:50 UTC | Jun 2, 16:55 UTC | 4h 5m |
| 2026-06-01 | VDA716 | - | Jun 1, 22:50 UTC | Jun 2, 01:25 UTC | 2h 35m |
| 2026-05-31 | VDA716 | - | May 31, 23:50 UTC | Jun 1, 17:50 UTC | 18h 0m |
| 2026-05-31 | VDA716 | - | May 31, 23:40 UTC | Jun 1, 17:50 UTC | 18h 10m |
| 2026-05-31 | VDA7159 | - | May 31, 14:25 UTC | May 31, 15:50 UTC | 1h 25m |
| 2026-05-30 | VDA516 | - | May 30, 13:40 UTC | May 30, 14:20 UTC | 40m |
| 2026-05-29 | VDA515 | - | May 29, 10:00 UTC | May 29, 14:00 UTC | 4h 0m |
| 2026-05-28 | VDA316 | - | May 28, 23:20 UTC | May 29, 01:45 UTC | 2h 25m |
| 2026-05-27 | VDA3159 | - | May 27, 14:35 UTC | May 28, 08:00 UTC | 17h 25m |
| 2026-05-27 | VDA3159 | - | May 27, 06:04 UTC | May 27, 09:55 UTC | 3h 51m |
| 2026-05-25 | VDA6159 | - | May 25, 16:15 UTC | May 26, 07:45 UTC | 15h 29m |
| 2026-05-23 | VDA4182 | - | May 23, 07:05 UTC | May 23, 07:15 UTC | 10m |
| 2026-05-23 | VDA4182 | - | May 23, 06:00 UTC | May 23, 06:10 UTC | 10m |
| 2026-05-22 | VDA7907 | - | May 22, 12:30 UTC | May 22, 16:05 UTC | 3h 35m |
| 2026-05-20 | VDA7906 | - | May 20, 07:35 UTC | May 20, 11:20 UTC | 3h 45m |
| 2026-05-16 | VDA408 | - | May 16, 13:25 UTC | May 16, 18:45 UTC | 5h 20m |
| 2026-05-15 | VDA4079 | - | May 15, 10:40 UTC | May 15, 13:25 UTC | 2h 45m |
| 2026-05-14 | VDA216 | - | May 14, 18:45 UTC | May 14, 18:55 UTC | 10m |
| 2026-05-14 | VDA216 | - | May 14, 11:15 UTC | May 14, 11:50 UTC | 35m |
| 2026-05-13 | VDA216 | - | May 13, 15:55 UTC | May 14, 11:50 UTC | 19h 55m |
| 2026-05-11 | VDA608 | - | May 11, 20:30 UTC | May 12, 15:40 UTC | 19h 10m |
| 2026-05-11 | VDA608 | - | May 11, 18:30 UTC | May 12, 15:40 UTC | 21h 10m |
| 2026-05-10 | VDA6079 | - | May 10, 19:45 UTC | May 10, 20:00 UTC | 15m |
| 2026-05-09 | VDA316 | - | May 9, 21:09 UTC | May 9, 21:34 UTC | 25m |
| 2026-05-02 | VDA415 | - | May 2, 01:45 UTC | May 2, 02:20 UTC | 35m |
| 2026-04-29 | VDA216 | - | Apr 29, 09:30 UTC | Apr 29, 10:05 UTC | 35m |
| 2026-04-26 | VDA7870 | - | Apr 26, 14:20 UTC | Apr 26, 14:55 UTC | 35m |
| 2026-04-26 | VDA7870 | - | Apr 26, 06:35 UTC | Apr 26, 06:50 UTC | 15m |
| 2026-04-25 | VDA7869 | SVO → SVO | Apr 25, 07:50 UTC | Apr 25, 08:00 UTC | 10m |
| 2026-04-24 | VDA416 | - | Apr 24, 08:15 UTC | Apr 24, 21:10 UTC | 12h 55m |
| 2026-04-23 | VDA415 | - | Apr 23, 15:45 UTC | Apr 23, 16:00 UTC | 15m |
| 2026-04-22 | VDA216 | - | Apr 22, 03:20 UTC | Apr 22, 16:35 UTC | 13h 15m |
| 2026-04-21 | VDA7161 | - | Apr 21, 02:30 UTC | Apr 21, 21:00 UTC | 18h 30m |
| 2026-04-20 | VDA716 | - | Apr 20, 18:50 UTC | Apr 20, 19:30 UTC | 40m |
| 2026-04-19 | VDA715 | - | Apr 19, 14:25 UTC | Apr 19, 14:55 UTC | 30m |
| 2026-04-18 | VDA715 | - | Apr 18, 20:40 UTC | Apr 18, 20:55 UTC | 15m |
| 2026-04-18 | VDA216 | - | Apr 18, 01:45 UTC | Apr 18, 02:25 UTC | 40m |
| 2026-04-16 | VDA215 | - | Apr 16, 09:45 UTC | Apr 16, 10:14 UTC | 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-76511 page for operator, model, and routing details .