BIZTRAC BETA
Restaurant activities

KJAPPEN VOSS AS

Org. no. 915298362 Limited company (AS) Voss Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 2.9m
Operating profit NOK 363,000
Equity NOK 721,000
Incorporated 2015
Share capital NOK 30,000

KJAPPEN VOSS AS is registered as a limited company in Voss, Vestland with organisation number 915298362. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Handel, serveringstjenester, tjenesteyting, samt ved aksjetegning eller annan måte å delta i andre selskap med liknande formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.9m in revenue and NOK 363,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.9m
Operating profit
NOK 363,000
Equity
NOK 721,000
Est. value
NOK 1.7m

Financial health · 2025

Liquidity
0.49
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
41.8%
Very good
Equity as a share of total capital

Who owns KJAPPEN VOSS AS?

KAMIL LUDWICZAK
KJAPPEN VOSS AS
NOK 2.9m rev. · NOK 363,000 profit

KJAPPEN VOSS AS has 2 registered shareholders:

All shareholders and roles →

Which companies does KJAPPEN VOSS AS own?

KJAPPEN VOSS AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about KJAPPEN VOSS AS

Who owns KJAPPEN VOSS AS?

KAMIL LUDWICZAK is the largest registered owner, with 50.0%.

What is the revenue of KJAPPEN VOSS AS?

KJAPPEN VOSS AS had revenue of NOK 2.9m in 2025.

Who is the general manager of KJAPPEN VOSS AS?

Jacek Piotr Kujawski is registered as general manager of KJAPPEN VOSS AS.

Where is KJAPPEN VOSS AS based?

KJAPPEN VOSS AS has its business address in Voss.

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.