BIZTRAC BETA
Site preparation

HAGEN GJENVINNING AS

Org. no. 998016991 Limited company (AS) Oslo Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 21.3m
Operating profit NOK 7.7m
Equity NOK 857,000
Incorporated 2012
Share capital NOK 30,000

HAGEN GJENVINNING AS is registered as a limited company in Oslo, Oslo with organisation number 998016991. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Deponi for miljøvennlige gravemasser. Arbeid innen tomteheving, samt oppgradering og utbedring av landskap. Drift og utleie av biler og anleggsmaskiner.”. The most recent filed accounts, for the 2025 financial year, show NOK 21.3m in revenue and NOK 7.7m in operating profit.

Key figures · 2025

Revenue
NOK 21.3m
Operating profit
NOK 7.7m
Equity
NOK 857,000
Est. value
NOK 22.5m

Financial health · 2025

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

Who owns HAGEN GJENVINNING AS?

HAGEN CAPITAL PARTNERS AS
HAGEN GJENVINNING AS
NOK 21.3m rev. · NOK 7.7m profit

HAGEN GJENVINNING AS has 1 registered shareholder:

All shareholders and roles →

Group structure

HAGEN GJENVINNING AS er morselskap for 3 datterselskaper:

Frequently asked questions about HAGEN GJENVINNING AS

Who owns HAGEN GJENVINNING AS?

HAGEN CAPITAL PARTNERS AS is the largest registered owner, with 100.0%.

What is the revenue of HAGEN GJENVINNING AS?

HAGEN GJENVINNING AS had revenue of NOK 21.3m in 2025.

Who is the general manager of HAGEN GJENVINNING AS?

Arild Hagen is registered as general manager of HAGEN GJENVINNING AS.

Where is HAGEN GJENVINNING AS based?

HAGEN GJENVINNING AS has its business address in Oslo.

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.