BIZTRAC BETA
Restaurant activities

KULTURHUSET I BERGEN AS

Org. no. 815413962 Limited company (AS) Bergen Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 29.8m
Operating profit NOK −3.3m
Equity NOK 640,000
Incorporated 2015
Share capital NOK 39,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−3,3 mill kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

KULTURHUSET I BERGEN AS is registered as a limited company in Bergen, Vestland with organisation number 815413962. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2015. Registered share capital is NOK 39,000, divided into 38982 shares. The company's stated purpose is: “Restauranter, derunder kjøp og salg av slike, etablering av nye restauranter, samt dermed forbundet virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 29.8m in revenue and NOK −3.3m in operating profit.

Key figures · 2024

Revenue
NOK 29.8m
Operating profit
NOK −3.3m
Equity
NOK 640,000
Est. value
NOK 21.1m

Financial health · 2024

Liquidity
0.96
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
4.8%
Weak
Equity as a share of total capital

Who owns KULTURHUSET I BERGEN AS?

ALTONA AS
KULTURHUSET I BERGEN AS
NOK 29.8m rev. · NOK −3.3m profit

KULTURHUSET I BERGEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KULTURHUSET I BERGEN AS

Who owns KULTURHUSET I BERGEN AS?

ALTONA AS is the largest registered owner, with 100.0%.

What is the revenue of KULTURHUSET I BERGEN AS?

KULTURHUSET I BERGEN AS had revenue of NOK 29.8m in 2024.

Where is KULTURHUSET I BERGEN AS based?

KULTURHUSET I BERGEN AS has its business address in Bergen.

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.