sensors Mode-S transponder
151DBF
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73151 · AIRBUS A-350-900
- Hex
- 151DBF
- Octal
- 05216677
- Decimal
- 1,383,871
- Country
- RU
- Tail
- RA-73151
- Type
- A359
- Flights observed
- 51
- Distinct callsigns
- 11
- Country
- RU
- Last broadcast
- 8h ago
Last known position
Country allocation
The ICAO 24-bit address 151DBF 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 11 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| AFL295 | Aeroflot Russian Airlines | 10 | 2026-05-30 |
| AFL298 | - | 8 | 2026-05-20 |
| AFL297 | Aeroflot Russian Airlines | 7 | 2026-05-10 |
| AFL294 | Aeroflot Russian Airlines | 6 | 2026-05-29 |
| AFL213 | Aeroflot Russian Airlines | 6 | 2026-05-29 |
| AFL212 | Aeroflot Russian Airlines | 5 | 2026-05-28 |
| AFL599 | Aeroflot Russian Airlines | 3 | 2026-04-30 |
| AFL296 | Aeroflot Russian Airlines | 2 | 2026-05-09 |
| AFL225 | Aeroflot Russian Airlines | 2 | 2026-05-08 |
| AFL299 | Aeroflot Russian Airlines | 1 | 2026-05-21 |
| AFL245 | Aeroflot Russian Airlines | 1 | 2026-04-27 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-30 | AFL295 | SVO → ATH | May 30, 00:50 UTC | May 30, 06:55 UTC | 6h 5m |
| 2026-05-29 | AFL294 | VCE → SVO | May 29, 16:50 UTC | May 29, 17:35 UTC | 45m |
| 2026-05-29 | AFL213 | HKG → SVO | May 29, 09:10 UTC | May 29, 09:50 UTC | 40m |
| 2026-05-29 | AFL213 | HKG → SVO | May 29, 04:00 UTC | May 29, 04:20 UTC | 20m |
| 2026-05-28 | AFL212 | SVO → HKG | May 28, 16:35 UTC | May 28, 17:00 UTC | 25m |
| 2026-05-26 | AFL294 | VCE → SVO | May 26, 21:04 UTC | May 27, 13:40 UTC | 16h 35m |
| 2026-05-26 | AFL294 | VCE → SVO | May 26, 16:35 UTC | May 27, 13:40 UTC | 21h 5m |
| 2026-05-24 | AFL295 | SVO → ATH | May 24, 20:45 UTC | May 25, 06:45 UTC | 10h 0m |
| 2026-05-21 | AFL299 | CXR → SVO | May 21, 01:50 UTC | May 21, 14:30 UTC | 12h 40m |
| 2026-05-20 | AFL298 | - | May 20, 07:50 UTC | May 21, 04:00 UTC | 20h 10m |
| 2026-05-20 | AFL295 | SVO → ATH | May 20, 05:50 UTC | May 21, 04:00 UTC | 22h 10m |
| 2026-05-20 | AFL295 | SVO → ATH | May 20, 05:30 UTC | May 21, 03:45 UTC | 22h 15m |
| 2026-05-19 | AFL295 | SVO → ATH | May 19, 22:55 UTC | May 20, 09:45 UTC | 10h 51m |
| 2026-05-18 | AFL298 | - | May 18, 02:00 UTC | May 18, 11:30 UTC | 9h 30m |
| 2026-05-17 | AFL298 | - | May 17, 08:50 UTC | May 18, 05:55 UTC | 21h 5m |
| 2026-05-17 | AFL213 | HKG → SVO | May 17, 03:55 UTC | May 17, 04:10 UTC | 15m |
| 2026-05-16 | AFL212 | SVO → HKG | May 16, 19:20 UTC | May 17, 01:20 UTC | 6h 0m |
| 2026-05-15 | AFL213 | HKG → SVO | May 15, 10:45 UTC | May 15, 11:20 UTC | 35m |
| 2026-05-15 | AFL213 | HKG → SVO | May 15, 05:35 UTC | May 15, 05:55 UTC | 20m |
| 2026-05-14 | AFL212 | SVO → HKG | May 14, 19:45 UTC | May 15, 01:40 UTC | 5h 55m |
| 2026-05-13 | AFL298 | - | May 13, 01:25 UTC | May 13, 12:30 UTC | 11h 5m |
| 2026-05-10 | AFL297 | DPS → SVO | May 10, 07:15 UTC | May 11, 01:34 UTC | 18h 20m |
| 2026-05-10 | AFL297 | DPS → SVO | May 10, 04:25 UTC | May 11, 01:34 UTC | 21h 10m |
| 2026-05-09 | AFL297 | DPS → SVO | May 9, 16:30 UTC | May 10, 09:45 UTC | 17h 15m |
| 2026-05-09 | AFL297 | DPS → SVO | May 9, 12:35 UTC | May 10, 09:45 UTC | 21h 10m |
| 2026-05-09 | AFL296 | SVO → DPS | May 9, 03:50 UTC | May 9, 21:25 UTC | 17h 35m |
| 2026-05-08 | AFL225 | SVO → ATH | May 8, 11:09 UTC | May 9, 04:30 UTC | 17h 20m |
| 2026-05-06 | AFL298 | - | May 6, 09:50 UTC | May 7, 05:15 UTC | 19h 24m |
| 2026-05-06 | AFL298 | - | May 6, 09:35 UTC | May 7, 05:15 UTC | 19h 39m |
| 2026-05-06 | AFL298 | - | May 6, 05:50 UTC | May 7, 05:15 UTC | 23h 24m |
| 2026-05-06 | AFL298 | - | May 6, 05:35 UTC | May 7, 03:35 UTC | 21h 59m |
| 2026-05-05 | AFL295 | SVO → ATH | May 5, 23:00 UTC | May 6, 09:50 UTC | 10h 50m |
| 2026-05-03 | AFL294 | VCE → SVO | May 3, 22:45 UTC | May 4, 07:05 UTC | 8h 20m |
| 2026-05-03 | AFL294 | VCE → SVO | May 3, 09:50 UTC | May 4, 07:05 UTC | 21h 15m |
| 2026-05-03 | AFL294 | VCE → SVO | May 3, 09:35 UTC | May 4, 07:05 UTC | 21h 30m |
| 2026-05-03 | AFL213 | HKG → SVO | May 3, 04:15 UTC | May 3, 04:30 UTC | 15m |
| 2026-05-02 | AFL212 | SVO → HKG | May 2, 19:30 UTC | May 3, 02:00 UTC | 6h 30m |
| 2026-05-02 | AFL212 | SVO → HKG | May 2, 03:50 UTC | May 3, 02:00 UTC | 22h 10m |
| 2026-05-01 | AFL225 | SVO → ATH | May 1, 11:30 UTC | May 2, 04:15 UTC | 16h 45m |
| 2026-04-30 | AFL599 | CXR → SVO | Apr 30, 13:50 UTC | May 1, 11:55 UTC | 22h 5m |
| 2026-04-30 | AFL599 | CXR → SVO | Apr 30, 12:10 UTC | May 1, 11:45 UTC | 23h 35m |
| 2026-04-30 | AFL599 | CXR → SVO | Apr 30, 03:50 UTC | Apr 30, 14:50 UTC | 11h 0m |
| 2026-04-29 | AFL295 | SVO → ATH | Apr 29, 07:50 UTC | Apr 30, 04:00 UTC | 20h 10m |
| 2026-04-29 | AFL295 | SVO → ATH | Apr 29, 05:50 UTC | Apr 30, 04:00 UTC | 22h 10m |
| 2026-04-29 | AFL295 | SVO → ATH | Apr 29, 05:40 UTC | Apr 29, 09:45 UTC | 4h 6m |
| 2026-04-27 | AFL245 | SVO → LHR | Apr 27, 03:50 UTC | Apr 27, 15:25 UTC | 11h 35m |
| 2026-04-15 | AFL297 | DPS → SVO | Apr 15, 09:00 UTC | Apr 15, 10:00 UTC | 1h 0m |
| 2026-04-15 | AFL297 | DPS → SVO | Apr 15, 07:25 UTC | Apr 15, 08:55 UTC | 1h 30m |
| 2026-04-15 | AFL297 | DPS → SVO | Apr 15, 04:40 UTC | Apr 15, 04:50 UTC | 10m |
| 2026-04-14 | AFL296 | - | Apr 14, 16:50 UTC | Apr 14, 18:45 UTC | 1h 55m |
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-73151 page for operator, model, and routing details .