sensors Mode-S transponder
151DB1
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73137 · BOEING 777-300ER
- Hex
- 151DB1
- Octal
- 05216661
- Decimal
- 1,383,857
- Country
- RU
- Tail
- RA-73137
- Type
- B77W
- Flights observed
- 169
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- 15h ago
Last known position
Country allocation
The ICAO 24-bit address 151DB1 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 |
|---|---|---|---|
| AFL209 | Aeroflot Russian Airlines | 21 | 2026-05-19 |
| AFL221 | Aeroflot Russian Airlines | 14 | 2026-05-30 |
| AFL325 | Aeroflot Russian Airlines | 13 | 2026-05-09 |
| AFL208 | - | 11 | 2026-06-24 |
| AFL205 | Aeroflot Russian Airlines | 9 | 2026-05-28 |
| AFL220 | Aeroflot Russian Airlines | 8 | 2026-05-29 |
| AFL1709 | - | 8 | 2026-07-11 |
| AFL320 | - | 4 | 2026-07-09 |
| AFL273 | - | 4 | 2026-06-29 |
| AFL272 | - | 4 | 2026-06-28 |
| AFL233 | - | 4 | 2026-07-09 |
| AFL204 | Aeroflot Russian Airlines | 4 | 2026-05-28 |
| AFL1755 | Aeroflot Russian Airlines | 4 | 2026-05-27 |
| AFL324 | - | 3 | 2026-06-27 |
| AFL321 | - | 3 | 2026-07-10 |
| AFL271 | Aeroflot Russian Airlines | 3 | 2026-04-18 |
| AFL270 | Aeroflot Russian Airlines | 3 | 2026-04-17 |
| AFL232 | - | 3 | 2026-07-08 |
| AFL225 | Aeroflot Russian Airlines | 3 | 2026-04-15 |
| AFL1713 | Aeroflot Russian Airlines | 3 | 2026-06-17 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | AFL1013 | - | Jul 13, 17:15 UTC | Jul 13, 18:00 UTC | 45m |
| 2026-07-13 | AFL1012 | - | Jul 13, 14:20 UTC | Jul 13, 15:00 UTC | 40m |
| 2026-07-12 | AFL1012 | - | Jul 12, 16:10 UTC | Jul 12, 16:50 UTC | 40m |
| 2026-07-11 | AFL1709 | - | Jul 11, 16:20 UTC | Jul 12, 16:15 UTC | 23h 55m |
| 2026-07-11 | AFL1709 | - | Jul 11, 15:25 UTC | Jul 11, 16:35 UTC | 1h 10m |
| 2026-07-10 | AFL321 | - | Jul 10, 00:15 UTC | Jul 10, 13:55 UTC | 13h 40m |
| 2026-07-09 | AFL320 | - | Jul 9, 20:05 UTC | Jul 9, 20:45 UTC | 40m |
| 2026-07-09 | AFL233 | - | Jul 9, 03:15 UTC | Jul 9, 07:40 UTC | 4h 25m |
| 2026-07-08 | AFL232 | - | Jul 8, 23:30 UTC | Jul 9, 00:10 UTC | 40m |
| 2026-07-08 | AFL232 | SVO → SVO | Jul 8, 18:55 UTC | Jul 8, 19:25 UTC | 30m |
| 2026-07-07 | AFL1739 | - | Jul 7, 20:55 UTC | Jul 8, 14:00 UTC | 17h 5m |
| 2026-07-07 | AFL1738 | - | Jul 7, 19:35 UTC | Jul 7, 19:45 UTC | 10m |
| 2026-07-07 | AFL320 | - | Jul 7, 00:15 UTC | Jul 7, 13:40 UTC | 13h 25m |
| 2026-07-04 | AFL1015 | - | Jul 4, 13:00 UTC | Jul 4, 14:00 UTC | 1h 0m |
| 2026-07-03 | AFL1013 | - | Jul 3, 16:55 UTC | Jul 4, 10:05 UTC | 17h 10m |
| 2026-07-03 | AFL1012 | - | Jul 3, 14:15 UTC | Jul 3, 14:50 UTC | 35m |
| 2026-07-01 | AFL1709 | VVO → SVO | Jul 1, 00:15 UTC | Jul 1, 16:55 UTC | 16h 40m |
| 2026-06-30 | AFL1709 | VVO → SVO | Jun 30, 15:35 UTC | Jul 1, 00:20 UTC | 8h 45m |
| 2026-06-29 | AFL273 | - | Jun 29, 06:40 UTC | Jun 29, 14:19 UTC | 7h 40m |
| 2026-06-28 | AFL272 | - | Jun 28, 11:59 UTC | Jun 29, 04:34 UTC | 16h 35m |
| 2026-06-27 | AFL1712 | - | Jun 27, 21:34 UTC | Jun 28, 12:25 UTC | 14h 50m |
| 2026-06-27 | AFL1712 | - | Jun 27, 16:35 UTC | Jun 28, 12:25 UTC | 19h 50m |
| 2026-06-27 | AFL324 | - | Jun 27, 02:39 UTC | Jun 27, 21:55 UTC | 19h 15m |
| 2026-06-27 | AFL324 | - | Jun 27, 01:39 UTC | Jun 27, 21:55 UTC | 20h 15m |
| 2026-06-24 | AFL208 | - | Jun 24, 20:49 UTC | Jun 25, 09:29 UTC | 12h 40m |
| 2026-06-24 | AFL208 | - | Jun 24, 13:44 UTC | Jun 25, 09:29 UTC | 19h 45m |
| 2026-06-24 | AFL321 | - | Jun 24, 02:24 UTC | Jun 24, 21:34 UTC | 19h 10m |
| 2026-06-24 | AFL321 | - | Jun 24, 00:59 UTC | Jun 24, 21:34 UTC | 20h 35m |
| 2026-06-23 | AFL320 | - | Jun 23, 23:59 UTC | Jun 24, 21:34 UTC | 21h 35m |
| 2026-06-23 | AFL320 | - | Jun 23, 10:19 UTC | Jun 24, 09:59 UTC | 23h 40m |
| 2026-06-23 | AFL273 | - | Jun 23, 08:20 UTC | Jun 24, 08:14 UTC | 23h 55m |
| 2026-06-23 | AFL273 | - | Jun 23, 06:34 UTC | Jun 24, 03:24 UTC | 20h 50m |
| 2026-06-22 | AFL272 | - | Jun 22, 12:19 UTC | Jun 23, 04:14 UTC | 15h 55m |
| 2026-06-20 | AFL1709 | VVO → SVO | Jun 20, 15:49 UTC | Jun 20, 16:55 UTC | 1h 5m |
| 2026-06-19 | AFL1709 | VVO → SVO | Jun 19, 15:24 UTC | Jun 19, 17:14 UTC | 1h 50m |
| 2026-06-18 | AFL1709 | VVO → SVO | Jun 18, 16:25 UTC | Jun 19, 16:14 UTC | 23h 49m |
| 2026-06-17 | AFL1709 | VVO → SVO | Jun 17, 23:40 UTC | Jun 18, 16:55 UTC | 17h 15m |
| 2026-06-17 | AFL1713 | KHV → SVO | Jun 17, 11:05 UTC | Jun 17, 23:55 UTC | 12h 50m |
| 2026-06-15 | AFL208 | - | Jun 15, 20:45 UTC | Jun 16, 09:50 UTC | 13h 5m |
| 2026-06-15 | AFL208 | SVO → SVO | Jun 15, 17:30 UTC | Jun 15, 17:50 UTC | 20m |
| 2026-06-15 | AFL1003 | KGD → SVO | Jun 15, 11:15 UTC | Jun 15, 13:05 UTC | 1h 50m |
| 2026-06-15 | AFL1002 | SVO → KGD | Jun 15, 07:20 UTC | Jun 15, 09:15 UTC | 1h 55m |
| 2026-06-14 | AFL1003 | KGD → SVO | Jun 14, 12:20 UTC | Jun 14, 13:25 UTC | 1h 5m |
| 2026-06-14 | AFL1002 | SVO → KGD | Jun 14, 09:45 UTC | Jun 14, 10:15 UTC | 30m |
| 2026-06-13 | AFL1139 | AER → SVO | Jun 13, 18:35 UTC | Jun 13, 19:00 UTC | 25m |
| 2026-06-13 | AFL1138 | SVO → AER | Jun 13, 08:50 UTC | Jun 13, 09:15 UTC | 25m |
| 2026-06-12 | AFL1713 | KHV → SVO | Jun 12, 11:05 UTC | Jun 12, 22:20 UTC | 11h 15m |
| 2026-06-11 | AFL1713 | KHV → SVO | Jun 11, 21:50 UTC | Jun 12, 13:50 UTC | 16h 1m |
| 2026-06-10 | AFL1701 | VVO → SVO | Jun 10, 14:30 UTC | Jun 11, 07:55 UTC | 17h 25m |
| 2026-06-10 | AFL1700 | SVO → VVO | Jun 10, 13:20 UTC | Jun 10, 13:45 UTC | 25m |
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-73137 page for operator, model, and routing details .