BIZTRAC BETA
Rental and operating of own or leased real estate

BYGGVERKET HALLINGDAL AS

Org. no. 978600352 Limited company (AS) Ål Incorporated 1997 Active
Ownership graph ↗
Revenue 2025 NOK 667,000
Operating profit NOK 95,000
Equity NOK 1.3m
Incorporated 1997
Share capital NOK 100,000

BYGGVERKET HALLINGDAL AS is registered as a limited company in Ål, Buskerud with organisation number 978600352. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1997. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Kjøp, drift, utleie og salg av fast eiendom. Utleie av driftsmidler. Annen næringsvirksomhet naturlig relatert til ovenstående.”. The most recent filed accounts, for the 2025 financial year, show NOK 667,000 in revenue and NOK 95,000 in operating profit.

Key figures · 2025

Revenue
NOK 667,000
Operating profit
NOK 95,000
Equity
NOK 1.3m
Est. value
NOK 1.2m

Financial health · 2025

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

Who owns BYGGVERKET HALLINGDAL AS?

SLÅTTO HOLDING AS
BYGGVERKET HALLINGDAL AS
NOK 667,000 rev. · NOK 95,000 profit

BYGGVERKET HALLINGDAL AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BYGGVERKET HALLINGDAL AS

Who owns BYGGVERKET HALLINGDAL AS?

SLÅTTO HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of BYGGVERKET HALLINGDAL AS?

BYGGVERKET HALLINGDAL AS had revenue of NOK 667,000 in 2025.

Who is the general manager of BYGGVERKET HALLINGDAL AS?

Morgan Slåtto is registered as general manager of BYGGVERKET HALLINGDAL AS.

Where is BYGGVERKET HALLINGDAL AS based?

BYGGVERKET HALLINGDAL AS has its business address in Ål.

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.