BIZTRAC BETA
Rental and operating of own or leased real estate

KÅRE BJORØY HOLDING AS

Org. no. 989122657 Limited company (AS) Øygarden Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 33,000
Operating profit NOK −40,000
Equity NOK 332.0m
Incorporated 2005
Share capital NOK 2.9m

Signals

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

KÅRE BJORØY HOLDING AS is registered as a limited company in Øygarden, Vestland with organisation number 989122657. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2005. Registered share capital is NOK 2.9m, divided into 2900 shares. The company's stated purpose is: “Investere i finans- og realobjekter.”. The most recent filed accounts, for the 2024 financial year, show NOK 33,000 in revenue and NOK −40,000 in operating profit.

Key figures · 2024

Revenue
NOK 33,000
Operating profit
NOK −40,000
Equity
NOK 332.0m
Est. value
NOK 543.8m

Financial health · 2024

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

Who owns KÅRE BJORØY HOLDING AS?

KÅRE BJORØY
KÅRE BJORØY HOLDING AS
NOK 33,000 rev. · NOK −40,000 profit

KÅRE BJORØY HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KÅRE BJORØY HOLDING AS own?

KÅRE BJORØY HOLDING AS holds stakes in 9 companies:

See the full ownership structure →

Frequently asked questions about KÅRE BJORØY HOLDING AS

Who owns KÅRE BJORØY HOLDING AS?

KÅRE BJORØY is the largest registered owner, with 100.0%.

What is the revenue of KÅRE BJORØY HOLDING AS?

KÅRE BJORØY HOLDING AS had revenue of NOK 33,000 in 2024.

Where is KÅRE BJORØY HOLDING AS based?

KÅRE BJORØY HOLDING AS has its business address in Straume.

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.