biztrac. BETA
COMPANY REGISTER PROFILE
928653137 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Restaurant activities

KLATREKAFEEN AS

Org. no. 928653137 Limited company (AS) Vågan Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 14.2m
Operating profit NOK 1.2m
Equity NOK 30,000
Incorporated 2022
Employees 20
Share capital NOK 30,000

KLATREKAFEEN AS is registered as a limited company in Vågan, Nordland with organisation number 928653137. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2022 and has 20 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Drifte serveringssted samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 14.2m in revenue and NOK 1.2m in operating profit.

Key figures · 2025

Revenue
NOK 14.2m
▲ +25 %
Operating profit
NOK 1.2m
▲ +6 %
Equity
NOK 30,000
▲ +0 %
Est. value
NOK 4.1m

Financial health · 2025

Liquidity
0.15
Not satisfactory
Current assets ÷ current liabilities
Profitability
36.0%
Very good
Return on total assets
Solidity
0.8%
Weak
Equity as a share of total capital

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

Who owns KLATREKAFEEN AS?

KLATREKAFEEN AS
NOK 14.2m rev. · NOK 1.2m profit

KLATREKAFEEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KLATREKAFEEN AS

Who owns KLATREKAFEEN AS?

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

What is the revenue of KLATREKAFEEN AS?

KLATREKAFEEN AS had revenue of NOK 14.2m in 2025.

Who is the general manager of KLATREKAFEEN AS?

Remi Andre Mjelde is registered as general manager of KLATREKAFEEN AS.

Where is KLATREKAFEEN AS based?

KLATREKAFEEN AS has its business address in Henningsvær.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.