biztrac. BETA
COMPANY REGISTER PROFILE
820374452 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

R-S EIENDOM AS

Org. no. 820374452 Limited company (AS) Farsund Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 440,000
Operating profit NOK 313,000
Equity NOK 316,000
Incorporated 2018
Share capital NOK 100,000

R-S EIENDOM AS is registered as a limited company in Farsund, Agder with organisation number 820374452. 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 100,000, divided into 100 shares. The company's stated purpose is: “Eie, kjøpe og selge eiendom og annet som naturlig faller sammen med dette. selskapet kan også drive med deltakelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 440,000 in revenue and NOK 313,000 in operating profit.

Key figures · 2025

Revenue
NOK 440,000
▲ +11 %
Operating profit
NOK 313,000
▲ +31 %
Equity
NOK 316,000
▲ +49 %
Est. value
NOK 613,000

Financial health · 2025

Liquidity
0.34
Not satisfactory
Current assets ÷ current liabilities
Profitability
11.1%
Good
Return on total assets
Solidity
11.1%
Satisfactory
Equity as a share of total capital

Who owns R-S EIENDOM AS?

R-S EIENDOM AS
NOK 440,000 rev. · NOK 313,000 profit

R-S EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about R-S EIENDOM AS

Who owns R-S EIENDOM AS?

Steffen Vik is the largest registered owner, with 100.0%.

What is the revenue of R-S EIENDOM AS?

R-S EIENDOM AS had revenue of NOK 440,000 in 2025.

Who is the general manager of R-S EIENDOM AS?

Steffen Vik is registered as general manager of R-S EIENDOM AS.

Where is R-S EIENDOM AS based?

R-S EIENDOM AS has its business address in Vanse.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.