Urgent.News

What's breaking now, across thousands of outlets.

Finance & Markets

Nike Is Down 80% From Its High. Here's the Only Number That Matters.

Disappointing guidance only adds to the bearish sentiment surrounding the stock.

Nike's stock has plummeted 80% from its peak, which was almost five years ago in November 2021. The brand, known for its global recognition, is facing a significant challenge in terms of revenue growth. In the most recent quarter, Nike's top line dropped by 4% compared to the previous year, falling short of analysts' expectations.

Over the past two and a half years, revenue has consistently declined. Nike's largest market, North America, showed a modest 2% increase in sales, while the Greater China market experienced a sharp 22% decline. Despite a slight uptick in performance sales, overall sportswear revenue, which includes popular items like the Air Force 1 and Jordan brand products, has declined.

CEO Elliott Hill acknowledged the company's efforts to reset the market in China, but the outlook remains uncertain. With expectations of a high single-digit revenue decline for fiscal 2027, Nike's profitability could be significantly impacted. Investors should closely monitor the company's upcoming investor day, where they will unveil new long-term financial guidance.

If Nike can turn its fortunes around, its shares may rebound. However, given the inherent risks in turnaround investments, caution is advised.

Written by urgent.news from Motley Fool's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Also reported by 1 other outlet

Read the original at fool.com →

More in Finance & Markets

Our price job put back the stock our stock job had just sold out

On the Friday of a November promotion we sold three hundred and forty cordless drills on a marketplace that we did not have. The listing had said fourteen in stock for most of the afternoon.

  • Company sold 340 cordless drills despite only 14 in stock
  • Price job and stock job conflicted due to lack of synchronization
  • Issue resolved by using ETags and If-Match header for updates

More from Wednesday 14 October →