BIZTRAC BETA
Rental and operating of own or leased real estate

TRONDHEIM NÆRINGSPARK AS

Org. no. 992540176 Limited company (AS) Trondheim Incorporated 2008 Active
Ownership graph ↗
Revenue 2024 NOK 22.3m
Operating profit NOK 11.8m
Equity NOK 39.6m
Incorporated 2008
Share capital NOK 3.0m

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

TRONDHEIM NÆRINGSPARK AS is registered as a limited company in Trondheim, Trøndelag with organisation number 992540176. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2008. Registered share capital is NOK 3.0m, divided into 96 shares. The company's stated purpose is: “Erverve, eie, utvikle og forvalte fast eiendom, aksjer og øvrige verdipapirer og virksomhet forbundet med det.”. The most recent filed accounts, for the 2024 financial year, show NOK 22.3m in revenue and NOK 11.8m in operating profit.

Key figures · 2024

Revenue
NOK 22.3m
Operating profit
NOK 11.8m
Equity
NOK 39.6m
Est. value
NOK 48.6m

Financial health · 2024

Liquidity
0.18
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
27.5%
Good
Equity as a share of total capital

Who owns TRONDHEIM NÆRINGSPARK AS?

R KJELDSBERG AS
TRONDHEIM NÆRINGSPARK AS
NOK 22.3m rev. · NOK 11.8m profit

TRONDHEIM NÆRINGSPARK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TRONDHEIM NÆRINGSPARK AS

Who owns TRONDHEIM NÆRINGSPARK AS?

R KJELDSBERG AS is the largest registered owner, with 100.0%.

What is the revenue of TRONDHEIM NÆRINGSPARK AS?

TRONDHEIM NÆRINGSPARK AS had revenue of NOK 22.3m in 2024.

Where is TRONDHEIM NÆRINGSPARK AS based?

TRONDHEIM NÆRINGSPARK 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.