biztrac. BETA
COMPANY REGISTER PROFILE
990626006 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Restaurant activities

ARENDAL GRO AS

Org. no. 990626006 Limited company (AS) Arendal Incorporated 2006 Active
Ownership graph ↗
Revenue 2025 NOK 32.2m
Operating profit NOK 2.5m
Equity NOK 1.3m
Incorporated 2006
Employees 20
Share capital NOK 100,000

ARENDAL GRO AS is registered as a limited company in Arendal, Agder with organisation number 990626006. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2006 and has 20 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Drive restaurant og servicevirksomhet samt annen næringsvirksomhet. Der iblant bistå med lån og eventuelle bidrag ved etablering og drift av andre "Egon-selskaper". Selskapet skal ha en daglig leder og en stedfortreder.”. The most recent filed accounts, for the 2025 financial year, show NOK 32.2m in revenue and NOK 2.5m in operating profit.

Key figures · 2025

Revenue
NOK 32.2m
▲ +7 %
Operating profit
NOK 2.5m
▼ −10 %
Equity
NOK 1.3m
▼ −0 %
Est. value
NOK 9.9m

Financial health · 2025

Liquidity
0.81
Weak
Current assets ÷ current liabilities
Profitability
26.7%
Very good
Return on total assets
Solidity
12.7%
Satisfactory
Equity as a share of total capital

Who owns ARENDAL GRO AS?

ARENDAL GRO AS has 9 registered shareholders:

All shareholders and roles →

Frequently asked questions about ARENDAL GRO AS

Who owns ARENDAL GRO AS?

NORREIN HOLDING AS is the largest registered owner, with 35.0%.

What is the revenue of ARENDAL GRO AS?

ARENDAL GRO AS had revenue of NOK 32.2m in 2025.

Who is the general manager of ARENDAL GRO AS?

Simon Lanng is registered as general manager of ARENDAL GRO AS.

Where is ARENDAL GRO AS based?

ARENDAL GRO AS has its business address in Arendal.

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.