BIZTRAC BETA
Rental and operating of own or leased real estate

RINGDALSKOGEN EIENDOM AS

Org. no. 933660796 Limited company (AS) Larvik Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 4.0m
Operating profit NOK 2.7m
Equity NOK 21.8m
Incorporated 2024
Share capital NOK 60,000

RINGDALSKOGEN EIENDOM AS is registered as a limited company in Larvik, Vestfold with organisation number 933660796. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2024. Registered share capital is NOK 60,000, divided into 3000 shares. The company's stated purpose is: “Drift av fast eiendom, herunder utleievirksomhet og det som naturlig følger av dette, samt deltagelse i andre virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.0m in revenue and NOK 2.7m in operating profit.

Key figures · 2025

Revenue
NOK 4.0m
Operating profit
NOK 2.7m
Equity
NOK 21.8m
Est. value
NOK 19.5m

Financial health · 2025

Liquidity
0.96
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
31.8%
Good
Equity as a share of total capital

Who owns RINGDALSKOGEN EIENDOM AS?

SKAGERAK EIENDOM AS
RINGDALSKOGEN EIENDOM AS
NOK 4.0m rev. · NOK 2.7m profit

RINGDALSKOGEN EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does RINGDALSKOGEN EIENDOM AS own?

RINGDALSKOGEN EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about RINGDALSKOGEN EIENDOM AS

Who owns RINGDALSKOGEN EIENDOM AS?

SKAGERAK EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of RINGDALSKOGEN EIENDOM AS?

RINGDALSKOGEN EIENDOM AS had revenue of NOK 4.0m in 2025.

Where is RINGDALSKOGEN EIENDOM AS based?

RINGDALSKOGEN EIENDOM AS has its business address in Larvik.

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.