BIZTRAC BETA
Retail sale of other food

VESTBRYGG AS

Org. no. 912105954 Limited company (AS) Bergen Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 8.5m
Operating profit NOK −230,000
Equity NOK 3.5m
Incorporated 2013
Share capital NOK 400,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−230k kr).

VESTBRYGG AS is registered as a limited company in Bergen, Vestland with organisation number 912105954. The business is classified under retail sale of other food (NACE 47.270). The company was incorporated in 2013. Registered share capital is NOK 400,000, divided into 400 shares. The company's stated purpose is: “Salg av råvarer og bryggeutstyr til hjemmeproduksjon av øl, og dertil tilhørende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 8.5m in revenue and NOK −230,000 in operating profit.

Key figures · 2025

Revenue
NOK 8.5m
Operating profit
NOK −230,000
Equity
NOK 3.5m
Est. value
NOK 4.4m

Financial health · 2025

Liquidity
3.31
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
85.0%
Very good
Equity as a share of total capital

Who owns VESTBRYGG AS?

BIRGER ÅSESØNN STORAAS
VESTBRYGG AS
NOK 8.5m rev. · NOK −230,000 profit

VESTBRYGG AS has 1 registered shareholder:

All shareholders and roles →

Which companies does VESTBRYGG AS own?

VESTBRYGG AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about VESTBRYGG AS

Who owns VESTBRYGG AS?

BIRGER ÅSESØNN STORAAS is the largest registered owner, with 100.0%.

What is the revenue of VESTBRYGG AS?

VESTBRYGG AS had revenue of NOK 8.5m in 2025.

Who is the general manager of VESTBRYGG AS?

Birger Åsesønn Storaas is registered as general manager of VESTBRYGG AS.

Where is VESTBRYGG AS based?

VESTBRYGG 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.