BIZTRAC BETA
Rental and operating of own or leased real estate

RIIBER HOLDING AS

Org. no. 989239112 Limited company (AS) Frøya Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 598,000
Operating profit NOK −302,000
Equity NOK 222.0m
Incorporated 2005
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−302k kr).

RIIBER HOLDING AS is registered as a limited company in Frøya, Trøndelag with organisation number 989239112. 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 100,000, divided into 1 shares. The company's stated purpose is: “Å være et holdingselskap med kjøp og salg av aksjer, samt alt hva hermed står i forbindelse”. The most recent filed accounts, for the 2024 financial year, show NOK 598,000 in revenue and NOK −302,000 in operating profit.

Key figures · 2024

Revenue
NOK 598,000
Operating profit
NOK −302,000
Equity
NOK 222.0m
Est. value
NOK 154.6m

Financial health · 2024

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

Who owns RIIBER HOLDING AS?

FRODE RIIBER
RIIBER HOLDING AS
NOK 598,000 rev. · NOK −302,000 profit

RIIBER HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does RIIBER HOLDING AS own?

RIIBER HOLDING AS holds stakes in 9 companies:

See the full ownership structure →

Frequently asked questions about RIIBER HOLDING AS

Who owns RIIBER HOLDING AS?

FRODE RIIBER is the largest registered owner, with 100.0%.

What is the revenue of RIIBER HOLDING AS?

RIIBER HOLDING AS had revenue of NOK 598,000 in 2024.

Where is RIIBER HOLDING AS based?

RIIBER HOLDING AS has its business address in Hamarvik.

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.