BIZTRAC BETA
Restaurant activities

BJØRVIKA BISTRO AS

Org. no. 920365515 Limited company (AS) Oslo Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 34.4m
Operating profit NOK 2.0m
Equity NOK 2.4m
Incorporated 2018
Employees 27
Share capital NOK 60,000

Signals

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

BJØRVIKA BISTRO AS is registered as a limited company in Oslo, Oslo with organisation number 920365515. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2018 and has 27 registered employees. Registered share capital is NOK 60,000, divided into 30 shares. The company's stated purpose is: “Restaurantdrift, uteservering og ellers hva som heri står i forbindelse”. The most recent filed accounts, for the 2024 financial year, show NOK 34.4m in revenue and NOK 2.0m in operating profit.

Key figures · 2024

Revenue
NOK 34.4m
Operating profit
NOK 2.0m
Equity
NOK 2.4m
Est. value
NOK 8.5m

Financial health · 2024

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

Who owns BJØRVIKA BISTRO AS?

DOGNVILL HOLDING AS
BJØRVIKA BISTRO AS
NOK 34.4m rev. · NOK 2.0m profit

BJØRVIKA BISTRO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BJØRVIKA BISTRO AS

Who owns BJØRVIKA BISTRO AS?

DOGNVILL HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of BJØRVIKA BISTRO AS?

BJØRVIKA BISTRO AS had revenue of NOK 34.4m in 2024.

Who is the general manager of BJØRVIKA BISTRO AS?

Tarje Haakstad is registered as general manager of BJØRVIKA BISTRO AS.

Where is BJØRVIKA BISTRO AS based?

BJØRVIKA BISTRO 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.