BIZTRAC BETA
Business and other management consultancy activities

STEINSHOLT HOLDING AS

Org. no. 831985062 Limited company (AS) Bærum Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 280,000
Operating profit NOK 226,000
Equity NOK 31,000
Incorporated 2023
Share capital NOK 30,000

STEINSHOLT HOLDING AS is registered as a limited company in Bærum, Akershus with organisation number 831985062. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Bedriftsrådgivning og det som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 280,000 in revenue and NOK 226,000 in operating profit.

Key figures · 2024

Revenue
NOK 280,000
Operating profit
NOK 226,000
Equity
NOK 31,000
Est. value
NOK 707,000

Financial health · 2024

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

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

Who owns STEINSHOLT HOLDING AS?

OLE STEINSHOLT
STEINSHOLT HOLDING AS
NOK 280,000 rev. · NOK 226,000 profit

STEINSHOLT HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does STEINSHOLT HOLDING AS own?

STEINSHOLT HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about STEINSHOLT HOLDING AS

Who owns STEINSHOLT HOLDING AS?

OLE STEINSHOLT is the largest registered owner, with 100.0%.

What is the revenue of STEINSHOLT HOLDING AS?

STEINSHOLT HOLDING AS had revenue of NOK 280,000 in 2024.

Where is STEINSHOLT HOLDING AS based?

STEINSHOLT HOLDING AS has its business address in Jar.

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.