biztrac. BETA
COMPANY REGISTER PROFILE
916021542 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Buying and selling of own real estate

INDUSTRITOPPEN INVEST AS

Org. no. 916021542 Limited company (AS) Froland Incorporated 2015 Active
Ownership graph ↗
Operating profit NOK −66,000
Equity NOK −19,000
Incorporated 2015
Share capital NOK 1.0m

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−19k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−66k kr).

INDUSTRITOPPEN INVEST AS is registered as a limited company in Froland, Agder with organisation number 916021542. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2015. Registered share capital is NOK 1.0m, divided into 1440 shares. The company's stated purpose is: “Eie og investering i aksjer og andre verdipapirer, kjøp og salg av fast eiendom, utvikling av fast eiendom, utleie av fast eiendom, samt alt som naturlig hører dertil.”.

Key figures · 2025

Operating profit
NOK −66,000
▼ −139 %
Equity
NOK −19,000
▼ −100 %

Financial health · 2025

Liquidity
0.84
Weak
Current assets ÷ current liabilities
Profitability
-1.7%
Not satisfactory
Return on total assets
Solidity
-19.6%
Weak
Equity as a share of total capital

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

Who owns INDUSTRITOPPEN INVEST AS?

INDUSTRITOPPEN INVEST AS has 5 registered shareholders:

All shareholders and roles →

Which companies does INDUSTRITOPPEN INVEST AS own?

INDUSTRITOPPEN INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about INDUSTRITOPPEN INVEST AS

Who owns INDUSTRITOPPEN INVEST AS?

Øystein Gauslå is the largest registered owner, with 50.0%.

Where is INDUSTRITOPPEN INVEST AS based?

INDUSTRITOPPEN INVEST AS has its business address in Froland.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.