BIZTRAC BETA
Construction of residential and non-residential buildings

JOAR BREKKE AS

Org. no. 997352688 Limited company (AS) Hareid Incorporated 2011 Active
Ownership graph ↗
Revenue 2024 NOK 1.2m
Operating profit NOK 367,000
Equity NOK 1.4m
Incorporated 2011
Share capital NOK 100,000

JOAR BREKKE AS is registered as a limited company in Hareid, Møre og Romsdal with organisation number 997352688. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2011. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Entreprenør- og konsulentvirksomhet innen bygg og anlegg, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.2m in revenue and NOK 367,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.2m
Operating profit
NOK 367,000
Equity
NOK 1.4m
Est. value
NOK 1.9m

Financial health · 2024

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

Who owns JOAR BREKKE AS?

JOAR DIMMEN BREKKE
JOAR BREKKE AS
NOK 1.2m rev. · NOK 367,000 profit

JOAR BREKKE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does JOAR BREKKE AS own?

JOAR BREKKE AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about JOAR BREKKE AS

Who owns JOAR BREKKE AS?

JOAR DIMMEN BREKKE is the largest registered owner, with 100.0%.

What is the revenue of JOAR BREKKE AS?

JOAR BREKKE AS had revenue of NOK 1.2m in 2024.

Where is JOAR BREKKE AS based?

JOAR BREKKE AS has its business address in Hareid.

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.