BIZTRAC BETA
Restaurant activities

AROI ASIA AS

Org. no. 918704051 Limited company (AS) Levanger Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 12.9m
Operating profit NOK 1.3m
Equity NOK 1.1m
Incorporated 2017
Employees 37
Share capital NOK 200,000

AROI ASIA AS is registered as a limited company in Levanger, Trøndelag with organisation number 918704051. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2017 and has 37 registered employees. Registered share capital is NOK 200,000, divided into 200 shares. The company's stated purpose is: “Investeringer i aksjer og verdipapirer, delta i andre selskaper og virksomheter, drive handel og forvaltning av fast eiendom og alt som står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 12.9m in revenue and NOK 1.3m in operating profit.

Key figures · 2024

Revenue
NOK 12.9m
Operating profit
NOK 1.3m
Equity
NOK 1.1m
Est. value
NOK 5.1m

Financial health · 2024

Liquidity
1.39
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
30.6%
Good
Equity as a share of total capital

Who owns AROI ASIA AS?

URI INVEST AS
AROI ASIA AS
NOK 12.9m rev. · NOK 1.3m profit

AROI ASIA AS has 2 registered shareholders:

All shareholders and roles →

Which companies does AROI ASIA AS own?

AROI ASIA AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about AROI ASIA AS

Who owns AROI ASIA AS?

URI INVEST AS is the largest registered owner, with 50.0%.

What is the revenue of AROI ASIA AS?

AROI ASIA AS had revenue of NOK 12.9m in 2024.

Who is the general manager of AROI ASIA AS?

Ulf Erling Rinnan is registered as general manager of AROI ASIA AS.

Where is AROI ASIA AS based?

AROI ASIA AS has its business address in Levanger.

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.