BIZTRAC BETA
Development of building projects

PROFESSOR KOHTS VEI UTVIKLING AS

Org. no. 919457597 Limited company (AS) Bærum Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 385.3m
Operating profit NOK 62.8m
Equity NOK 202.6m
Incorporated 2017
Share capital NOK 369,000

PROFESSOR KOHTS VEI UTVIKLING AS is registered as a limited company in Bærum, Akershus with organisation number 919457597. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2017. Registered share capital is NOK 369,000, divided into 2000 shares. The company's stated purpose is: “Investere i, herunder erverv, salg, utvikling og utbygging av fast eiendom eller selskaper som eier fast eiendom og alt som hermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 385.3m in revenue and NOK 62.8m in operating profit.

Key figures · 2024

Revenue
NOK 385.3m
Operating profit
NOK 62.8m
Equity
NOK 202.6m
Est. value
NOK 290.3m

Financial health · 2024

Liquidity
1.52
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
20.8%
Good
Equity as a share of total capital

Who owns PROFESSOR KOHTS VEI UTVIKLING AS?

BERTEL O. STEEN EIENDOMSUTVIKLING AS
PROFESSOR KOHTS VEI UTVIKLING AS
NOK 385.3m rev. · NOK 62.8m profit

PROFESSOR KOHTS VEI UTVIKLING AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about PROFESSOR KOHTS VEI UTVIKLING AS

Who owns PROFESSOR KOHTS VEI UTVIKLING AS?

BERTEL O. STEEN EIENDOMSUTVIKLING AS is the largest registered owner, with 40.9%.

What is the revenue of PROFESSOR KOHTS VEI UTVIKLING AS?

PROFESSOR KOHTS VEI UTVIKLING AS had revenue of NOK 385.3m in 2024.

Where is PROFESSOR KOHTS VEI UTVIKLING AS based?

PROFESSOR KOHTS VEI UTVIKLING AS has its business address in Lysaker.

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.