sensors Mode-S transponder
151FB8
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73656 · BOEING 737-800
- Hex
- 151FB8
- Octal
- 05217670
- Decimal
- 1,384,376
- Country
- RU
- Tail
- RA-73656
- Type
- B738
- Flights observed
- 38
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- 7h ago
Last known position
Country allocation
The ICAO 24-bit address 151FB8 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 |
|---|---|---|---|
| AUL531 | Aeroflot-Nord | 4 | 2026-05-14 |
| AUL507 | Aeroflot-Nord | 3 | 2026-05-26 |
| AUL592 | Aeroflot-Nord | 2 | 2026-05-09 |
| AUL546 | Aeroflot-Nord | 2 | 2026-05-28 |
| AUL541 | - | 2 | 2026-05-22 |
| AUL532 | Aeroflot-Nord | 2 | 2026-04-25 |
| AUL513 | Aeroflot-Nord | 2 | 2026-05-24 |
| AUL509 | Aeroflot-Nord | 2 | 2026-05-25 |
| AUL508 | Aeroflot-Nord | 2 | 2026-05-11 |
| AUL504 | - | 2 | 2026-05-29 |
| AUL503 | Aeroflot-Nord | 2 | 2026-05-29 |
| AUL588 | Aeroflot-Nord | 1 | 2026-05-23 |
| AUL586 | Aeroflot-Nord | 1 | 2026-05-11 |
| AUL582 | - | 1 | 2026-04-17 |
| AUL572 | Aeroflot-Nord | 1 | 2026-05-25 |
| AUL545 | Aeroflot-Nord | 1 | 2026-04-29 |
| AUL529 | Aeroflot-Nord | 1 | 2026-05-02 |
| AUL528 | Aeroflot-Nord | 1 | 2026-05-09 |
| AUL511 | Aeroflot-Nord | 1 | 2026-05-24 |
| AUL505 | Aeroflot-Nord | 1 | 2026-05-10 |
Recent flights last 38
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | AUL504 | - | May 29, 20:50 UTC | May 29, 21:35 UTC | 45m |
| 2026-05-29 | AUL503 | LED → SCW | May 29, 17:50 UTC | May 29, 18:10 UTC | 20m |
| 2026-05-28 | AUL546 | AER → LED | May 28, 11:35 UTC | May 28, 12:15 UTC | 40m |
| 2026-05-26 | AUL151 | ARH → LED | May 26, 16:30 UTC | May 26, 16:59 UTC | 30m |
| 2026-05-26 | AUL507 | LED → MMK | May 26, 07:15 UTC | May 26, 13:00 UTC | 5h 45m |
| 2026-05-25 | AUL509 | LED → GOJ | May 25, 07:20 UTC | May 25, 21:49 UTC | 14h 29m |
| 2026-05-25 | AUL572 | OVB → LED | May 25, 04:00 UTC | May 25, 04:15 UTC | 15m |
| 2026-05-24 | AUL513 | LED → KGD | May 24, 12:50 UTC | May 24, 14:00 UTC | 1h 10m |
| 2026-05-24 | AUL511 | LED → VOG | May 24, 06:00 UTC | May 24, 07:05 UTC | 1h 5m |
| 2026-05-23 | AUL509 | LED → GOJ | May 23, 13:20 UTC | May 23, 13:45 UTC | 25m |
| 2026-05-23 | AUL588 | REN → LED | May 23, 03:30 UTC | May 23, 09:55 UTC | 6h 25m |
| 2026-05-22 | AUL541 | LED → LED | May 22, 12:35 UTC | May 22, 13:10 UTC | 35m |
| 2026-05-22 | AUL507 | LED → MMK | May 22, 07:10 UTC | May 22, 10:35 UTC | 3h 25m |
| 2026-05-14 | AUL531 | LED → KUF | May 14, 07:55 UTC | May 14, 09:00 UTC | 1h 5m |
| 2026-05-13 | AUL531 | LED → KUF | May 13, 13:10 UTC | May 14, 09:00 UTC | 19h 50m |
| 2026-05-11 | AUL508 | MMK → LED | May 11, 17:30 UTC | May 12, 11:10 UTC | 17h 40m |
| 2026-05-11 | AUL508 | MMK → LED | May 11, 12:45 UTC | May 12, 11:10 UTC | 22h 26m |
| 2026-05-11 | AUL586 | KRR → LED | May 11, 08:50 UTC | May 12, 08:00 UTC | 23h 11m |
| 2026-05-10 | AUL513 | LED → KGD | May 10, 11:40 UTC | May 10, 12:40 UTC | 1h 0m |
| 2026-05-10 | AUL505 | SVO → SCW | May 10, 07:15 UTC | May 10, 07:25 UTC | 10m |
| 2026-05-09 | AUL592 | UFA → LED | May 9, 13:45 UTC | May 10, 03:10 UTC | 13h 25m |
| 2026-05-09 | AUL528 | CEK → LED | May 9, 07:05 UTC | May 10, 03:10 UTC | 20h 5m |
| 2026-05-08 | AUL147 | ARH → LED | May 8, 13:25 UTC | May 8, 13:45 UTC | 20m |
| 2026-05-08 | AUL148 | LED → ARH | May 8, 10:59 UTC | May 8, 11:30 UTC | 30m |
| 2026-05-06 | AUL592 | UFA → LED | May 6, 02:30 UTC | May 6, 03:10 UTC | 40m |
| 2026-05-02 | AUL529 | MMK → MMK | May 2, 18:05 UTC | May 2, 22:30 UTC | 4h 25m |
| 2026-04-29 | AUL546 | AER → LED | Apr 29, 16:05 UTC | Apr 29, 16:15 UTC | 10m |
| 2026-04-29 | AUL545 | LED → AER | Apr 29, 07:24 UTC | Apr 29, 13:50 UTC | 6h 26m |
| 2026-04-28 | AUL507 | LED → MMK | Apr 28, 07:15 UTC | Apr 28, 11:40 UTC | 4h 25m |
| 2026-04-26 | AUL504 | - | Apr 26, 20:35 UTC | Apr 26, 21:20 UTC | 45m |
| 2026-04-26 | AUL503 | LED → SCW | Apr 26, 19:10 UTC | Apr 26, 19:25 UTC | 15m |
| 2026-04-25 | AUL532 | KUF → LED | Apr 25, 09:45 UTC | Apr 25, 09:55 UTC | 10m |
| 2026-04-24 | AUL541 | LED → LED | Apr 24, 12:25 UTC | Apr 24, 13:25 UTC | 1h 0m |
| 2026-04-20 | AUL531 | LED → KUF | Apr 20, 06:35 UTC | Apr 20, 06:55 UTC | 20m |
| 2026-04-17 | AUL582 | - | Apr 17, 15:45 UTC | Apr 17, 16:05 UTC | 20m |
| 2026-04-15 | AUL502 | SCW → SVO | Apr 15, 02:55 UTC | Apr 15, 03:35 UTC | 40m |
| 2026-04-14 | AUL532 | KUF → LED | Apr 14, 10:10 UTC | Apr 14, 10:20 UTC | 10m |
| 2026-04-14 | AUL531 | LED → KUF | Apr 14, 08:10 UTC | Apr 14, 08:25 UTC | 15m |
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-73656 page for operator, model, and routing details .