BIZTRAC BETA
Rental and operating of own or leased real estate

TOPPEN INDUSTRIPARK 10 AS

Org. no. 916459149 Limited company (AS) Kongsberg Incorporated 2015 Active
Ownership graph ↗
Equity NOK 98,000
Incorporated 2015
Share capital NOK 85,000

Signals

2 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.
  • Nylig endring 2026-02-21 Adresseendring registrert 2026-02-21.

TOPPEN INDUSTRIPARK 10 AS is registered as a limited company in Kongsberg, Buskerud with organisation number 916459149. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2015. Registered share capital is NOK 85,000, divided into 84588 shares. The company's stated purpose is: “Eie, drive og utvikle fast eiendom med dertil tilhørende virksomhet.”.

Key figures · 2025

Equity
NOK 98,000
Est. value
NOK 89,000

Financial health · 2025

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

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

Who owns TOPPEN INDUSTRIPARK 10 AS?

KONGSBERG EIENDOMSSELSKAP HOLDING AS
TOPPEN INDUSTRIPARK 10 AS

TOPPEN INDUSTRIPARK 10 AS has 1 registered shareholder:

All shareholders and roles →

Group structure

TOPPEN INDUSTRIPARK 10 AS er morselskap for 10 datterselskaper:

Frequently asked questions about TOPPEN INDUSTRIPARK 10 AS

Who owns TOPPEN INDUSTRIPARK 10 AS?

KONGSBERG EIENDOMSSELSKAP HOLDING AS is the largest registered owner, with 100.0%.

Who is the general manager of TOPPEN INDUSTRIPARK 10 AS?

Nicolay Hostvedt Spiten is registered as general manager of TOPPEN INDUSTRIPARK 10 AS.

Where is TOPPEN INDUSTRIPARK 10 AS based?

TOPPEN INDUSTRIPARK 10 AS has its business address in Kongsberg.

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.