BIZTRAC BETA
Rental and operating of own or leased real estate

RIIS INVEST AS

Org. no. 914616344 Limited company (AS) Lillestrøm Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 1.8m
Operating profit NOK 945,000
Equity NOK 85.0m
Incorporated 2014
Share capital NOK 100,000

RIIS INVEST AS is registered as a limited company in Lillestrøm, Akershus with organisation number 914616344. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2014. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Kjøp, utleie og salg av fast eiendom. Investeringsselskap, herunder investeringer i aksjer, andeler i selskap etter selskapsloven, utenlandske selskaper og andre finansielle eiendeler. Annen virksomhet naturlig relatert til ovenstående.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.8m in revenue and NOK 945,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.8m
Operating profit
NOK 945,000
Equity
NOK 85.0m
Est. value
NOK 61.2m

Financial health · 2024

Liquidity
8.06
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
96.4%
Very good
Equity as a share of total capital

Who owns RIIS INVEST AS?

RUNE STRØM NÆVERDAL
RIIS INVEST AS
NOK 1.8m rev. · NOK 945,000 profit

RIIS INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does RIIS INVEST AS own?

RIIS INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about RIIS INVEST AS

Who owns RIIS INVEST AS?

RUNE STRØM NÆVERDAL is the largest registered owner, with 100.0%.

What is the revenue of RIIS INVEST AS?

RIIS INVEST AS had revenue of NOK 1.8m in 2024.

Where is RIIS INVEST AS based?

RIIS INVEST AS has its business address in Kjeller.

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.