biztrac. BETA
COMPANY REGISTER PROFILE
917157537 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

HØVIK ØST UTVIKLING AS

Org. no. 917157537 Limited company (AS) Bærum Incorporated 2016 Active
Operating profit NOK −93,000
Equity NOK 1.0m
Incorporated 2016
Share capital NOK 1.0m

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−93k kr).

HØVIK ØST UTVIKLING AS is registered as a limited company in Bærum, Akershus with organisation number 917157537. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2016. Registered share capital is NOK 1.0m, divided into 1000000 shares. The company's stated purpose is: “Investere i fast eiendom eller selskaper som eier fast eiendom, og alt som dermed står i forbindelse.”.

Key figures · 2025

Operating profit
NOK −93,000
▼ −2 %
Equity
NOK 1.0m
▲ +0 %
Est. value
NOK 913,000

Financial health · 2025

Liquidity
5543.28
Very good
Current assets ÷ current liabilities
Profitability
-0.1%
Not satisfactory
Return on total assets
Solidity
1.0%
Not satisfactory
Equity as a share of total capital

Who owns HØVIK ØST UTVIKLING AS?

HØVIK ØST UTVIKLING AS
· NOK −93,000 profit

HØVIK ØST UTVIKLING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does HØVIK ØST UTVIKLING AS own?

HØVIK ØST UTVIKLING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about HØVIK ØST UTVIKLING AS

Who owns HØVIK ØST UTVIKLING AS?

CENTRA HØVIK EIENDOM AS is the largest registered owner, with 100.0%.

Who is the general manager of HØVIK ØST UTVIKLING AS?

Per Christian Johannesen is registered as general manager of HØVIK ØST UTVIKLING AS.

Where is HØVIK ØST UTVIKLING AS based?

HØVIK ØST 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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.