BIZTRAC BETA
Freight transport by road

CO LINK AS

Org. no. 994698338 Limited company (AS) Trondheim Incorporated 2009 Active
Ownership graph ↗
Revenue 2025 NOK 2.1m
Operating profit NOK −577,000
Equity NOK −1.2m
Incorporated 2009
Share capital NOK 400,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−1,2 mill kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−577k kr).

CO LINK AS is registered as a limited company in Trondheim, Trøndelag with organisation number 994698338. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 2009. Registered share capital is NOK 400,000, divided into 4000 shares. The company's stated purpose is: “Internasjonal handel og transport av salgsvarer. Rådgivning samt tjenesteyting i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.1m in revenue and NOK −577,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.1m
Operating profit
NOK −577,000
Equity
NOK −1.2m

Financial health · 2025

Liquidity
0.06
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-506.3%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns CO LINK AS?

CHRISTIAN JOHANSEN
CO LINK AS
NOK 2.1m rev. · NOK −577,000 profit

CO LINK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about CO LINK AS

Who owns CO LINK AS?

CHRISTIAN JOHANSEN is the largest registered owner, with 100.0%.

What is the revenue of CO LINK AS?

CO LINK AS had revenue of NOK 2.1m in 2025.

Who is the general manager of CO LINK AS?

Christian Johansen is registered as general manager of CO LINK AS.

Where is CO LINK AS based?

CO LINK AS has its business address in Trondheim.

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.