BIZTRAC BETA
Restaurant activities

VIBES KAFE AS

Org. no. 925656267 Limited company (AS) Gjøvik Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 3.0m
Operating profit NOK 50,000
Equity NOK −113,000
Incorporated 2020
Employees 9
Share capital NOK 115,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−113k kr).

VIBES KAFE AS is registered as a limited company in Gjøvik, Innlandet with organisation number 925656267. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2020 and has 9 registered employees. Registered share capital is NOK 115,000, divided into 100 shares. The company's stated purpose is: “Drift av serveringsvirksomhet, catering, rådgivning og andre produkter og tjenester i denne forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.0m in revenue and NOK 50,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.0m
Operating profit
NOK 50,000
Equity
NOK −113,000
Est. value
NOK 372,000

Financial health · 2025

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

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

Who owns VIBES KAFE AS?

ANNE METTE GJESTRUMBAKKEN
VIBES KAFE AS
NOK 3.0m rev. · NOK 50,000 profit

VIBES KAFE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VIBES KAFE AS

Who owns VIBES KAFE AS?

ANNE METTE GJESTRUMBAKKEN is the largest registered owner, with 100.0%.

What is the revenue of VIBES KAFE AS?

VIBES KAFE AS had revenue of NOK 3.0m in 2025.

Who is the general manager of VIBES KAFE AS?

Anne Mette Gjestrumbakken is registered as general manager of VIBES KAFE AS.

Where is VIBES KAFE AS based?

VIBES KAFE AS has its business address in Gjøvik.

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.