BIZTRAC BETA
Development of building projects

GULLHAUGEN AS

Org. no. 923803130 Limited company (AS) Drammen Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 318,000
Operating profit NOK 181,000
Equity NOK 1.5m
Incorporated 2019
Share capital NOK 30,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

GULLHAUGEN AS is registered as a limited company in Drammen, Buskerud with organisation number 923803130. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Investering i eiendom og eiendomsutvikling og andre produkter/tjenester som naturlig hører til dette, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 318,000 in revenue and NOK 181,000 in operating profit.

Key figures · 2025

Revenue
NOK 318,000
Operating profit
NOK 181,000
Equity
NOK 1.5m
Est. value
NOK 1.3m

Financial health · 2025

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

Who owns GULLHAUGEN AS?

GULLHAUGEN HOLDING AS
GULLHAUGEN AS
NOK 318,000 rev. · NOK 181,000 profit

GULLHAUGEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GULLHAUGEN AS

Who owns GULLHAUGEN AS?

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

What is the revenue of GULLHAUGEN AS?

GULLHAUGEN AS had revenue of NOK 318,000 in 2025.

Where is GULLHAUGEN AS based?

GULLHAUGEN AS has its business address in Drammen.

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.