BIZTRAC BETA
Other support activities to arts and performing arts

SOMMERBRIS AS

Org. no. 924354674 Limited company (AS) Kristiansand Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 41.9m
Operating profit NOK 2.2m
Equity NOK 2.4m
Incorporated 2019
Employees 8
Share capital NOK 100,000

Signals

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

SOMMERBRIS AS is registered as a limited company in Kristiansand, Agder with organisation number 924354674. The business is classified under other support activities to arts and performing arts (NACE 90.390). The company was incorporated in 2019 and has 8 registered employees. Registered share capital is NOK 100,000, divided into 10000 shares. The company's stated purpose is: “Drive festival-, restaurant og kafedrift, samt å investere i annen forretningsvirksomhet, herunder delta i andre selskaper som aksjeeier eller ansvarlig deltaker.”. The most recent filed accounts, for the 2024 financial year, show NOK 41.9m in revenue and NOK 2.2m in operating profit.

Key figures · 2024

Revenue
NOK 41.9m
Operating profit
NOK 2.2m
Equity
NOK 2.4m
Est. value
NOK 10.9m

Financial health · 2024

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

Who owns SOMMERBRIS AS?

STRØMME STRØM AS
SOMMERBRIS AS
NOK 41.9m rev. · NOK 2.2m profit

SOMMERBRIS AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about SOMMERBRIS AS

Who owns SOMMERBRIS AS?

STRØMME STRØM AS is the largest registered owner, with 68.0%.

What is the revenue of SOMMERBRIS AS?

SOMMERBRIS AS had revenue of NOK 41.9m in 2024.

Where is SOMMERBRIS AS based?

SOMMERBRIS AS has its business address in Kristiansand S.

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.