BIZTRAC BETA
Restaurant activities

BØVÅGEN ØL OG VINSTUE AS

Org. no. 994548948 Limited company (AS) Alver Incorporated 2009 Active
Ownership graph ↗
Revenue 2025 NOK 322,000
Operating profit NOK −110,000
Equity NOK −1.1m
Incorporated 2009
Share capital NOK 513,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−1,1 mill kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−110k kr).

BØVÅGEN ØL OG VINSTUE AS is registered as a limited company in Alver, Vestland with organisation number 994548948. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2009. Registered share capital is NOK 513,000, divided into 513 shares. The company's stated purpose is: “Restaurantdrift, utleie og andre produkter/tjenester som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 322,000 in revenue and NOK −110,000 in operating profit.

Key figures · 2025

Revenue
NOK 322,000
Operating profit
NOK −110,000
Equity
NOK −1.1m

Financial health · 2025

Liquidity
0.38
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-102.4%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns BØVÅGEN ØL OG VINSTUE AS?

RIKSTAD INVEST AS
BØVÅGEN ØL OG VINSTUE AS
NOK 322,000 rev. · NOK −110,000 profit

BØVÅGEN ØL OG VINSTUE AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about BØVÅGEN ØL OG VINSTUE AS

Who owns BØVÅGEN ØL OG VINSTUE AS?

RIKSTAD INVEST AS is the largest registered owner, with 38.6%.

What is the revenue of BØVÅGEN ØL OG VINSTUE AS?

BØVÅGEN ØL OG VINSTUE AS had revenue of NOK 322,000 in 2025.

Where is BØVÅGEN ØL OG VINSTUE AS based?

BØVÅGEN ØL OG VINSTUE AS has its business address in Bøvågen.

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.