BIZTRAC BETA
Development of building projects

THAMSHAVN NÆRINGSPARK AS

Org. no. 928616916 Limited company (AS) Melhus Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 120,000
Operating profit NOK −32,000
Equity NOK −289,000
Incorporated 2021
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−289k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−32k kr).

THAMSHAVN NÆRINGSPARK AS is registered as a limited company in Melhus, Trøndelag with organisation number 928616916. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Utvikling av eiendom, samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 120,000 in revenue and NOK −32,000 in operating profit.

Key figures · 2024

Revenue
NOK 120,000
Operating profit
NOK −32,000
Equity
NOK −289,000

Financial health · 2024

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

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

Who owns THAMSHAVN NÆRINGSPARK AS?

ARJO INVEST AS
THAMSHAVN NÆRINGSPARK AS
NOK 120,000 rev. · NOK −32,000 profit

THAMSHAVN NÆRINGSPARK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about THAMSHAVN NÆRINGSPARK AS

Who owns THAMSHAVN NÆRINGSPARK AS?

ARJO INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of THAMSHAVN NÆRINGSPARK AS?

THAMSHAVN NÆRINGSPARK AS had revenue of NOK 120,000 in 2024.

Where is THAMSHAVN NÆRINGSPARK AS based?

THAMSHAVN NÆRINGSPARK AS has its business address in Melhus.

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.