SUSHI 0.00% Over 24 Hours During Market Fluctuations and Lock-Up Contracts
On October 26, 2025, the SUSHI cryptocurrency token ended the day at $0.5325, showing no change over the previous 24 hours. Over the last seven days, SUSHI saw a modest increase of 0.76%. However, the token has dropped 20.38% in the past month and suffered a steep 60.78% decrease over the last year. This price action highlights ongoing volatility, with recent short-term gains failing to compensate for substantial long-term losses. Experts believe SUSHI’s short-term trajectory will largely depend on overall market trends, including global economic factors and prevailing investor attitudes toward cryptocurrencies.
During this period, several significant market events have taken place or are expected, such as the release of various U.S. economic statistics like unemployment figures and wholesale sales reports. Despite this, these events do not have a direct impact on SUSHI’s price, as the cryptocurrency market generally moves independently of traditional economic indicators. Still, worldwide economic conditions can shape investor risk preferences, which may indirectly influence digital assets like
It is also worth noting that lock-up periods for shares of companies such as Nebius Group N.V. and Lucid Diagnostics Inc. are set to conclude on October 26, 2025. These agreements, which began on September 10 and last for 46 days, prevent company insiders from selling or transferring certain shares and options. While these corporate events are not directly connected to SUSHI, they do signal broader market activity and could affect how investors view liquidity and capital movement in the wider financial landscape.
A backtesting method has been suggested to analyze how SUSHI’s price might behave by looking at historical trends. This method involves pinpointing specific event dates and checking if the token has historically fallen by at least 10% within 30 days after such events. However, the backtest faced two technical problems: a bug in the event backtest engine and a division-by-zero error caused by at least one day where the closing price was recorded as zero. These issues prevent the backtest from producing valid results unless the input data is adjusted.
To address this, one approach is to exclude all event dates where SUSHI’s closing price was zero, as well as any 30-day periods that include those dates. This would allow the event-based backtest to run on a cleaned dataset while keeping the original logic intact. Alternatively, a strategy backtest could be used, where trades are initiated on dates when a 10% drop is detected and closed after 30 days. This approach would generate risk and return statistics using the strategy backtest engine, which is better equipped to handle data irregularities. Both methods are feasible: the first maintains the original event-driven analysis, while the second offers more adaptability for assessing real-world performance.
