BIZTRAC BETA
Development of building projects

ULVEN OG STRANDE AS

Org. no. 926514814 Limited company (AS) Ringerike Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 1.7m
Operating profit NOK 77,000
Equity NOK 793,000
Incorporated 2021
Share capital NOK 30,000

ULVEN OG STRANDE AS is registered as a limited company in Ringerike, Buskerud with organisation number 926514814. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Kjøp, salg og utvikling av fast eiendom samt det som naturlig faller inn under dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.7m in revenue and NOK 77,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.7m
Operating profit
NOK 77,000
Equity
NOK 793,000
Est. value
NOK 782,000

Financial health · 2024

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

Who owns ULVEN OG STRANDE AS?

LARS ULVEN ROLID
ULVEN OG STRANDE AS
NOK 1.7m rev. · NOK 77,000 profit

ULVEN OG STRANDE AS has 2 registered shareholders:

All shareholders and roles →

Which companies does ULVEN OG STRANDE AS own?

ULVEN OG STRANDE AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ULVEN OG STRANDE AS

Who owns ULVEN OG STRANDE AS?

LARS ULVEN ROLID is the largest registered owner, with 50.0%.

What is the revenue of ULVEN OG STRANDE AS?

ULVEN OG STRANDE AS had revenue of NOK 1.7m in 2024.

Who is the general manager of ULVEN OG STRANDE AS?

Lars Ulven Rolid is registered as general manager of ULVEN OG STRANDE AS.

Where is ULVEN OG STRANDE AS based?

ULVEN OG STRANDE AS has its business address in Hønefoss.

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.