BIZTRAC BETA
Repair and maintenance of motor vehicles

SKOGEN EIENDOM AS

Org. no. 984573324 Limited company (AS) Gol Incorporated 2002 Active
Ownership graph ↗
Revenue 2024 NOK 5.1m
Operating profit NOK 3.2m
Equity NOK 1.3m
Incorporated 2002
Share capital NOK 400,000

SKOGEN EIENDOM AS is registered as a limited company in Gol, Buskerud with organisation number 984573324. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 2002. Registered share capital is NOK 400,000, divided into 2000 shares. The company's stated purpose is: “Kjøp, salg og forvaltning av fast eiendom og det som hermed står i forbindelse, samt deltakelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 5.1m in revenue and NOK 3.2m in operating profit.

Key figures · 2024

Revenue
NOK 5.1m
Operating profit
NOK 3.2m
Equity
NOK 1.3m
Est. value
NOK 10.2m

Financial health · 2024

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

Who owns SKOGEN EIENDOM AS?

STØLEN EIENDOM AS
SKOGEN EIENDOM AS
NOK 5.1m rev. · NOK 3.2m profit

SKOGEN EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SKOGEN EIENDOM AS own?

SKOGEN EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SKOGEN EIENDOM AS

Who owns SKOGEN EIENDOM AS?

STØLEN EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of SKOGEN EIENDOM AS?

SKOGEN EIENDOM AS had revenue of NOK 5.1m in 2024.

Who is the general manager of SKOGEN EIENDOM AS?

Ola Stølen is registered as general manager of SKOGEN EIENDOM AS.

Where is SKOGEN EIENDOM AS based?

SKOGEN EIENDOM AS has its business address in Gol.

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.