BIZTRAC BETA
Development of building projects

HEIMRE SKARET AS

Org. no. 925440450 Limited company (AS) Hemsedal Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 11.0m
Operating profit NOK 522,000
Equity NOK 346,000
Incorporated 2020
Share capital NOK 50,000

HEIMRE SKARET AS is registered as a limited company in Hemsedal, Buskerud with organisation number 925440450. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2020. Registered share capital is NOK 50,000, divided into 100 shares. The company's stated purpose is: “Selskapets virksomhet er kjøp og sal av tomter og utvikling av eigedom for tomteformål, samt investering i andre selskap og anna som naturleg faller saman med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 11.0m in revenue and NOK 522,000 in operating profit.

Key figures · 2024

Revenue
NOK 11.0m
Operating profit
NOK 522,000
Equity
NOK 346,000
Est. value
NOK 1.5m

Financial health · 2024

Liquidity
1.04
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
3.6%
Weak
Equity as a share of total capital

Who owns HEIMRE SKARET AS?

HEIMRE SKARET HOLDING AS
HEIMRE SKARET AS
NOK 11.0m rev. · NOK 522,000 profit

HEIMRE SKARET AS has 1 registered shareholder:

All shareholders and roles →

Group structure

HEIMRE SKARET AS er morselskap for 2 datterselskaper:

Frequently asked questions about HEIMRE SKARET AS

Who owns HEIMRE SKARET AS?

HEIMRE SKARET HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of HEIMRE SKARET AS?

HEIMRE SKARET AS had revenue of NOK 11.0m in 2024.

Who is the general manager of HEIMRE SKARET AS?

Olav Holde is registered as general manager of HEIMRE SKARET AS.

Where is HEIMRE SKARET AS based?

HEIMRE SKARET AS has its business address in Hemsedal.

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.