sensors Mode-S transponder
151DB2
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73138 · BOEING 777-300ER
- Hex
- 151DB2
- Octal
- 05216662
- Decimal
- 1,383,858
- Country
- RU
- Tail
- RA-73138
- Type
- B77W
- Flights observed
- 160
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- 9h ago
Last known position
Country allocation
The ICAO 24-bit address 151DB2 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 | 22 | 2026-05-31 |
| AFL221 | - | 13 | 2026-06-21 |
| AFL204 | - | 10 | 2026-07-13 |
| AFL1731 | - | 10 | 2026-06-20 |
| AFL205 | - | 9 | 2026-07-13 |
| AFL1730 | Aeroflot Russian Airlines | 9 | 2026-06-19 |
| AFL220 | Aeroflot Russian Airlines | 7 | 2026-06-08 |
| AFL1705 | - | 7 | 2026-07-09 |
| AFL321 | Aeroflot Russian Airlines | 5 | 2026-04-27 |
| AFL1745 | - | 4 | 2026-06-25 |
| AFL1714 | - | 4 | 2026-07-03 |
| AFL639 | Aeroflot Russian Airlines | 3 | 2026-04-24 |
| AFL275 | Aeroflot Russian Airlines | 3 | 2026-04-18 |
| AFL233 | - | 3 | 2026-07-11 |
| AFL232 | - | 3 | 2026-07-10 |
| AFL1722 | - | 3 | 2026-06-14 |
| AFL1718 | Aeroflot Russian Airlines | 3 | 2026-06-18 |
| AFL1715 | - | 3 | 2026-06-23 |
| AFL638 | Aeroflot Russian Airlines | 2 | 2026-04-24 |
| AFL320 | Aeroflot Russian Airlines | 2 | 2026-04-26 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | AFL1735 | - | Jul 13, 18:35 UTC | Jul 14, 11:35 UTC | 17h 0m |
| 2026-07-13 | AFL205 | - | Jul 13, 04:05 UTC | Jul 13, 11:25 UTC | 7h 20m |
| 2026-07-13 | AFL204 | - | Jul 13, 01:01 UTC | Jul 13, 01:15 UTC | 15m |
| 2026-07-12 | AFL1757 | - | Jul 12, 06:15 UTC | Jul 12, 22:30 UTC | 16h 15m |
| 2026-07-11 | AFL233 | - | Jul 11, 02:50 UTC | Jul 11, 03:30 UTC | 40m |
| 2026-07-10 | AFL232 | - | Jul 10, 07:05 UTC | Jul 11, 00:00 UTC | 16h 55m |
| 2026-07-10 | AFL205 | - | Jul 10, 04:05 UTC | Jul 10, 04:15 UTC | 10m |
| 2026-07-10 | AFL204 | - | Jul 10, 01:05 UTC | Jul 10, 01:20 UTC | 15m |
| 2026-07-09 | AFL1705 | - | Jul 9, 08:10 UTC | Jul 9, 22:25 UTC | 14h 15m |
| 2026-07-08 | AFL205 | - | Jul 8, 04:00 UTC | Jul 8, 07:40 UTC | 3h 40m |
| 2026-07-07 | AFL273 | - | Jul 7, 06:35 UTC | Jul 8, 01:00 UTC | 18h 25m |
| 2026-07-07 | AFL272 | - | Jul 7, 00:25 UTC | Jul 7, 04:20 UTC | 3h 55m |
| 2026-07-06 | AFL272 | - | Jul 6, 19:50 UTC | Jul 6, 20:20 UTC | 30m |
| 2026-07-06 | AFL1017 | - | Jul 6, 13:10 UTC | Jul 6, 14:10 UTC | 1h 0m |
| 2026-07-06 | AFL1016 | - | Jul 6, 09:40 UTC | Jul 6, 10:05 UTC | 25m |
| 2026-07-05 | AFL1010 | - | Jul 5, 16:25 UTC | Jul 5, 16:55 UTC | 30m |
| 2026-07-03 | AFL1714 | - | Jul 3, 20:45 UTC | Jul 4, 11:30 UTC | 14h 45m |
| 2026-07-03 | AFL1714 | - | Jul 3, 05:05 UTC | Jul 3, 21:45 UTC | 16h 40m |
| 2026-07-02 | AFL1723 | - | Jul 2, 15:00 UTC | Jul 3, 05:30 UTC | 14h 30m |
| 2026-07-02 | AFL1705 | - | Jul 2, 08:35 UTC | Jul 3, 05:30 UTC | 20h 55m |
| 2026-07-02 | AFL1705 | - | Jul 2, 08:20 UTC | Jul 3, 05:30 UTC | 21h 10m |
| 2026-07-01 | AFL1017 | - | Jul 1, 10:35 UTC | Jul 2, 09:35 UTC | 23h 0m |
| 2026-07-01 | AFL1016 | - | Jul 1, 07:45 UTC | Jul 1, 08:25 UTC | 40m |
| 2026-06-30 | AFL1713 | - | Jun 30, 13:10 UTC | Jun 30, 14:20 UTC | 1h 10m |
| 2026-06-29 | AFL1713 | - | Jun 29, 15:39 UTC | Jun 30, 14:20 UTC | 22h 41m |
| 2026-06-28 | AFL1010 | - | Jun 28, 16:14 UTC | Jun 28, 16:49 UTC | 35m |
| 2026-06-26 | AFL205 | - | Jun 26, 04:04 UTC | Jun 26, 07:39 UTC | 3h 35m |
| 2026-06-26 | AFL204 | - | Jun 26, 00:59 UTC | Jun 26, 01:15 UTC | 15m |
| 2026-06-25 | AFL1745 | - | Jun 25, 06:35 UTC | Jun 25, 22:14 UTC | 15h 40m |
| 2026-06-24 | AFL1745 | - | Jun 24, 15:24 UTC | Jun 25, 07:45 UTC | 16h 20m |
| 2026-06-24 | AFL1745 | - | Jun 24, 10:35 UTC | Jun 25, 07:45 UTC | 21h 10m |
| 2026-06-24 | AFL1745 | - | Jun 24, 10:25 UTC | Jun 25, 07:45 UTC | 21h 20m |
| 2026-06-23 | AFL1715 | - | Jun 23, 20:34 UTC | Jun 24, 15:29 UTC | 18h 55m |
| 2026-06-23 | AFL1714 | - | Jun 23, 19:24 UTC | Jun 24, 15:29 UTC | 20h 5m |
| 2026-06-23 | AFL1714 | - | Jun 23, 06:24 UTC | Jun 23, 20:34 UTC | 14h 10m |
| 2026-06-22 | AFL1744 | SVO → UUS | Jun 22, 15:45 UTC | Jun 23, 06:49 UTC | 15h 5m |
| 2026-06-22 | AFL1744 | SVO → UUS | Jun 22, 07:14 UTC | Jun 23, 06:29 UTC | 23h 15m |
| 2026-06-22 | AFL205 | - | Jun 22, 04:09 UTC | Jun 22, 16:50 UTC | 12h 40m |
| 2026-06-22 | AFL204 | - | Jun 22, 01:10 UTC | Jun 22, 01:25 UTC | 15m |
| 2026-06-21 | AFL221 | - | Jun 21, 08:54 UTC | Jun 21, 22:34 UTC | 13h 40m |
| 2026-06-20 | AFL221 | - | Jun 20, 19:49 UTC | Jun 21, 09:35 UTC | 13h 45m |
| 2026-06-20 | AFL1731 | - | Jun 20, 06:49 UTC | Jun 20, 20:25 UTC | 13h 35m |
| 2026-06-19 | AFL1730 | SVO → PKC | Jun 19, 15:19 UTC | Jun 20, 08:14 UTC | 16h 55m |
| 2026-06-19 | AFL1730 | SVO → PKC | Jun 19, 06:54 UTC | Jun 19, 16:29 UTC | 9h 35m |
| 2026-06-18 | AFL1730 | SVO → PKC | Jun 18, 16:55 UTC | Jun 19, 16:29 UTC | 23h 34m |
| 2026-06-18 | AFL1718 | SVO → KHV | Jun 18, 15:30 UTC | Jun 18, 15:50 UTC | 20m |
| 2026-06-17 | AFL204 | - | Jun 17, 18:50 UTC | Jun 18, 08:00 UTC | 13h 10m |
| 2026-06-17 | AFL1015 | KGD → SVO | Jun 17, 10:35 UTC | Jun 18, 08:00 UTC | 21h 25m |
| 2026-06-17 | AFL1015 | KGD → SVO | Jun 17, 09:50 UTC | Jun 18, 08:00 UTC | 22h 10m |
| 2026-06-16 | AFL1025 | KGD → SVO | Jun 16, 17:15 UTC | Jun 17, 07:30 UTC | 14h 16m |
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-73138 page for operator, model, and routing details .