BIZTRAC BETA
Development of building projects

ARO AS

Org. no. 961963788 Limited company (AS) Trondheim Incorporated 1991 Active
Ownership graph ↗
Revenue 2024 NOK 336,000
Operating profit NOK 106,000
Equity NOK 45.6m
Incorporated 1991
Share capital NOK 100,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

ARO AS is registered as a limited company in Trondheim, Trøndelag with organisation number 961963788. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 1991. Registered share capital is NOK 100,000, divided into 50 shares. The company's stated purpose is: “Drive med kjøp og salg av aksjer, investeringer i fast eiendom, utvikling av eiendom og deltakelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 336,000 in revenue and NOK 106,000 in operating profit.

Key figures · 2024

Revenue
NOK 336,000
Operating profit
NOK 106,000
Equity
NOK 45.6m
Est. value
NOK 31.6m

Financial health · 2024

Liquidity
206.90
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 ARO AS?

MARI HOLDING AS
ARO AS
NOK 336,000 rev. · NOK 106,000 profit

ARO AS has 2 registered shareholders:

All shareholders and roles →

Which companies does ARO AS own?

ARO AS holds stakes in 5 companies:

See the full ownership structure →

Frequently asked questions about ARO AS

Who owns ARO AS?

MARI HOLDING AS is the largest registered owner, with 50.0%.

What is the revenue of ARO AS?

ARO AS had revenue of NOK 336,000 in 2024.

Who is the general manager of ARO AS?

Rasmus Olstad is registered as general manager of ARO AS.

Where is ARO AS based?

ARO 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.