BIZTRAC BETA
Buying and selling of own real estate

STILLERUD UTVIKLING AS

Org. no. 920049451 Limited company (AS) Holmestrand Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 7.5m
Operating profit NOK 2.4m
Equity NOK 416,000
Incorporated 2017
Share capital NOK 90,000

STILLERUD UTVIKLING AS is registered as a limited company in Holmestrand, Vestfold with organisation number 920049451. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2017. Registered share capital is NOK 90,000, divided into 30000 shares. The company's stated purpose is: “Inngå avtaler om tomtearealer, selge Mesterhus på egne og andres tomter og derigjennom tilføre aksjonærene byggeoppdrag.”. The most recent filed accounts, for the 2025 financial year, show NOK 7.5m in revenue and NOK 2.4m in operating profit.

Key figures · 2025

Revenue
NOK 7.5m
Operating profit
NOK 2.4m
Equity
NOK 416,000
Est. value
NOK 4.5m

Financial health · 2025

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

Who owns STILLERUD UTVIKLING AS?

SANDVIN EIENDOM AS
STILLERUD UTVIKLING AS
NOK 7.5m rev. · NOK 2.4m profit

STILLERUD UTVIKLING AS has 6 registered shareholders:

All shareholders and roles →

Frequently asked questions about STILLERUD UTVIKLING AS

Who owns STILLERUD UTVIKLING AS?

SANDVIN EIENDOM AS is the largest registered owner, with 25.0%.

What is the revenue of STILLERUD UTVIKLING AS?

STILLERUD UTVIKLING AS had revenue of NOK 7.5m in 2025.

Who is the general manager of STILLERUD UTVIKLING AS?

Ole Kristian Svendsøy Lofsberg is registered as general manager of STILLERUD UTVIKLING AS.

Where is STILLERUD UTVIKLING AS based?

STILLERUD UTVIKLING AS has its business address in Sande I Vestfold.

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.