sensors Mode-S transponder
151DB3
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73139 · BOEING 777-300ER
- Hex
- 151DB3
- Octal
- 05216663
- Decimal
- 1,383,859
- Country
- RU
- Tail
- RA-73139
- Type
- B77W
- Flights observed
- 194
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- Jul 26, 14:50 UTC
Last known position
Country allocation
The ICAO 24-bit address 151DB3 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 |
|---|---|---|---|
| AFL320 | Aeroflot Russian Airlines | 27 | 2026-07-25 |
| AFL321 | Aeroflot Russian Airlines | 25 | 2026-07-26 |
| AFL205 | Aeroflot Russian Airlines | 22 | 2026-07-18 |
| AFL204 | Aeroflot Russian Airlines | 20 | 2026-07-18 |
| AFL221 | - | 19 | 2026-07-10 |
| AFL220 | - | 7 | 2026-07-10 |
| AFL208 | - | 7 | 2026-07-15 |
| AFL232 | - | 6 | 2026-07-05 |
| AFL209 | - | 6 | 2026-07-15 |
| AFL233 | - | 5 | 2026-07-06 |
| AFL585 | Aeroflot Russian Airlines | 3 | 2026-05-01 |
| AFL1731 | Aeroflot Russian Airlines | 3 | 2026-07-21 |
| AFL1719 | - | 3 | 2026-07-13 |
| AFL1713 | - | 3 | 2026-07-15 |
| AFL325 | - | 2 | 2026-04-13 |
| AFL273 | Aeroflot Russian Airlines | 2 | 2026-06-09 |
| AFL272 | Aeroflot Russian Airlines | 2 | 2026-06-09 |
| AFL2701 | Aeroflot Russian Airlines | 2 | 2026-05-11 |
| AFL2700 | Aeroflot Russian Airlines | 2 | 2026-05-11 |
| AFL1757 | Aeroflot Russian Airlines | 2 | 2026-07-18 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | AFL321 | MLE → SVO | Jul 26, 14:10 UTC | Jul 26, 14:50 UTC | 40m |
| 2026-07-25 | AFL321 | MLE → SVO | Jul 25, 21:00 UTC | Jul 26, 13:35 UTC | 16h 36m |
| 2026-07-25 | AFL320 | SVO → MLE | Jul 25, 19:55 UTC | Jul 25, 20:20 UTC | 25m |
| 2026-07-25 | AFL321 | MLE → SVO | Jul 25, 00:30 UTC | Jul 25, 13:40 UTC | 13h 10m |
| 2026-07-24 | AFL320 | SVO → MLE | Jul 24, 12:50 UTC | Jul 25, 10:00 UTC | 21h 10m |
| 2026-07-24 | AFL320 | SVO → MLE | Jul 24, 12:25 UTC | Jul 25, 10:00 UTC | 21h 35m |
| 2026-07-23 | AFL1019 | - | Jul 23, 15:35 UTC | Jul 23, 16:55 UTC | 1h 20m |
| 2026-07-23 | AFL1018 | SVO → KGD | Jul 23, 12:05 UTC | Jul 23, 13:00 UTC | 55m |
| 2026-07-21 | AFL1731 | PKC → SVO | Jul 21, 06:30 UTC | Jul 21, 15:40 UTC | 9h 10m |
| 2026-07-20 | AFL1731 | PKC → SVO | Jul 20, 15:40 UTC | Jul 21, 07:10 UTC | 15h 29m |
| 2026-07-20 | AFL1730 | - | Jul 20, 14:10 UTC | Jul 20, 14:30 UTC | 20m |
| 2026-07-18 | AFL1757 | VVO → SVO | Jul 18, 15:25 UTC | Jul 19, 08:50 UTC | 17h 25m |
| 2026-07-18 | AFL1757 | VVO → SVO | Jul 18, 10:05 UTC | Jul 19, 08:45 UTC | 22h 40m |
| 2026-07-18 | AFL205 | PKX → SVO | Jul 18, 07:10 UTC | Jul 19, 06:45 UTC | 23h 35m |
| 2026-07-18 | AFL205 | PKX → SVO | Jul 18, 04:10 UTC | Jul 18, 15:35 UTC | 11h 25m |
| 2026-07-18 | AFL204 | SVO → PKX | Jul 18, 00:55 UTC | Jul 18, 01:10 UTC | 15m |
| 2026-07-17 | AFL1735 | - | Jul 17, 10:10 UTC | Jul 17, 22:20 UTC | 12h 10m |
| 2026-07-15 | AFL209 | - | Jul 15, 20:50 UTC | Jul 16, 13:05 UTC | 16h 15m |
| 2026-07-15 | AFL208 | SVO → SVO | Jul 15, 17:40 UTC | Jul 15, 18:00 UTC | 20m |
| 2026-07-15 | AFL1713 | - | Jul 15, 11:00 UTC | Jul 15, 13:10 UTC | 2h 10m |
| 2026-07-14 | AFL1712 | SVO → SVO | Jul 14, 20:25 UTC | Jul 14, 20:45 UTC | 20m |
| 2026-07-14 | AFL1709 | - | Jul 14, 15:15 UTC | Jul 14, 16:35 UTC | 1h 20m |
| 2026-07-13 | AFL1719 | - | Jul 13, 08:25 UTC | Jul 13, 08:35 UTC | 10m |
| 2026-07-13 | AFL1719 | - | Jul 13, 06:30 UTC | Jul 13, 07:45 UTC | 1h 15m |
| 2026-07-12 | AFL205 | - | Jul 12, 07:20 UTC | Jul 13, 06:45 UTC | 23h 25m |
| 2026-07-12 | AFL205 | - | Jul 12, 04:20 UTC | Jul 12, 08:05 UTC | 3h 45m |
| 2026-07-12 | AFL204 | - | Jul 12, 01:15 UTC | Jul 12, 01:25 UTC | 10m |
| 2026-07-11 | AFL204 | - | Jul 11, 22:01 UTC | Jul 11, 22:40 UTC | 40m |
| 2026-07-11 | AFL204 | SVO → SVO | Jul 11, 18:45 UTC | Jul 11, 19:00 UTC | 15m |
| 2026-07-10 | AFL221 | - | Jul 10, 20:05 UTC | Jul 11, 09:20 UTC | 13h 15m |
| 2026-07-10 | AFL220 | - | Jul 10, 08:50 UTC | Jul 11, 08:45 UTC | 23h 55m |
| 2026-07-10 | AFL209 | - | Jul 10, 08:40 UTC | Jul 10, 20:40 UTC | 12h 0m |
| 2026-07-09 | AFL209 | - | Jul 9, 20:50 UTC | Jul 10, 20:40 UTC | 23h 50m |
| 2026-07-09 | AFL208 | - | Jul 9, 17:40 UTC | Jul 9, 17:55 UTC | 15m |
| 2026-07-08 | AFL221 | - | Jul 8, 20:40 UTC | Jul 9, 10:25 UTC | 13h 45m |
| 2026-07-08 | AFL220 | SVO → SVO | Jul 8, 17:30 UTC | Jul 8, 17:55 UTC | 25m |
| 2026-07-07 | AFL221 | - | Jul 7, 19:55 UTC | Jul 8, 10:20 UTC | 14h 25m |
| 2026-07-07 | AFL221 | - | Jul 7, 08:50 UTC | Jul 7, 20:30 UTC | 11h 40m |
| 2026-07-06 | AFL220 | - | Jul 6, 20:05 UTC | Jul 7, 09:30 UTC | 13h 25m |
| 2026-07-06 | AFL233 | - | Jul 6, 02:30 UTC | Jul 6, 20:45 UTC | 18h 15m |
| 2026-07-05 | AFL232 | - | Jul 5, 23:25 UTC | Jul 6, 00:10 UTC | 45m |
| 2026-07-05 | AFL232 | SVO → SVO | Jul 5, 18:45 UTC | Jul 5, 19:15 UTC | 30m |
| 2026-07-04 | AFL1719 | KHV → SVO | Jul 4, 16:25 UTC | Jul 5, 08:10 UTC | 15h 45m |
| 2026-07-03 | AFL1701 | - | Jul 3, 05:20 UTC | Jul 3, 06:40 UTC | 1h 20m |
| 2026-07-02 | AFL1701 | - | Jul 2, 07:20 UTC | Jul 3, 06:40 UTC | 23h 20m |
| 2026-07-01 | AFL205 | - | Jul 1, 04:35 UTC | Jul 1, 08:30 UTC | 3h 55m |
| 2026-07-01 | AFL204 | - | Jul 1, 01:55 UTC | Jul 1, 02:05 UTC | 10m |
| 2026-06-30 | AFL221 | - | Jun 30, 09:10 UTC | Jun 30, 23:20 UTC | 14h 10m |
| 2026-06-29 | AFL221 | - | Jun 29, 20:15 UTC | Jun 30, 09:55 UTC | 13h 41m |
| 2026-06-27 | AFL1704 | - | Jun 27, 16:55 UTC | Jun 27, 17:04 UTC | 10m |
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-73139 page for operator, model, and routing details .