sensors Mode-S transponder
151DB0
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73136 · BOEING 777-300ER
- Hex
- 151DB0
- Octal
- 05216660
- Decimal
- 1,383,856
- Country
- RU
- Tail
- RA-73136
- Type
- B77W
- Flights observed
- 107
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- Jul 26, 21:10 UTC
Current position
Country allocation
The ICAO 24-bit address 151DB0 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 |
|---|---|---|---|
| AFL204 | Aeroflot Russian Airlines | 9 | 2026-07-22 |
| AFL272 | Aeroflot Russian Airlines | 8 | 2026-07-21 |
| AFL205 | Aeroflot Russian Airlines | 8 | 2026-07-22 |
| AFL209 | - | 7 | 2026-07-17 |
| AFL324 | - | 4 | 2026-07-02 |
| AFL285 | - | 4 | 2026-07-13 |
| AFL273 | Aeroflot Russian Airlines | 4 | 2026-07-21 |
| AFL221 | - | 4 | 2026-07-18 |
| AFL1719 | Aeroflot Russian Airlines | 4 | 2026-07-25 |
| AFL284 | - | 3 | 2026-07-12 |
| AFL275 | Aeroflot Russian Airlines | 3 | 2026-04-25 |
| AFL220 | - | 3 | 2026-07-17 |
| AFL208 | Aeroflot Russian Airlines | 3 | 2026-07-26 |
| AFL1757 | - | 3 | 2026-07-11 |
| AFL1745 | - | 3 | 2026-06-24 |
| AFL1714 | Aeroflot Russian Airlines | 3 | 2026-06-22 |
| AFL321 | - | 2 | 2026-07-05 |
| AFL288 | Aeroflot Russian Airlines | 2 | 2026-04-29 |
| AFL225 | Aeroflot Russian Airlines | 2 | 2026-04-16 |
| AFL1713 | Aeroflot Russian Airlines | 2 | 2026-05-04 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | AFL208 | SVO → PVG | Jul 26, 06:30 UTC | Jul 26, 21:10 UTC | 14h 41m |
| 2026-07-25 | AFL1719 | KHV → SVO | Jul 25, 09:10 UTC | Jul 25, 09:20 UTC | 10m |
| 2026-07-25 | AFL1719 | KHV → SVO | Jul 25, 07:00 UTC | Jul 25, 08:20 UTC | 1h 20m |
| 2026-07-24 | AFL1719 | KHV → SVO | Jul 24, 08:05 UTC | Jul 25, 08:00 UTC | 23h 55m |
| 2026-07-24 | AFL1719 | KHV → SVO | Jul 24, 07:50 UTC | Jul 24, 08:15 UTC | 25m |
| 2026-07-22 | AFL205 | PKX → SVO | Jul 22, 10:20 UTC | Jul 22, 12:20 UTC | 2h 0m |
| 2026-07-22 | AFL204 | SVO → PKX | Jul 22, 02:50 UTC | Jul 22, 03:05 UTC | 15m |
| 2026-07-21 | AFL273 | BKK → SVO | Jul 21, 06:45 UTC | Jul 22, 00:15 UTC | 17h 30m |
| 2026-07-21 | AFL272 | SVO → BKK | Jul 21, 00:45 UTC | Jul 21, 04:40 UTC | 3h 55m |
| 2026-07-20 | AFL273 | BKK → SVO | Jul 20, 06:35 UTC | Jul 20, 15:45 UTC | 9h 10m |
| 2026-07-20 | AFL272 | SVO → BKK | Jul 20, 00:10 UTC | Jul 20, 04:30 UTC | 4h 20m |
| 2026-07-19 | AFL272 | SVO → BKK | Jul 19, 07:05 UTC | Jul 20, 04:30 UTC | 21h 25m |
| 2026-07-19 | AFL272 | SVO → BKK | Jul 19, 02:50 UTC | Jul 20, 02:00 UTC | 23h 10m |
| 2026-07-18 | AFL221 | - | Jul 18, 08:50 UTC | Jul 19, 00:35 UTC | 15h 45m |
| 2026-07-17 | AFL221 | - | Jul 17, 18:10 UTC | Jul 18, 11:55 UTC | 17h 46m |
| 2026-07-17 | AFL220 | - | Jul 17, 11:25 UTC | Jul 18, 09:35 UTC | 22h 11m |
| 2026-07-17 | AFL209 | - | Jul 17, 08:54 UTC | Jul 17, 20:40 UTC | 11h 45m |
| 2026-07-16 | AFL209 | - | Jul 16, 20:49 UTC | Jul 17, 20:00 UTC | 23h 10m |
| 2026-07-16 | AFL205 | - | Jul 16, 11:10 UTC | Jul 16, 11:20 UTC | 10m |
| 2026-07-16 | AFL205 | - | Jul 16, 04:05 UTC | Jul 16, 07:55 UTC | 3h 50m |
| 2026-07-16 | AFL204 | - | Jul 16, 01:00 UTC | Jul 16, 01:10 UTC | 10m |
| 2026-07-15 | AFL204 | - | Jul 15, 21:50 UTC | Jul 15, 22:35 UTC | 45m |
| 2026-07-15 | AFL204 | SVO → SVO | Jul 15, 18:40 UTC | Jul 15, 19:10 UTC | 30m |
| 2026-07-15 | AFL221 | - | Jul 15, 09:35 UTC | Jul 15, 12:40 UTC | 3h 5m |
| 2026-07-14 | AFL220 | - | Jul 14, 17:45 UTC | Jul 14, 20:30 UTC | 2h 45m |
| 2026-07-13 | AFL209 | - | Jul 13, 20:40 UTC | Jul 14, 09:35 UTC | 12h 55m |
| 2026-07-13 | AFL285 | - | Jul 13, 05:50 UTC | Jul 13, 21:15 UTC | 15h 25m |
| 2026-07-12 | AFL285 | - | Jul 12, 22:05 UTC | Jul 13, 21:15 UTC | 23h 10m |
| 2026-07-12 | AFL284 | - | Jul 12, 21:25 UTC | Jul 13, 08:01 UTC | 10h 35m |
| 2026-07-12 | AFL284 | - | Jul 12, 04:05 UTC | Jul 12, 23:50 UTC | 19h 45m |
| 2026-07-12 | AFL284 | - | Jul 12, 03:55 UTC | Jul 12, 23:50 UTC | 19h 55m |
| 2026-07-11 | AFL1723 | - | Jul 11, 14:50 UTC | Jul 12, 05:10 UTC | 14h 20m |
| 2026-07-11 | AFL1722 | SVO → SVO | Jul 11, 13:15 UTC | Jul 11, 13:40 UTC | 25m |
| 2026-07-11 | AFL1757 | - | Jul 11, 06:30 UTC | Jul 11, 07:45 UTC | 1h 15m |
| 2026-07-10 | AFL1757 | - | Jul 10, 10:05 UTC | Jul 11, 07:45 UTC | 21h 41m |
| 2026-07-10 | AFL1757 | - | Jul 10, 09:05 UTC | Jul 11, 07:45 UTC | 22h 40m |
| 2026-07-06 | AFL273 | - | Jul 6, 06:50 UTC | Jul 6, 14:35 UTC | 7h 45m |
| 2026-07-05 | AFL272 | - | Jul 5, 13:30 UTC | Jul 6, 04:45 UTC | 15h 15m |
| 2026-07-05 | AFL272 | - | Jul 5, 08:35 UTC | Jul 6, 04:45 UTC | 20h 10m |
| 2026-07-05 | AFL272 | - | Jul 5, 06:55 UTC | Jul 6, 04:00 UTC | 21h 5m |
| 2026-07-05 | AFL321 | - | Jul 5, 02:10 UTC | Jul 6, 01:35 UTC | 23h 25m |
| 2026-07-05 | AFL321 | - | Jul 5, 00:25 UTC | Jul 5, 21:15 UTC | 20h 50m |
| 2026-07-04 | AFL320 | SVO → SVO | Jul 4, 20:05 UTC | Jul 4, 20:45 UTC | 40m |
| 2026-07-03 | AFL1738 | - | Jul 3, 20:40 UTC | Jul 4, 13:55 UTC | 17h 15m |
| 2026-07-02 | AFL324 | - | Jul 2, 01:20 UTC | Jul 2, 15:10 UTC | 13h 50m |
| 2026-07-01 | AFL324 | - | Jul 1, 12:55 UTC | Jul 2, 11:30 UTC | 22h 35m |
| 2026-06-29 | AFL1731 | - | Jun 29, 20:40 UTC | Jun 30, 13:10 UTC | 16h 31m |
| 2026-06-28 | AFL1009 | - | Jun 28, 01:50 UTC | Jun 28, 03:19 UTC | 1h 30m |
| 2026-06-27 | AFL1072 | - | Jun 27, 22:15 UTC | Jun 27, 22:40 UTC | 25m |
| 2026-06-24 | AFL1745 | - | Jun 24, 08:09 UTC | Jun 24, 08:30 UTC | 20m |
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-73136 page for operator, model, and routing details .