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

AKER BRYGGE GRO AS

Org. no. 992452951 Limited company (AS) Trondheim Incorporated 2008 Active
Revenue 2025 NOK 35.1m
Operating profit NOK 2.3m
Equity NOK 4.3m
Incorporated 2008
Employees 26
Share capital NOK 100,000

AKER BRYGGE GRO AS is registered as a limited company in Trondheim, Trøndelag with organisation number 992452951. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2008 and has 26 registered employees. Registered share capital is NOK 100,000, divided into 200 shares. The company's stated purpose is: “Restaurant og servicevirksomhet samt annen næringsvirksomhet. Deriblant bistå med lån og eventuelle bidrag ved etablering og drift av andre "egon selskaper".”. The most recent filed accounts, for the 2025 financial year, show NOK 35.1m in revenue and NOK 2.3m in operating profit.

Key figures · 2025

Revenue
NOK 35.1m
▲ +0 %
Operating profit
NOK 2.3m
▲ +3 %
Equity
NOK 4.3m
▲ +1 %
Est. value
NOK 11.4m

Financial health · 2025

Liquidity
1.18
Satisfactory
Current assets ÷ current liabilities
Profitability
23.2%
Very good
Return on total assets
Solidity
37.2%
Good
Equity as a share of total capital

Who owns AKER BRYGGE GRO AS?

AKER BRYGGE GRO AS has 10 registered shareholders:

All shareholders and roles →

Frequently asked questions about AKER BRYGGE GRO AS

Who owns AKER BRYGGE GRO AS?

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

What is the revenue of AKER BRYGGE GRO AS?

AKER BRYGGE GRO AS had revenue of NOK 35.1m in 2025.

Who is the general manager of AKER BRYGGE GRO AS?

Tobias Røe Skjelbakken is registered as general manager of AKER BRYGGE GRO AS.

Where is AKER BRYGGE GRO AS based?

AKER BRYGGE GRO 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 03.10.2026.

Report a problem

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