BIZTRAC BETA
Rental and operating of own or leased real estate

RICKO EIENDOM AS

Org. no. 990309477 Limited company (AS) Oslo Incorporated 2006 Active
Ownership graph ↗
Revenue 2025 NOK 1.3m
Operating profit NOK 749,000
Equity NOK 2.0m
Incorporated 2006
Share capital NOK 100,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

RICKO EIENDOM AS is registered as a limited company in Oslo, Oslo with organisation number 990309477. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2006. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Investeringsvirksomhet, herunder investering i finansielle instrumenter, selskapsandeler og fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.3m in revenue and NOK 749,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.3m
Operating profit
NOK 749,000
Equity
NOK 2.0m
Est. value
NOK 2.6m

Financial health · 2025

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

Who owns RICKO EIENDOM AS?

ARVO INVEST AS
RICKO EIENDOM AS
NOK 1.3m rev. · NOK 749,000 profit

RICKO EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RICKO EIENDOM AS

Who owns RICKO EIENDOM AS?

ARVO INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of RICKO EIENDOM AS?

RICKO EIENDOM AS had revenue of NOK 1.3m in 2025.

Who is the general manager of RICKO EIENDOM AS?

Ole Dag Rustad is registered as general manager of RICKO EIENDOM AS.

Where is RICKO EIENDOM AS based?

RICKO EIENDOM AS has its business address in Oslo.

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.