BIZTRAC BETA
Business and other management consultancy activities

KONGSBERG KLYNGEN AS

Org. no. 981117735 Limited company (AS) Kongsberg Incorporated 1999 Active
Ownership graph ↗
Revenue 2024 NOK 8.2m
Operating profit NOK −17,000
Equity NOK 836,000
Incorporated 1999
Share capital NOK 110,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−17k kr).

KONGSBERG KLYNGEN AS is registered as a limited company in Kongsberg, Buskerud with organisation number 981117735. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 1999. Registered share capital is NOK 110,000, divided into 100 shares. The company's stated purpose is: “Drive virksomhet på vegne av Kongsberg Innovasjon AS i forbindelse med prosjekter innen regional næringsutvikling og markedsføring, samt det som naturlig hører sammen med slik virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 8.2m in revenue and NOK −17,000 in operating profit.

Key figures · 2024

Revenue
NOK 8.2m
Operating profit
NOK −17,000
Equity
NOK 836,000
Est. value
NOK 9.1m

Financial health · 2024

Liquidity
1.40
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
29.3%
Good
Equity as a share of total capital

Who owns KONGSBERG KLYNGEN AS?

KONGSBERG INNOVASJON AS
KONGSBERG KLYNGEN AS
NOK 8.2m rev. · NOK −17,000 profit

KONGSBERG KLYNGEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KONGSBERG KLYNGEN AS

Who owns KONGSBERG KLYNGEN AS?

KONGSBERG INNOVASJON AS is the largest registered owner, with 100.0%.

What is the revenue of KONGSBERG KLYNGEN AS?

KONGSBERG KLYNGEN AS had revenue of NOK 8.2m in 2024.

Where is KONGSBERG KLYNGEN AS based?

KONGSBERG KLYNGEN 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.