BIZTRAC BETA
Wholesale of china and glassware and cleaning materials

KOKKENS BESTE AS

Org. no. 918456546 Limited company (AS) Lillehammer Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 2.8m
Operating profit NOK 210,000
Equity NOK 296,000
Incorporated 2017
Share capital NOK 30,000

KOKKENS BESTE AS is registered as a limited company in Lillehammer, Innlandet with organisation number 918456546. The business is classified under wholesale of china and glassware and cleaning materials (NACE 46.440). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Salg av kokke- og kjøkkenutstyr, salg av gave- og profileringsartikler, salg av klær og sko, bearbeidelse av matvarer og andre produkter/tjenester som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.8m in revenue and NOK 210,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.8m
Operating profit
NOK 210,000
Equity
NOK 296,000
Est. value
NOK 959,000

Financial health · 2024

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

Who owns KOKKENS BESTE AS?

SIGFRIED SOKOLLEK
KOKKENS BESTE AS
NOK 2.8m rev. · NOK 210,000 profit

KOKKENS BESTE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KOKKENS BESTE AS

Who owns KOKKENS BESTE AS?

SIGFRIED SOKOLLEK is the largest registered owner, with 100.0%.

What is the revenue of KOKKENS BESTE AS?

KOKKENS BESTE AS had revenue of NOK 2.8m in 2024.

Who is the general manager of KOKKENS BESTE AS?

Sigfried Sokollek is registered as general manager of KOKKENS BESTE AS.

Where is KOKKENS BESTE AS based?

KOKKENS BESTE AS has its business address in Fåberg.

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.