BIZTRAC BETA
Rental and operating of own or leased real estate

RUENESS EIENDOM AS

Org. no. 921070314 Limited company (AS) Tvedestrand Incorporated 2018 Active
Ownership graph ↗
Operating profit NOK −412,000
Equity NOK −690,000
Incorporated 2018
Share capital NOK 44,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−690k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−412k kr).

RUENESS EIENDOM AS is registered as a limited company in Tvedestrand, Agder with organisation number 921070314. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2018. Registered share capital is NOK 44,000, divided into 4364 shares. The company's stated purpose is: “Kjøp, drift og salg av fast eiendom, utvikling av tomteområder samt deltakelse i andre selskaper.”.

Key figures · 2025

Operating profit
NOK −412,000
Equity
NOK −690,000

Financial health · 2025

Liquidity
0.89
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-5.8%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns RUENESS EIENDOM AS?

VIDAR MICHAEL RUENESS
RUENESS EIENDOM AS
· NOK −412,000 profit

RUENESS EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does RUENESS EIENDOM AS own?

RUENESS EIENDOM AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about RUENESS EIENDOM AS

Who owns RUENESS EIENDOM AS?

VIDAR MICHAEL RUENESS is the largest registered owner, with 100.0%.

Who is the general manager of RUENESS EIENDOM AS?

Vidar Michael Rueness is registered as general manager of RUENESS EIENDOM AS.

Where is RUENESS EIENDOM AS based?

RUENESS EIENDOM AS has its business address in Tvedestrand.

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.