BIZTRAC BETA
Work training and permanently adapted work

INKO AS

Org. no. 928731022 Limited company (AS) Harstad Incorporated 1964 Active
Ownership graph ↗
Revenue 2024 NOK 40.4m
Operating profit NOK 607,000
Equity NOK 21.6m
Incorporated 1964
Employees 29
Share capital NOK 828,000

INKO AS is registered as a limited company in Harstad, Troms with organisation number 928731022. The business is classified under work training and permanently adapted work (NACE 88.993). The company was incorporated in 1964 and has 29 registered employees. Registered share capital is NOK 828,000, divided into 3310 shares. The company's stated purpose is: “Sørge for at våre deltakere får prekvalifisering og nødvendig og målrettet kompetanseheving som fører til jobb. Målet skal være ordinær jobb, eller tilrettelagt arbeid. Dette skal vi gjøre gjennom veiledning, oppfølging og arbeidstrening. Selskapet skal også gi tilbud om fast arbeid til arbeidstakere som har mindre muligheter til å få fast arbeid i det ordinære arbeidsmarkedet.”. The most recent filed accounts, for the 2024 financial year, show NOK 40.4m in revenue and NOK 607,000 in operating profit.

Key figures · 2024

Revenue
NOK 40.4m
Operating profit
NOK 607,000
Equity
NOK 21.6m
Est. value
NOK 16.9m

Financial health · 2024

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

Who owns INKO AS?

No shareholders are registered for INKO AS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about INKO AS

What is the revenue of INKO AS?

INKO AS had revenue of NOK 40.4m in 2024.

Who is the general manager of INKO AS?

Annette Ekman is registered as general manager of INKO AS.

Where is INKO AS based?

INKO AS has its business address in Harstad.

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.