BIZTRAC BETA
Preventive health care activities

STOLTEN CONSULTING AS

Org. no. 917533172 Limited company (AS) Vestby Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 3.0m
Operating profit NOK 179,000
Equity NOK 45,000
Incorporated 2016
Share capital NOK 30,000

STOLTEN CONSULTING AS is registered as a limited company in Vestby, Akershus with organisation number 917533172. The business is classified under preventive health care activities (NACE 86.992). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Konsulentvirksomhet innen HMS med hertil hørende virksomhet, samt all annen virksomhet med økonomisk vinning som formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.0m in revenue and NOK 179,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.0m
Operating profit
NOK 179,000
Equity
NOK 45,000
Est. value
NOK 851,000

Financial health · 2024

Liquidity
1.07
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
6.5%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns STOLTEN CONSULTING AS?

CATO STOLTENBERG
STOLTEN CONSULTING AS
NOK 3.0m rev. · NOK 179,000 profit

STOLTEN CONSULTING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STOLTEN CONSULTING AS

Who owns STOLTEN CONSULTING AS?

CATO STOLTENBERG is the largest registered owner, with 100.0%.

What is the revenue of STOLTEN CONSULTING AS?

STOLTEN CONSULTING AS had revenue of NOK 3.0m in 2024.

Who is the general manager of STOLTEN CONSULTING AS?

Cato Stoltenberg is registered as general manager of STOLTEN CONSULTING AS.

Where is STOLTEN CONSULTING AS based?

STOLTEN CONSULTING AS has its business address in Son.

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.