Back to News
Market Impact: 0.05

Webstep ASA: Financial calendar

Corporate EarningsManagement & GovernanceCompany FundamentalsCorporate Guidance & OutlookTechnology & Innovation

Webstep ASA published its financial calendar detailing reporting and corporate event dates: FY2025 — Quarterly Report Q4 on 12.02.2026 and Annual Report on 23.04.2026; FY2026 — Annual General Meeting on 19.05.2026, Q1 report on 20.05.2026, half-yearly report on 20.08.2026, Q3 report on 17.11.2026 and Q4 report on 18.02.2027. Investor contact is CFO Henning Hesjedal (+47 916 83 601, ir@webstep.com); Webstep is an IT consultancy serving public and private sectors.

Analysis

Market structure: Webstep (OSE:WSTEP) sits in the niche IT consultancy segment where demand for digitalisation and public-sector projects benefits specialist firms while large integrators (e.g., Accenture ACN) may cede tactical projects. Talent scarcity implies upward pressure on bill rates but also margin risk if utilisation falls below ~80%; expect idiosyncratic equity volatility rather than sector-wide dislocation. Cross-asset: negligible direct bond/commodity impact, but NOK and OSEBX option vols could pick up around the February 12, 2026 Q4 release. Risk assessment: Tail risks include loss of a top client (>15–25% revenue), major project overruns, or a data breach that could hit revenue and bookings; these are low-probability but could halve market cap within 6–12 months. Near-term (days/weeks) sensitivity centers on guidance and backlog metrics; medium-term (3–12 months) sensitivity is to utilisation, wage inflation, and public budget cycles. Hidden dependencies: client concentration, subcontractor margins and utilisation smoothing; catalysts are the Feb 12 Q4 report and any large contract announcements before May 20 Q1 update. Trade implications: If liquidity permits, establish a small, event-driven position: consider a 1–2% portfolio long in WSTEP entering 7–14 trading days before Feb 12, 2026 to capture potential positive guidance; hedge market beta with −0.5% exposure to OSEBX futures. If liquid options exist, buy a 30–60 day ATM straddle sized to risk no more than 0.5% portfolio, targeting exit on a >10% price move or 50% of premium decay. If revenue or backlog declines >5% YoY on Feb 12, flip to a short-sized position (0.5–1%) within 3 trading days. Contrarian angles: The market may underprice recurring municipal/public-sector contracts that create multi-quarter revenue visibility—buy if the share falls >15% on noise and backlog remains stable, holding 6–12 months. Conversely, the market may under-appreciate wage-led margin compression; sell/avoid if gross margin falls >200bps QoQ or utilisation <78% for two consecutive quarters. Historical small-Nordic-consultancy patterns show outsized moves ±15–30% around earnings; trade size accordingly and expect quick mean reversion or trend continuation depending on backlog cues.

AllMind AI Terminal

AI-powered research, real-time alerts, and portfolio analytics for institutional investors.

Request a Demo

Market Sentiment

Overall Sentiment

neutral

Sentiment Score

0.00

Key Decisions for Investors

  • Establish a 1–2% long position in Webstep (OSE:WSTEP) 7–14 trading days ahead of the Feb 12, 2026 Q4 report; hedge market risk with a −0.5% notional OSEBX futures position to isolate company-specific upside.
  • If liquid, buy a 30–60 day ATM straddle on WSTEP sized to risk no more than 0.5% of portfolio; plan to exit on a >10% stock move or when 50% of option premium has decayed, and avoid holding through more than one earnings event.
  • Set hard triggers: reduce/close long exposure and consider initiating a 0.5–1% short if Feb 12 results show revenue or backlog down >5% YoY, or if gross margin falls >200bps QoQ; conversely add to longs (to 3% max) if share price drops >15% on noise while backlog/utilisation remain intact.
  • Monitor within 30 days: client concentration (>15% revenue from one client), utilisation rate (critical threshold 78–85%), and any large contract announcements before May 20, 2026; these three metrics should determine scaling the position up or down.