BIZTRAC BETA
Manufacture of other special-purpose machinery n.e.c.

DELITEK AS

Org. no. 963864019 Limited company (AS) Øksnes Incorporated 1992 Active
Ownership graph ↗
Revenue 2024 NOK 39.0m
Operating profit NOK 4.4m
Equity NOK 17.2m
Incorporated 1992
Employees 19
Share capital NOK 100,000

DELITEK AS is registered as a limited company in Øksnes, Nordland with organisation number 963864019. The business is classified under manufacture of other special-purpose machinery n.e.c. (NACE 28.990). The company was incorporated in 1992 and has 19 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Drive produktutvikling, produksjon av produkter til industri, skip, offshore og beslektede virksomheter, samt handel.”. The most recent filed accounts, for the 2024 financial year, show NOK 39.0m in revenue and NOK 4.4m in operating profit.

Key figures · 2024

Revenue
NOK 39.0m
Operating profit
NOK 4.4m
Equity
NOK 17.2m
Est. value
NOK 26.9m

Financial health · 2024

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

Who owns DELITEK AS?

BJØRN IVAR LARSEN
DELITEK AS
NOK 39.0m rev. · NOK 4.4m profit

DELITEK AS has 3 registered shareholders:

All shareholders and roles →

Which companies does DELITEK AS own?

DELITEK AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about DELITEK AS

Who owns DELITEK AS?

BJØRN IVAR LARSEN is the largest registered owner, with 35.0%.

What is the revenue of DELITEK AS?

DELITEK AS had revenue of NOK 39.0m in 2024.

Who is the general manager of DELITEK AS?

Bjørn Ivar Larsen is registered as general manager of DELITEK AS.

Where is DELITEK AS based?

DELITEK AS has its business address in Alsvåg.

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.