BIZTRAC BETA
Rental and operating of own or leased real estate

ROGER HAGEN AS

Org. no. 912251888 Limited company (AS) Oslo Incorporated 1971 Active
Ownership graph ↗
Revenue 2025 NOK 975,000
Operating profit NOK 339,000
Equity NOK 1.0m
Incorporated 1971
Share capital NOK 500,000

ROGER HAGEN AS is registered as a limited company in Oslo, Oslo with organisation number 912251888. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1971. Registered share capital is NOK 500,000, divided into 100 shares. The company's stated purpose is: “VVS-virksomhet, EL-installasjon, herunder deltagelse i andre selskaper av enhver art, og hva hermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 975,000 in revenue and NOK 339,000 in operating profit.

Key figures · 2025

Revenue
NOK 975,000
Operating profit
NOK 339,000
Equity
NOK 1.0m
Est. value
NOK 1.6m

Financial health · 2025

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

Who owns ROGER HAGEN AS?

BJØRN-ERIK ANDERSEN
ROGER HAGEN AS
NOK 975,000 rev. · NOK 339,000 profit

ROGER HAGEN AS has 2 registered shareholders:

All shareholders and roles →

Which companies does ROGER HAGEN AS own?

ROGER HAGEN AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about ROGER HAGEN AS

Who owns ROGER HAGEN AS?

BJØRN-ERIK ANDERSEN is the largest registered owner, with 55.0%.

What is the revenue of ROGER HAGEN AS?

ROGER HAGEN AS had revenue of NOK 975,000 in 2025.

Who is the general manager of ROGER HAGEN AS?

Bjørn-Erik Andersen is registered as general manager of ROGER HAGEN AS.

Where is ROGER HAGEN AS based?

ROGER HAGEN 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.