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

RIMO HOLDING AS

Org. no. 989140302 Limited company (AS) Ringsaker Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 24,000
Operating profit NOK −237,000
Equity NOK 1.2m
Incorporated 2005
Share capital NOK 1.1m

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−237k kr).

RIMO HOLDING AS is registered as a limited company in Ringsaker, Innlandet with organisation number 989140302. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2005. Registered share capital is NOK 1.1m, divided into 1002 shares. The company's stated purpose is: “Å investere i andre selskaper samt hva som herved står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 24,000 in revenue and NOK −237,000 in operating profit.

Key figures · 2025

Revenue
NOK 24,000
▼ −6 %
Operating profit
NOK −237,000
▼ −53 %
Equity
NOK 1.2m
▼ −28 %
Est. value
NOK 10.3m

Financial health · 2025

Liquidity
1.09
Satisfactory
Current assets ÷ current liabilities
Profitability
33.9%
Very good
Return on total assets
Solidity
6.7%
Weak
Equity as a share of total capital

Who owns RIMO HOLDING AS?

RIMO HOLDING AS has 8 registered shareholders:

All shareholders and roles →

Which companies does RIMO HOLDING AS own?

RIMO HOLDING AS holds stakes in 6 companies:

See the full ownership structure →

Frequently asked questions about RIMO HOLDING AS

Who owns RIMO HOLDING AS?

FEB HOLDING AS is the largest registered owner, with 29.9%.

What is the revenue of RIMO HOLDING AS?

RIMO HOLDING AS had revenue of NOK 24,000 in 2025.

Where is RIMO HOLDING AS based?

RIMO HOLDING AS has its business address in Brumunddal.

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.