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
- 87
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- 13d 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 20 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| SYL487 | - | 20 | 2026-07-10 |
| SYL736 | Yakutia Airlines | 9 | 2026-06-23 |
| SYL473 | - | 7 | 2026-07-10 |
| SYL476 | Yakutia Airlines | 6 | 2026-06-10 |
| SYL453 | Yakutia Airlines | 6 | 2026-07-22 |
| SYL475 | - | 4 | 2026-06-21 |
| SYL474 | Yakutia Airlines | 4 | 2026-06-15 |
| SYL748 | Yakutia Airlines | 3 | 2026-05-31 |
| SYL479 | - | 3 | 2026-07-18 |
| SYL454 | - | 3 | 2026-07-17 |
| STL479 | - | 3 | 2026-07-24 |
| SYL9997 | Yakutia Airlines | 2 | 2026-05-30 |
| SYL9915 | - | 2 | 2026-06-30 |
| SYL735 | Yakutia Airlines | 2 | 2026-06-01 |
| SYL488 | Yakutia Airlines | 2 | 2026-06-19 |
| SYL468 | Yakutia Airlines | 2 | 2026-07-26 |
| SYL465 | Yakutia Airlines | 2 | 2026-07-23 |
| SYL9986 | Yakutia Airlines | 1 | 2026-05-29 |
| SYL9914 | Yakutia Airlines | 1 | 2026-05-29 |
| SYL794 | Yakutia Airlines | 1 | 2026-05-21 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | SYL468 | LED → SVX | Jul 26, 13:00 UTC | Jul 26, 13:15 UTC | 15m |
| 2026-07-24 | STL479 | - | Jul 24, 03:20 UTC | Jul 24, 18:25 UTC | 15h 5m |
| 2026-07-23 | STL479 | - | Jul 23, 19:20 UTC | Jul 24, 18:25 UTC | 23h 5m |
| 2026-07-23 | STL479 | - | Jul 23, 18:50 UTC | Jul 24, 04:00 UTC | 9h 10m |
| 2026-07-23 | SYL465 | OVB → VKO | Jul 23, 04:25 UTC | Jul 23, 19:20 UTC | 14h 55m |
| 2026-07-22 | SYL465 | OVB → VKO | Jul 22, 19:30 UTC | Jul 23, 04:55 UTC | 9h 25m |
| 2026-07-22 | SYL453 | YKS → OMS | Jul 22, 03:45 UTC | Jul 22, 19:35 UTC | 15h 50m |
| 2026-07-21 | SYL453 | YKS → OMS | Jul 21, 09:20 UTC | Jul 22, 04:25 UTC | 19h 5m |
| 2026-07-21 | SYL453 | YKS → OMS | Jul 21, 09:10 UTC | Jul 22, 04:25 UTC | 19h 15m |
| 2026-07-20 | SYL485 | YKS → OVB | Jul 20, 20:25 UTC | Jul 21, 09:45 UTC | 13h 20m |
| 2026-07-18 | SYL479 | - | Jul 18, 17:00 UTC | Jul 18, 17:30 UTC | 30m |
| 2026-07-17 | SYL454 | - | Jul 17, 19:30 UTC | Jul 18, 17:30 UTC | 22h 1m |
| 2026-07-17 | SYL454 | - | Jul 17, 05:30 UTC | Jul 17, 20:10 UTC | 14h 40m |
| 2026-07-16 | SYL453 | YKS → OMS | Jul 16, 20:19 UTC | Jul 17, 06:05 UTC | 9h 45m |
| 2026-07-10 | SYL473 | - | Jul 10, 15:20 UTC | Jul 11, 04:15 UTC | 12h 55m |
| 2026-07-10 | SYL487 | - | Jul 10, 09:35 UTC | Jul 10, 11:25 UTC | 1h 50m |
| 2026-07-09 | SYL487 | - | Jul 9, 11:20 UTC | Jul 10, 11:15 UTC | 23h 55m |
| 2026-07-09 | SYL487 | - | Jul 9, 09:40 UTC | Jul 9, 12:15 UTC | 2h 35m |
| 2026-07-07 | SYL487 | - | Jul 7, 09:20 UTC | Jul 8, 04:10 UTC | 18h 50m |
| 2026-07-07 | SYL487 | - | Jul 7, 09:05 UTC | Jul 8, 04:10 UTC | 19h 5m |
| 2026-07-06 | SYL487 | - | Jul 6, 21:20 UTC | Jul 7, 16:25 UTC | 19h 5m |
| 2026-07-06 | SYL487 | - | Jul 6, 20:45 UTC | Jul 7, 16:25 UTC | 19h 40m |
| 2026-07-06 | SYL487 | - | Jul 6, 11:45 UTC | Jul 7, 11:00 UTC | 23h 15m |
| 2026-07-06 | SYL473 | - | Jul 6, 04:35 UTC | Jul 6, 21:55 UTC | 17h 20m |
| 2026-07-05 | SYL473 | - | Jul 5, 14:15 UTC | Jul 6, 06:10 UTC | 15h 55m |
| 2026-07-02 | SYL487 | - | Jul 2, 10:20 UTC | Jul 3, 03:35 UTC | 17h 15m |
| 2026-07-01 | SYL487 | - | Jul 1, 19:30 UTC | Jul 2, 11:20 UTC | 15h 50m |
| 2026-07-01 | SYL454 | - | Jul 1, 04:15 UTC | Jul 1, 19:35 UTC | 15h 20m |
| 2026-06-30 | SYL286 | - | Jun 30, 19:40 UTC | Jul 1, 04:20 UTC | 8h 40m |
| 2026-06-30 | SYL9915 | - | Jun 30, 05:55 UTC | Jun 30, 17:50 UTC | 11h 55m |
| 2026-06-30 | SYL285 | - | Jun 30, 03:30 UTC | Jun 30, 04:05 UTC | 35m |
| 2026-06-26 | SYL479 | - | Jun 26, 02:44 UTC | Jun 26, 19:39 UTC | 16h 55m |
| 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 |
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 .