BIZTRAC BETA
Retail sale of household articles and equipment n.e.c.

KONGSBERG KJØKKENSENTER AS

Org. no. 982794935 Limited company (AS) Kongsberg Incorporated 2000 Active
Ownership graph ↗
Revenue 2024 NOK 8.9m
Operating profit NOK 29,000
Equity NOK 3.1m
Incorporated 2000
Share capital NOK 100,000

KONGSBERG KJØKKENSENTER AS is registered as a limited company in Kongsberg, Buskerud with organisation number 982794935. The business is classified under retail sale of household articles and equipment n.e.c. (NACE 47.559). The company was incorporated in 2000. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Salg av kjøkkeninnredning, hvitevarer, garderober, bad, samt deltagelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 8.9m in revenue and NOK 29,000 in operating profit.

Key figures · 2024

Revenue
NOK 8.9m
Operating profit
NOK 29,000
Equity
NOK 3.1m
Est. value
NOK 1.6m

Financial health · 2024

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

Who owns KONGSBERG KJØKKENSENTER AS?

JAN BRÅTEN
KONGSBERG KJØKKENSENTER AS
NOK 8.9m rev. · NOK 29,000 profit

KONGSBERG KJØKKENSENTER AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about KONGSBERG KJØKKENSENTER AS

Who owns KONGSBERG KJØKKENSENTER AS?

JAN BRÅTEN is the largest registered owner, with 66.0%.

What is the revenue of KONGSBERG KJØKKENSENTER AS?

KONGSBERG KJØKKENSENTER AS had revenue of NOK 8.9m in 2024.

Who is the general manager of KONGSBERG KJØKKENSENTER AS?

Jan Bråten is registered as general manager of KONGSBERG KJØKKENSENTER AS.

Where is KONGSBERG KJØKKENSENTER AS based?

KONGSBERG KJØKKENSENTER AS has its business address in Kongsberg.

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.