sensors Mode-S transponder
151E2E
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73262 · BOEING 737-700
- Hex
- 151E2E
- Octal
- 05217056
- Decimal
- 1,383,982
- Country
- RU
- Tail
- RA-73262
- Type
- B737
- Flights observed
- 77
- Distinct callsigns
- 12
- Country
- RU
- Last broadcast
- 2h ago
Last known position
Country allocation
The ICAO 24-bit address 151E2E 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 12 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| SYL487 | Yakutia Airlines | 16 | 2026-05-29 |
| SYL475 | Yakutia Airlines | 10 | 2026-05-24 |
| SYL465 | Yakutia Airlines | 10 | 2026-05-28 |
| SYL479 | Yakutia Airlines | 9 | 2026-05-26 |
| SYL473 | Yakutia Airlines | 8 | 2026-05-18 |
| SYL476 | Yakutia Airlines | 6 | 2026-05-24 |
| SYL467 | Yakutia Airlines | 5 | 2026-05-17 |
| SYL474 | Yakutia Airlines | 3 | 2026-05-16 |
| SYL468 | Yakutia Airlines | 3 | 2026-05-17 |
| SYL466 | Yakutia Airlines | 3 | 2026-04-23 |
| SYL488 | - | 2 | 2026-04-17 |
| SYL480 | Yakutia Airlines | 2 | 2026-04-22 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | SYL487 | YKS → LED | May 29, 10:25 UTC | May 30, 03:05 UTC | 16h 40m |
| 2026-05-28 | SYL487 | YKS → LED | May 28, 19:35 UTC | May 29, 11:55 UTC | 16h 20m |
| 2026-05-28 | SYL487 | YKS → LED | May 28, 17:15 UTC | May 29, 11:55 UTC | 18h 40m |
| 2026-05-28 | SYL465 | OVB → VKO | May 28, 01:45 UTC | May 28, 02:25 UTC | 40m |
| 2026-05-26 | SYL479 | VKO → MRV | May 26, 02:49 UTC | May 26, 03:19 UTC | 30m |
| 2026-05-24 | SYL476 | VKO → YKS | May 24, 16:50 UTC | May 24, 17:10 UTC | 20m |
| 2026-05-24 | SYL475 | YKS → VKO | May 24, 02:35 UTC | May 24, 09:40 UTC | 7h 5m |
| 2026-05-21 | SYL479 | VKO → MRV | May 21, 18:20 UTC | May 22, 04:15 UTC | 9h 55m |
| 2026-05-21 | SYL465 | OVB → VKO | May 21, 07:15 UTC | May 21, 14:25 UTC | 7h 10m |
| 2026-05-21 | SYL465 | OVB → VKO | May 21, 04:45 UTC | May 21, 05:25 UTC | 40m |
| 2026-05-20 | SYL465 | OVB → VKO | May 20, 06:00 UTC | May 21, 05:25 UTC | 23h 25m |
| 2026-05-19 | SYL475 | YKS → VKO | May 19, 19:00 UTC | May 20, 06:35 UTC | 11h 36m |
| 2026-05-19 | SYL487 | YKS → LED | May 19, 09:35 UTC | May 20, 06:35 UTC | 21h 1m |
| 2026-05-19 | SYL487 | YKS → LED | May 19, 09:25 UTC | May 20, 06:35 UTC | 21h 11m |
| 2026-05-18 | SYL473 | VKO → AER | May 18, 10:10 UTC | May 18, 10:30 UTC | 20m |
| 2026-05-17 | SYL473 | VKO → AER | May 17, 15:20 UTC | May 18, 06:20 UTC | 15h 0m |
| 2026-05-17 | SYL468 | LED → SVX | May 17, 13:50 UTC | May 17, 14:05 UTC | 15m |
| 2026-05-17 | SYL467 | SVX → LED | May 17, 10:40 UTC | May 17, 10:50 UTC | 10m |
| 2026-05-16 | SYL474 | AER → VKO | May 16, 20:00 UTC | May 16, 20:25 UTC | 25m |
| 2026-05-16 | SYL474 | AER → VKO | May 16, 17:01 UTC | May 16, 17:30 UTC | 30m |
| 2026-05-16 | SYL473 | VKO → AER | May 16, 02:50 UTC | May 16, 03:25 UTC | 35m |
| 2026-05-15 | SYL487 | YKS → LED | May 15, 10:30 UTC | May 15, 12:10 UTC | 1h 40m |
| 2026-05-14 | SYL487 | YKS → LED | May 14, 15:40 UTC | May 15, 12:10 UTC | 20h 30m |
| 2026-05-14 | SYL465 | OVB → VKO | May 14, 01:40 UTC | May 14, 16:00 UTC | 14h 20m |
| 2026-05-13 | SYL476 | VKO → YKS | May 13, 15:00 UTC | May 14, 02:10 UTC | 11h 10m |
| 2026-05-13 | SYL476 | VKO → YKS | May 13, 03:55 UTC | May 14, 02:10 UTC | 22h 15m |
| 2026-05-13 | SYL475 | YKS → VKO | May 13, 02:55 UTC | May 13, 16:15 UTC | 13h 20m |
| 2026-05-12 | SYL475 | YKS → VKO | May 12, 14:00 UTC | May 13, 04:30 UTC | 14h 30m |
| 2026-05-12 | SYL487 | YKS → LED | May 12, 09:10 UTC | May 12, 10:15 UTC | 1h 5m |
| 2026-05-11 | SYL487 | YKS → LED | May 11, 09:40 UTC | May 12, 09:30 UTC | 23h 51m |
| 2026-05-09 | SYL475 | YKS → VKO | May 9, 23:44 UTC | May 10, 00:20 UTC | 35m |
| 2026-05-08 | SYL465 | OVB → VKO | May 8, 13:25 UTC | May 8, 16:20 UTC | 2h 55m |
| 2026-05-08 | SYL476 | VKO → YKS | May 8, 00:20 UTC | May 8, 10:54 UTC | 10h 35m |
| 2026-05-06 | SYL475 | YKS → VKO | May 6, 06:50 UTC | May 6, 20:25 UTC | 13h 34m |
| 2026-05-05 | SYL479 | VKO → MRV | May 5, 03:35 UTC | May 5, 04:30 UTC | 55m |
| 2026-05-03 | SYL468 | LED → SVX | May 3, 12:40 UTC | May 3, 12:55 UTC | 15m |
| 2026-05-02 | SYL474 | AER → VKO | May 2, 18:55 UTC | May 2, 19:30 UTC | 35m |
| 2026-05-01 | SYL473 | VKO → AER | May 1, 15:40 UTC | May 2, 10:30 UTC | 18h 50m |
| 2026-05-01 | SYL473 | VKO → AER | May 1, 10:25 UTC | May 2, 04:20 UTC | 17h 55m |
| 2026-04-30 | SYL465 | OVB → VKO | Apr 30, 04:00 UTC | Apr 30, 09:25 UTC | 5h 25m |
| 2026-04-28 | SYL479 | VKO → MRV | Apr 28, 13:45 UTC | Apr 29, 04:20 UTC | 14h 35m |
| 2026-04-27 | SYL476 | VKO → YKS | Apr 27, 18:40 UTC | Apr 28, 09:40 UTC | 15h 0m |
| 2026-04-27 | SYL475 | YKS → VKO | Apr 27, 03:10 UTC | Apr 27, 19:00 UTC | 15h 50m |
| 2026-04-26 | SYL467 | SVX → LED | Apr 26, 08:00 UTC | Apr 26, 15:05 UTC | 7h 5m |
| 2026-04-25 | SYL467 | SVX → LED | Apr 25, 18:10 UTC | Apr 26, 15:05 UTC | 20h 55m |
| 2026-04-25 | SYL473 | VKO → AER | Apr 25, 02:50 UTC | Apr 25, 18:40 UTC | 15h 50m |
| 2026-04-24 | SYL487 | YKS → LED | Apr 24, 09:35 UTC | Apr 25, 04:20 UTC | 18h 45m |
| 2026-04-23 | SYL487 | YKS → LED | Apr 23, 18:05 UTC | Apr 24, 15:40 UTC | 21h 35m |
| 2026-04-23 | SYL466 | VKO → OVB | Apr 23, 06:30 UTC | Apr 23, 14:50 UTC | 8h 20m |
| 2026-04-22 | SYL480 | MRV → VKO | Apr 22, 16:10 UTC | Apr 23, 04:15 UTC | 12h 5m |
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-73262 page for operator, model, and routing details .