BIZTRAC BETA
Rental and operating of own or leased real estate

RIIBO EIENDOM AS

Org. no. 871073252 Limited company (AS) Trondheim Incorporated 1994 Active
Ownership graph ↗
Revenue 2025 NOK 261,000
Operating profit NOK −129,000
Equity NOK 6.0m
Incorporated 1994
Share capital NOK 250,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−129k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

RIIBO EIENDOM AS is registered as a limited company in Trondheim, Trøndelag with organisation number 871073252. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1994. Registered share capital is NOK 250,000. The company's stated purpose is: “Handel, herunder kjøp, salg og drift av fast eiendom, videre deltakelse i andre selskaper samt hva hermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 261,000 in revenue and NOK −129,000 in operating profit.

Key figures · 2025

Revenue
NOK 261,000
Operating profit
NOK −129,000
Equity
NOK 6.0m
Est. value
NOK 4.5m

Financial health · 2025

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

Who owns RIIBO EIENDOM AS?

RIIBEGRUPPEN AS
RIIBO EIENDOM AS
NOK 261,000 rev. · NOK −129,000 profit

RIIBO EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RIIBO EIENDOM AS

Who owns RIIBO EIENDOM AS?

RIIBEGRUPPEN AS is the largest registered owner, with 100.0%.

What is the revenue of RIIBO EIENDOM AS?

RIIBO EIENDOM AS had revenue of NOK 261,000 in 2025.

Where is RIIBO EIENDOM AS based?

RIIBO EIENDOM AS has its business address in Trondheim.

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.