BIZTRAC BETA
COMPANY REGISTER PROFILE
924415533 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

RILLRO AS

Org. no. 924415533 Limited company (AS) Bærum Incorporated 2019 Active
Ownership graph ↗
Operating profit NOK −37,000
Equity NOK 15.7m
Incorporated 2019
Share capital NOK 30,000

Signals

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

RILLRO AS is registered as a limited company in Bærum, Akershus with organisation number 924415533. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 12 shares. The company's stated purpose is: “Å eie aksjer og eiendomsforvaltning, og det som naturlig hører sammen med dette.”.

Key figures · 2025

Operating profit
NOK −37,000
Equity
NOK 15.7m
Est. value
NOK 13.2m

Financial health · 2025

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

Who owns RILLRO AS?

RILLRO AS has 4 registered shareholders:

All shareholders and roles →

Which companies does RILLRO AS own?

RILLRO AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about RILLRO AS

Who owns RILLRO AS?

RAGNHILD ROGNERUD is the largest registered owner, with 50.0%.

Where is RILLRO AS based?

RILLRO AS has its business address in Kolsås.

Property

Business address Lillehauger 3, 1352 Kolsås
Cadastral unit 3201-89/314/0/0
Building Terrassehus · 12 units

4 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.