sensors Mode-S transponder
151E2D
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73261 · BOEING 737-800
- Hex
- 151E2D
- Octal
- 05217055
- Decimal
- 1,383,981
- Country
- RU
- Tail
- RA-73261
- Type
- B738
- Flights observed
- 55
- Distinct callsigns
- 18
- Country
- RU
- Last broadcast
- 13h ago
Last known position
Country allocation
The ICAO 24-bit address 151E2D 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 18 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| SYL487 | - | 10 | 2026-06-19 |
| SYL736 | Yakutia Airlines | 9 | 2026-06-23 |
| SYL476 | Yakutia Airlines | 6 | 2026-06-10 |
| SYL475 | - | 4 | 2026-06-21 |
| SYL474 | Yakutia Airlines | 4 | 2026-06-15 |
| SYL473 | Yakutia Airlines | 4 | 2026-06-15 |
| SYL748 | Yakutia Airlines | 3 | 2026-05-31 |
| SYL9997 | Yakutia Airlines | 2 | 2026-05-30 |
| SYL735 | Yakutia Airlines | 2 | 2026-06-01 |
| SYL488 | Yakutia Airlines | 2 | 2026-06-19 |
| SYL453 | - | 2 | 2026-06-24 |
| SYL9986 | Yakutia Airlines | 1 | 2026-05-29 |
| SYL9915 | - | 1 | 2026-06-18 |
| SYL9914 | Yakutia Airlines | 1 | 2026-05-29 |
| SYL794 | Yakutia Airlines | 1 | 2026-05-21 |
| SYL793 | Yakutia Airlines | 1 | 2026-06-04 |
| SYL479 | Yakutia Airlines | 1 | 2026-05-15 |
| SYL468 | Yakutia Airlines | 1 | 2026-06-14 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-24 | SYL453 | - | Jun 24, 03:44 UTC | Jun 24, 19:39 UTC | 15h 55m |
| 2026-06-23 | SYL453 | - | Jun 23, 16:54 UTC | Jun 24, 10:04 UTC | 17h 10m |
| 2026-06-23 | SYL736 | YKS → VKO | Jun 23, 14:44 UTC | Jun 23, 15:04 UTC | 20m |
| 2026-06-23 | SYL736 | YKS → VKO | Jun 23, 12:29 UTC | Jun 23, 13:59 UTC | 1h 30m |
| 2026-06-22 | SYL736 | YKS → VKO | Jun 22, 14:14 UTC | Jun 23, 13:09 UTC | 22h 55m |
| 2026-06-21 | SYL475 | - | Jun 21, 05:59 UTC | Jun 21, 06:29 UTC | 30m |
| 2026-06-19 | SYL488 | LED → YKS | Jun 19, 16:29 UTC | Jun 20, 12:04 UTC | 19h 35m |
| 2026-06-19 | SYL487 | - | Jun 19, 03:15 UTC | Jun 19, 14:04 UTC | 10h 50m |
| 2026-06-18 | SYL9915 | - | Jun 18, 11:00 UTC | Jun 19, 01:10 UTC | 14h 9m |
| 2026-06-16 | SYL475 | - | Jun 16, 15:35 UTC | Jun 17, 04:15 UTC | 12h 41m |
| 2026-06-16 | SYL475 | - | Jun 16, 08:25 UTC | Jun 17, 04:15 UTC | 19h 51m |
| 2026-06-15 | SYL487 | YKS → LED | Jun 15, 18:45 UTC | Jun 16, 15:55 UTC | 21h 10m |
| 2026-06-15 | SYL474 | AER → VKO | Jun 15, 13:34 UTC | Jun 16, 08:55 UTC | 19h 20m |
| 2026-06-15 | SYL474 | AER → VKO | Jun 15, 07:40 UTC | Jun 15, 19:10 UTC | 11h 30m |
| 2026-06-15 | SYL473 | VKO → AER | Jun 15, 03:35 UTC | Jun 15, 05:00 UTC | 1h 25m |
| 2026-06-14 | SYL468 | LED → SVX | Jun 14, 13:00 UTC | Jun 14, 13:10 UTC | 10m |
| 2026-06-13 | SYL474 | AER → VKO | Jun 13, 17:25 UTC | Jun 13, 19:35 UTC | 2h 10m |
| 2026-06-12 | SYL488 | LED → YKS | Jun 12, 10:25 UTC | Jun 13, 04:30 UTC | 18h 4m |
| 2026-06-10 | SYL476 | VKO → YKS | Jun 10, 13:55 UTC | Jun 10, 14:20 UTC | 25m |
| 2026-06-09 | SYL487 | YKS → LED | Jun 9, 09:20 UTC | Jun 10, 05:10 UTC | 19h 50m |
| 2026-06-09 | SYL487 | YKS → LED | Jun 9, 09:10 UTC | Jun 10, 05:10 UTC | 20h 0m |
| 2026-06-08 | SYL487 | YKS → LED | Jun 8, 18:55 UTC | Jun 9, 10:45 UTC | 15h 50m |
| 2026-06-08 | SYL473 | VKO → AER | Jun 8, 07:05 UTC | Jun 8, 19:10 UTC | 12h 5m |
| 2026-06-07 | SYL476 | VKO → YKS | Jun 7, 14:50 UTC | Jun 8, 04:10 UTC | 13h 20m |
| 2026-06-07 | SYL476 | VKO → YKS | Jun 7, 03:45 UTC | Jun 8, 03:15 UTC | 23h 30m |
| 2026-06-07 | SYL476 | VKO → YKS | Jun 7, 02:50 UTC | Jun 7, 16:15 UTC | 13h 25m |
| 2026-06-04 | SYL793 | VKO → UFA | Jun 4, 03:30 UTC | Jun 4, 04:35 UTC | 1h 5m |
| 2026-06-02 | SYL736 | YKS → VKO | Jun 2, 12:00 UTC | Jun 2, 12:35 UTC | 35m |
| 2026-06-01 | SYL736 | YKS → VKO | Jun 1, 15:20 UTC | Jun 2, 12:35 UTC | 21h 15m |
| 2026-06-01 | SYL735 | VKO → YKS | Jun 1, 14:15 UTC | Jun 2, 12:35 UTC | 22h 20m |
| 2026-06-01 | SYL735 | VKO → YKS | Jun 1, 01:15 UTC | Jun 1, 15:35 UTC | 14h 20m |
| 2026-05-31 | SYL748 | KJA → VKO | May 31, 12:55 UTC | Jun 1, 06:30 UTC | 17h 35m |
| 2026-05-31 | SYL748 | KJA → VKO | May 31, 10:10 UTC | Jun 1, 06:30 UTC | 20h 20m |
| 2026-05-30 | SYL748 | KJA → VKO | May 30, 19:30 UTC | May 31, 13:30 UTC | 18h 0m |
| 2026-05-30 | SYL9997 | VKO → KJA | May 30, 05:10 UTC | May 30, 22:10 UTC | 17h 0m |
| 2026-05-30 | SYL9997 | VKO → KJA | May 30, 00:00 UTC | May 30, 22:10 UTC | 22h 10m |
| 2026-05-29 | SYL9914 | UUD → SVX | May 29, 11:45 UTC | May 30, 05:50 UTC | 18h 5m |
| 2026-05-29 | SYL9986 | SBT → KUF | May 29, 06:05 UTC | May 30, 05:15 UTC | 23h 10m |
| 2026-05-28 | SYL736 | YKS → VKO | May 28, 12:00 UTC | May 28, 14:25 UTC | 2h 25m |
| 2026-05-26 | SYL475 | YKS → VKO | May 26, 13:40 UTC | May 27, 04:14 UTC | 14h 35m |
| 2026-05-25 | SYL487 | YKS → LED | May 25, 18:30 UTC | May 26, 09:49 UTC | 15h 20m |
| 2026-05-22 | SYL473 | VKO → AER | May 22, 14:45 UTC | May 23, 03:20 UTC | 12h 34m |
| 2026-05-22 | SYL487 | YKS → LED | May 22, 11:25 UTC | May 22, 12:25 UTC | 1h 0m |
| 2026-05-21 | SYL794 | UFA → VKO | May 21, 15:45 UTC | May 21, 20:00 UTC | 4h 15m |
| 2026-05-19 | SYL476 | VKO → YKS | May 19, 17:30 UTC | May 20, 12:45 UTC | 19h 16m |
| 2026-05-19 | SYL476 | VKO → YKS | May 19, 12:10 UTC | May 20, 10:20 UTC | 22h 11m |
| 2026-05-15 | SYL479 | VKO → MRV | May 15, 02:45 UTC | May 15, 03:15 UTC | 30m |
| 2026-05-12 | SYL736 | YKS → VKO | May 12, 12:00 UTC | May 12, 18:45 UTC | 6h 45m |
| 2026-05-11 | SYL736 | YKS → VKO | May 11, 15:20 UTC | May 12, 13:25 UTC | 22h 6m |
| 2026-05-11 | SYL736 | YKS → VKO | May 11, 15:00 UTC | May 12, 13:15 UTC | 22h 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-73261 page for operator, model, and routing details .