BIZTRAC BETA
Development of building projects

PROFESSOR SMITHS HAGE UTVIKLING AS

Org. no. 988728586 Limited company (AS) Oslo Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 63.5m
Operating profit NOK 9.1m
Equity NOK 55.7m
Incorporated 2005
Share capital NOK 3.3m

PROFESSOR SMITHS HAGE UTVIKLING AS is registered as a limited company in Oslo, Oslo with organisation number 988728586. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2005. Registered share capital is NOK 3.3m, divided into 3000 shares. The company's stated purpose is: “Utvikling, forvaltning og eierskap av fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 63.5m in revenue and NOK 9.1m in operating profit.

Key figures · 2024

Revenue
NOK 63.5m
Operating profit
NOK 9.1m
Equity
NOK 55.7m
Est. value
NOK 55.6m

Financial health · 2024

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

Who owns PROFESSOR SMITHS HAGE UTVIKLING AS?

BANE NOR EIENDOM AS
PROFESSOR SMITHS HAGE UTVIKLING AS
NOK 63.5m rev. · NOK 9.1m profit

PROFESSOR SMITHS HAGE UTVIKLING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PROFESSOR SMITHS HAGE UTVIKLING AS

Who owns PROFESSOR SMITHS HAGE UTVIKLING AS?

BANE NOR EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of PROFESSOR SMITHS HAGE UTVIKLING AS?

PROFESSOR SMITHS HAGE UTVIKLING AS had revenue of NOK 63.5m in 2024.

Who is the general manager of PROFESSOR SMITHS HAGE UTVIKLING AS?

Joakim Bøhn is registered as general manager of PROFESSOR SMITHS HAGE UTVIKLING AS.

Where is PROFESSOR SMITHS HAGE UTVIKLING AS based?

PROFESSOR SMITHS HAGE UTVIKLING AS has its business address in Oslo.

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.