BIZTRAC BETA
Site preparation

GULLHAGEN ANLEGGSDRIFT AS

Org. no. 988415472 Limited company (AS) Ål Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 3.0m
Operating profit NOK 559,000
Equity NOK 4.1m
Incorporated 2005
Share capital NOK 299,000

GULLHAGEN ANLEGGSDRIFT AS is registered as a limited company in Ål, Buskerud with organisation number 988415472. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2005. Registered share capital is NOK 299,000, divided into 100 shares. The company's stated purpose is: “Generell anleggsdrift herunder oppdrag med graving og sprengning, samt deltakelse i andre selskaper med liknende virksomhet ved aksjetegning eller på annen måte.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.0m in revenue and NOK 559,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.0m
Operating profit
NOK 559,000
Equity
NOK 4.1m
Est. value
NOK 3.6m

Financial health · 2025

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

Who owns GULLHAGEN ANLEGGSDRIFT AS?

ARNE OLAV GULLHAGEN
GULLHAGEN ANLEGGSDRIFT AS
NOK 3.0m rev. · NOK 559,000 profit

GULLHAGEN ANLEGGSDRIFT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GULLHAGEN ANLEGGSDRIFT AS

Who owns GULLHAGEN ANLEGGSDRIFT AS?

ARNE OLAV GULLHAGEN is the largest registered owner, with 100.0%.

What is the revenue of GULLHAGEN ANLEGGSDRIFT AS?

GULLHAGEN ANLEGGSDRIFT AS had revenue of NOK 3.0m in 2025.

Who is the general manager of GULLHAGEN ANLEGGSDRIFT AS?

Arne Olav Gullhagen is registered as general manager of GULLHAGEN ANLEGGSDRIFT AS.

Where is GULLHAGEN ANLEGGSDRIFT AS based?

GULLHAGEN ANLEGGSDRIFT 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.