BIZTRAC BETA
Construction of residential and non-residential buildings

RENSVIK EIENDOM AS

Org. no. 989826581 Limited company (AS) Kristiansund Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 1.3m
Operating profit NOK 707,000
Equity NOK 604,000
Incorporated 2006
Share capital NOK 125,000

RENSVIK EIENDOM AS is registered as a limited company in Kristiansund, Møre og Romsdal with organisation number 989826581. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2006. Registered share capital is NOK 125,000, divided into 1250 shares. The company's stated purpose is: “Å drive handel med og utleie av eiendom og andre produkter og tjenester som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.3m in revenue and NOK 707,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.3m
Operating profit
NOK 707,000
Equity
NOK 604,000
Est. value
NOK 1.6m

Financial health · 2024

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

Who owns RENSVIK EIENDOM AS?

ØYEN INVEST OG UTLEIE AS
RENSVIK EIENDOM AS
NOK 1.3m rev. · NOK 707,000 profit

RENSVIK EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RENSVIK EIENDOM AS

Who owns RENSVIK EIENDOM AS?

ØYEN INVEST OG UTLEIE AS is the largest registered owner, with 100.0%.

What is the revenue of RENSVIK EIENDOM AS?

RENSVIK EIENDOM AS had revenue of NOK 1.3m in 2024.

Where is RENSVIK EIENDOM AS based?

RENSVIK EIENDOM AS has its business address in Kristiansund N.

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.