BIZTRAC BETA
Restaurant activities

KVIKK BAR AS

Org. no. 991493662 Limited company (AS) Skaun Incorporated 2007 Active
Ownership graph ↗
Revenue 2024 NOK 624,000
Operating profit NOK −41,000
Equity NOK −1.0m
Incorporated 2007
Share capital NOK 210,000

Signals

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

KVIKK BAR AS is registered as a limited company in Skaun, Trøndelag with organisation number 991493662. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2007. Registered share capital is NOK 210,000, divided into 21000 shares. The company's stated purpose is: “Drive cafévirksomhet, herunder servering av mat og drikke, samt eierskap i andre virksomheter.”. The most recent filed accounts, for the 2024 financial year, show NOK 624,000 in revenue and NOK −41,000 in operating profit.

Key figures · 2024

Revenue
NOK 624,000
Operating profit
NOK −41,000
Equity
NOK −1.0m

Financial health · 2024

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

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

Who owns KVIKK BAR AS?

BEATE ARENTZ HAGEN
KVIKK BAR AS
NOK 624,000 rev. · NOK −41,000 profit

KVIKK BAR AS has 5 registered shareholders:

All shareholders and roles →

Frequently asked questions about KVIKK BAR AS

Who owns KVIKK BAR AS?

BEATE ARENTZ HAGEN is the largest registered owner, with 33.6%.

What is the revenue of KVIKK BAR AS?

KVIKK BAR AS had revenue of NOK 624,000 in 2024.

Who is the general manager of KVIKK BAR AS?

Karianne Arentz Hagen is registered as general manager of KVIKK BAR AS.

Where is KVIKK BAR AS based?

KVIKK BAR AS has its business address in Viggja.

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.