BIZTRAC BETA
Other investment companies, except captive companies

INAK 3 AS

Org. no. 912801268 Limited company (AS) Tønsberg Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 12.0m
Operating profit NOK 9.8m
Equity NOK 217.6m
Incorporated 2013
Share capital NOK 501,000

INAK 3 AS is registered as a limited company in Tønsberg, Vestfold with organisation number 912801268. The business is classified under other investment companies, except captive companies (NACE 64.312). The company was incorporated in 2013. Registered share capital is NOK 501,000, divided into 501 shares. The company's stated purpose is: “Investeringsselskap å investere i Norge og de øvrige nordiske land i form av noterte og unoterte aksjer, konvertible og ansvarlige lån samt andre tilsvarende instrumenter, herunder derivater.”. The most recent filed accounts, for the 2024 financial year, show NOK 12.0m in revenue and NOK 9.8m in operating profit.

Key figures · 2024

Revenue
NOK 12.0m
Operating profit
NOK 9.8m
Equity
NOK 217.6m
Est. value
NOK 149.1m

Financial health · 2024

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

Who owns INAK 3 AS?

TTC INVEST AS
INAK 3 AS
NOK 12.0m rev. · NOK 9.8m profit

INAK 3 AS has 11 registered shareholders:

All shareholders and roles →

Which companies does INAK 3 AS own?

INAK 3 AS holds stakes in 6 companies:

See the full ownership structure →

Frequently asked questions about INAK 3 AS

Who owns INAK 3 AS?

TTC INVEST AS is the largest registered owner, with 20.0%.

What is the revenue of INAK 3 AS?

INAK 3 AS had revenue of NOK 12.0m in 2024.

Who is the general manager of INAK 3 AS?

Bjørnar Olsen is registered as general manager of INAK 3 AS.

Where is INAK 3 AS based?

INAK 3 AS has its business address in Tønsberg.

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.