BIZTRAC BETA
Restaurant activities

KOS KAFE OG SPISERI AS

Org. no. 925110809 Limited company (AS) Kristiansund Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 11.8m
Operating profit NOK 623,000
Equity NOK 1.9m
Incorporated 2020
Employees 18
Share capital NOK 300,000

KOS KAFE OG SPISERI AS is registered as a limited company in Kristiansund, Møre og Romsdal with organisation number 925110809. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2020 and has 18 registered employees. Registered share capital is NOK 300,000, divided into 300 shares. The company's stated purpose is: “Drift av kafe og det som naturlig hører under. Selskapet kan også delta i andre selskaper som styret finner det fornuftig å involvere seg i.”. The most recent filed accounts, for the 2025 financial year, show NOK 11.8m in revenue and NOK 623,000 in operating profit.

Key figures · 2025

Revenue
NOK 11.8m
Operating profit
NOK 623,000
Equity
NOK 1.9m
Est. value
NOK 3.3m

Financial health · 2025

Liquidity
1.66
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
41.9%
Very good
Equity as a share of total capital

Who owns KOS KAFE OG SPISERI AS?

MARIANNE BERGDAL
KOS KAFE OG SPISERI AS
NOK 11.8m rev. · NOK 623,000 profit

KOS KAFE OG SPISERI AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about KOS KAFE OG SPISERI AS

Who owns KOS KAFE OG SPISERI AS?

MARIANNE BERGDAL is the largest registered owner, with 50.0%.

What is the revenue of KOS KAFE OG SPISERI AS?

KOS KAFE OG SPISERI AS had revenue of NOK 11.8m in 2025.

Who is the general manager of KOS KAFE OG SPISERI AS?

Marianne Bergdal is registered as general manager of KOS KAFE OG SPISERI AS.

Where is KOS KAFE OG SPISERI AS based?

KOS KAFE OG SPISERI AS has its business address in Kristiansund N.

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.