BIZTRAC BETA
Restaurant activities

DIS KAFFEBAR AS

Org. no. 928988910 Limited company (AS) Sykkylven Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 2.1m
Operating profit NOK −433,000
Equity NOK −724,000
Incorporated 2022
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−724k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−433k kr).

DIS KAFFEBAR AS is registered as a limited company in Sykkylven, Møre og Romsdal with organisation number 928988910. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Kaffebar, kultur, næring og utleie.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.1m in revenue and NOK −433,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.1m
Operating profit
NOK −433,000
Equity
NOK −724,000

Financial health · 2024

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

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

Who owns DIS KAFFEBAR AS?

THERESE KRISTIN STIGEN
DIS KAFFEBAR AS
NOK 2.1m rev. · NOK −433,000 profit

DIS KAFFEBAR AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about DIS KAFFEBAR AS

Who owns DIS KAFFEBAR AS?

THERESE KRISTIN STIGEN is the largest registered owner, with 50.0%.

What is the revenue of DIS KAFFEBAR AS?

DIS KAFFEBAR AS had revenue of NOK 2.1m in 2024.

Who is the general manager of DIS KAFFEBAR AS?

Tim Christopher Viksand is registered as general manager of DIS KAFFEBAR AS.

Where is DIS KAFFEBAR AS based?

DIS KAFFEBAR AS has its business address in Sykkylven.

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.