BIZTRAC BETA
Manufacture of other builders' carpentry and joinery

TREECON AS

Org. no. 984162901 Limited company (AS) Namsos Incorporated 2001 Active
Ownership graph ↗
Revenue 2024 NOK 15.8m
Operating profit NOK −7.7m
Equity NOK 13.2m
Incorporated 2001
Employees 13
Share capital NOK 14.8m

Signals

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

TREECON AS is registered as a limited company in Namsos, Trøndelag with organisation number 984162901. The business is classified under manufacture of other builders' carpentry and joinery (NACE 16.230). The company was incorporated in 2001 and has 13 registered employees. Registered share capital is NOK 14.8m, divided into 329345 shares. The company's stated purpose is: “Trevareindustri, kjøp og salg av varer og tjenester og virksomhet forbundet med dette. Selskapet kan som eier eller deltaker ha interesser i andre foretak.”. The most recent filed accounts, for the 2024 financial year, show NOK 15.8m in revenue and NOK −7.7m in operating profit.

Key figures · 2024

Revenue
NOK 15.8m
Operating profit
NOK −7.7m
Equity
NOK 13.2m
Est. value
NOK 7.3m

Financial health · 2024

Liquidity
0.72
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
35.6%
Good
Equity as a share of total capital

Who owns TREECON AS?

HØKNES EIENDOM AS
TREECON AS
NOK 15.8m rev. · NOK −7.7m profit

TREECON AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about TREECON AS

Who owns TREECON AS?

HØKNES EIENDOM AS is the largest registered owner, with 31.4%.

What is the revenue of TREECON AS?

TREECON AS had revenue of NOK 15.8m in 2024.

Who is the general manager of TREECON AS?

Ole Kristoffer Larsen is registered as general manager of TREECON AS.

Where is TREECON AS based?

TREECON AS has its business address in Namsos.

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.