BIZTRAC BETA
Other non-specialised retail sale

TOPPSPRAY AS

Org. no. 925748129 Limited company (AS) Ørland Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 3,000
Operating profit NOK −73,000
Equity NOK −74,000
Incorporated 2020
Share capital NOK 30,000

Signals

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

TOPPSPRAY AS is registered as a limited company in Ørland, Trøndelag with organisation number 925748129. The business is classified under other non-specialised retail sale (NACE 47.120). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Selskapets virksomhet er drive handelsvirksomhet innen rengjøring og beskyttelsesmidler.”. The most recent filed accounts, for the 2025 financial year, show NOK 3,000 in revenue and NOK −73,000 in operating profit.

Key figures · 2025

Revenue
NOK 3,000
Operating profit
NOK −73,000
Equity
NOK −74,000

Financial health · 2025

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

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

Who owns TOPPSPRAY AS?

AHI HOLDING AS
TOPPSPRAY AS
NOK 3,000 rev. · NOK −73,000 profit

TOPPSPRAY AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TOPPSPRAY AS

Who owns TOPPSPRAY AS?

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

What is the revenue of TOPPSPRAY AS?

TOPPSPRAY AS had revenue of NOK 3,000 in 2025.

Who is the general manager of TOPPSPRAY AS?

Arild Henry Instebø is registered as general manager of TOPPSPRAY AS.

Where is TOPPSPRAY AS based?

TOPPSPRAY AS has its business address in Brekstad.

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.