BIZTRAC BETA
Other technical consultancy

KAMTEK AS

Org. no. 917506345 Limited company (AS) Lillestrøm Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 24.8m
Operating profit NOK 2.3m
Equity NOK 4.3m
Incorporated 2016
Share capital NOK 30,000

KAMTEK AS is registered as a limited company in Lillestrøm, Akershus with organisation number 917506345. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Import, distribusjon, samt konsulentvirksomhet innen sikkerhetsteknologi og løsninger og andre tjenester og produkter som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender samt kjøp, salg og utleie av fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 24.8m in revenue and NOK 2.3m in operating profit.

Key figures · 2024

Revenue
NOK 24.8m
Operating profit
NOK 2.3m
Equity
NOK 4.3m
Est. value
NOK 13.6m

Financial health · 2024

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

Who owns KAMTEK AS?

JOAKIM SPILHAUG TORKILDSEN
KAMTEK AS
NOK 24.8m rev. · NOK 2.3m profit

KAMTEK AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about KAMTEK AS

Who owns KAMTEK AS?

JOAKIM SPILHAUG TORKILDSEN is the largest registered owner, with 50.0%.

What is the revenue of KAMTEK AS?

KAMTEK AS had revenue of NOK 24.8m in 2024.

Who is the general manager of KAMTEK AS?

Kato Lystad is registered as general manager of KAMTEK AS.

Where is KAMTEK AS based?

KAMTEK AS has its business address in Skedsmokorset.

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.