BIZTRAC BETA
Other technical consultancy

COBITEK AS

Org. no. 922285578 Limited company (AS) Modum Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 11.4m
Operating profit NOK 398,000
Equity NOK 2.0m
Incorporated 2019
Employees 8
Share capital NOK 30,000

COBITEK AS is registered as a limited company in Modum, Buskerud with organisation number 922285578. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2019 and has 8 registered employees. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Bidra til at norsk industri fortsatt kan være konkurransekraftig og innovativ. Vi vil med vår brede erfaring innen automasjon og robotteknologi ta industrien til et nytt nivå. Vedlikeholds oppfølgning og engineering vil også være en viktig faktor for industrien fremover. Og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 11.4m in revenue and NOK 398,000 in operating profit.

Key figures · 2025

Revenue
NOK 11.4m
Operating profit
NOK 398,000
Equity
NOK 2.0m
Est. value
NOK 2.9m

Financial health · 2025

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

Who owns COBITEK AS?

KHN-HOLDING AS
COBITEK AS
NOK 11.4m rev. · NOK 398,000 profit

COBITEK AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about COBITEK AS

Who owns COBITEK AS?

KHN-HOLDING AS is the largest registered owner, with 50.0%.

What is the revenue of COBITEK AS?

COBITEK AS had revenue of NOK 11.4m in 2025.

Who is the general manager of COBITEK AS?

Stig Hølen is registered as general manager of COBITEK AS.

Where is COBITEK AS based?

COBITEK AS has its business address in Vikersund.

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.