BIZTRAC BETA
Rental and operating of own or leased real estate

BJØRNSONHUSETS VENNER AS

Org. no. 983624782 Limited company (AS) Molde Incorporated 2001 Active
Ownership graph ↗
Operating profit NOK −61,000
Equity NOK 24.5m
Incorporated 2001
Share capital NOK 24.8m

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−61k kr).

BJØRNSONHUSETS VENNER AS is registered as a limited company in Molde, Møre og Romsdal with organisation number 983624782. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2001. Registered share capital is NOK 24.8m, divided into 24775 shares. The company's stated purpose is: “Investere i bygging av kulturhus påp Reknes i Molde samt alt som står i forbindelse med dette, herunder deltakelse i andre selskaper med samme virksomhet.”.

Key figures · 2024

Operating profit
NOK −61,000
Equity
NOK 24.5m
Est. value
NOK 22.3m

Financial health · 2024

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

Who owns BJØRNSONHUSETS VENNER AS?

SEILET HOTELL EIENDOM AS
BJØRNSONHUSETS VENNER AS
· NOK −61,000 profit

BJØRNSONHUSETS VENNER AS has 19 registered shareholders:

All shareholders and roles →

Which companies does BJØRNSONHUSETS VENNER AS own?

BJØRNSONHUSETS VENNER AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about BJØRNSONHUSETS VENNER AS

Who owns BJØRNSONHUSETS VENNER AS?

SEILET HOTELL EIENDOM AS is the largest registered owner, with 51.0%.

Who is the general manager of BJØRNSONHUSETS VENNER AS?

Ole Hosen is registered as general manager of BJØRNSONHUSETS VENNER AS.

Where is BJØRNSONHUSETS VENNER AS based?

BJØRNSONHUSETS VENNER AS has its business address in Molde.

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.