BIZTRAC BETA
Development of building projects

LINKPRO AS

Org. no. 916376162 Limited company (AS) Bodø Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 1.9m
Operating profit NOK −2.2m
Equity NOK 21.2m
Incorporated 2015
Share capital NOK 650,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−2,2 mill kr).

LINKPRO AS is registered as a limited company in Bodø, Nordland with organisation number 916376162. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2015. Registered share capital is NOK 650,000, divided into 26000 shares. The company's stated purpose is: “Å forestå tomteerverv, tomte og prosjektutvikling, samt prosjekt og byggeledelse knyttet til boligvirksomhet og beslektet virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.9m in revenue and NOK −2.2m in operating profit.

Key figures · 2024

Revenue
NOK 1.9m
Operating profit
NOK −2.2m
Equity
NOK 21.2m
Est. value
NOK 17.0m

Financial health · 2024

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

Who owns LINKPRO AS?

TE HOLDING AS
LINKPRO AS
NOK 1.9m rev. · NOK −2.2m profit

LINKPRO AS has 3 registered shareholders:

All shareholders and roles →

Which companies does LINKPRO AS own?

LINKPRO AS holds stakes in 7 companies:

See the full ownership structure →

Frequently asked questions about LINKPRO AS

Who owns LINKPRO AS?

TE HOLDING AS is the largest registered owner, with 78.5%.

What is the revenue of LINKPRO AS?

LINKPRO AS had revenue of NOK 1.9m in 2024.

Who is the general manager of LINKPRO AS?

Thor Sandfred Ekhorn is registered as general manager of LINKPRO AS.

Where is LINKPRO AS based?

LINKPRO AS has its business address in Bodø.

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.