BIZTRAC BETA
Restaurant activities

DELICATESSEN AKER BRYGGE AS

Org. no. 911578476 Limited company (AS) Oslo Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 28.6m
Operating profit NOK 4.2m
Equity NOK 2.0m
Incorporated 2013
Employees 19
Share capital NOK 780,000

Signals

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

DELICATESSEN AKER BRYGGE AS is registered as a limited company in Oslo, Oslo with organisation number 911578476. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2013 and has 19 registered employees. Registered share capital is NOK 780,000, divided into 780000 shares. The company's stated purpose is: “Å drive restaurantvirksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 28.6m in revenue and NOK 4.2m in operating profit.

Key figures · 2024

Revenue
NOK 28.6m
Operating profit
NOK 4.2m
Equity
NOK 2.0m
Est. value
NOK 16.7m

Financial health · 2024

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

Who owns DELICATESSEN AKER BRYGGE AS?

DELICATESSEN RESTAURANTS AS
DELICATESSEN AKER BRYGGE AS
NOK 28.6m rev. · NOK 4.2m profit

DELICATESSEN AKER BRYGGE AS has 1 registered shareholder:

All shareholders and roles →

Group structure

DELICATESSEN AKER BRYGGE AS er morselskap for 6 datterselskaper:

Frequently asked questions about DELICATESSEN AKER BRYGGE AS

Who owns DELICATESSEN AKER BRYGGE AS?

DELICATESSEN RESTAURANTS AS is the largest registered owner, with 100.0%.

What is the revenue of DELICATESSEN AKER BRYGGE AS?

DELICATESSEN AKER BRYGGE AS had revenue of NOK 28.6m in 2024.

Where is DELICATESSEN AKER BRYGGE AS based?

DELICATESSEN AKER BRYGGE AS has its business address in Oslo.

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.