BIZTRAC BETA
Other technical consultancy

STOKNES NEXT AS

Org. no. 922162387 Limited company (AS) Bærum Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 1.3m
Operating profit NOK 36,000
Equity NOK 4.0m
Incorporated 2019
Share capital NOK 30,000

STOKNES NEXT AS is registered as a limited company in Bærum, Akershus with organisation number 922162387. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Konsulentvirksomhet innen olje og gass, grundervirksomhet, samt andre produkter/tjenester som naturlig hører sammen med dette, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.3m in revenue and NOK 36,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.3m
Operating profit
NOK 36,000
Equity
NOK 4.0m
Est. value
NOK 2.7m

Financial health · 2025

Liquidity
9.88
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
92.5%
Very good
Equity as a share of total capital

Who owns STOKNES NEXT AS?

ANNE KRISTIN STOKNES
STOKNES NEXT AS
NOK 1.3m rev. · NOK 36,000 profit

STOKNES NEXT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STOKNES NEXT AS

Who owns STOKNES NEXT AS?

ANNE KRISTIN STOKNES is the largest registered owner, with 100.0%.

What is the revenue of STOKNES NEXT AS?

STOKNES NEXT AS had revenue of NOK 1.3m in 2025.

Who is the general manager of STOKNES NEXT AS?

Anne Kristin Stoknes is registered as general manager of STOKNES NEXT AS.

Where is STOKNES NEXT AS based?

STOKNES NEXT AS has its business address in Rykkinn.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.