biztrac. BETA
COMPANY REGISTER PROFILE
927612100 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Other captive investment companies

RO LEGACY AS

Org. no. 927612100 Limited company (AS) Iveland Incorporated 2021 Active
Ownership graph ↗
Operating profit NOK −46,000
Equity NOK −230,000
Incorporated 2021
Share capital NOK 44,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−230k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−46k kr).

RO LEGACY AS is registered as a limited company in Iveland, Agder with organisation number 927612100. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2021. Registered share capital is NOK 44,000, divided into 182405614 shares. The company's stated purpose is: “Direkte og/eller indirekte - å kjøpe, eie og selge aksjer, obligasjoner og andre finansielle instrumenter og alt som er beslektet eller står i forbindelse med dette. Selskapet skal også kunne eie - helt eller delvis - eller delta i selskaper eller foretak som driver næringsvirksomhet, samt deltagelse i andre selskaper ved aksjeinnskudd eller på annen måte”.

Former names: NFH 210825 AS

Key figures · 2025

Operating profit
NOK −46,000
▲ +18 %
Equity
NOK −230,000
▼ −25 %

Financial health · 2025

Liquidity
12.06
Very good
Current assets ÷ current liabilities
Profitability
-7.5%
Not satisfactory
Return on total assets
Solidity
-38.8%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns RO LEGACY AS?

RO LEGACY AS has 20+ registered shareholders:

All shareholders and roles →

Frequently asked questions about RO LEGACY AS

Who owns RO LEGACY AS?

HARLEM FOOD AS is the largest registered owner, with 23.4%.

Where is RO LEGACY AS based?

RO LEGACY AS has its business address in Vatnestrøm.

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.