BIZTRAC BETA
Development of building projects

STORSAND HOLDING AS

Org. no. 989263951 Limited company (AS) Melhus Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −9,000
Equity NOK −554,000
Incorporated 2005
Share capital NOK 100,000

Signals

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

STORSAND HOLDING AS is registered as a limited company in Melhus, Trøndelag with organisation number 989263951. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Utvikling og salg av egen fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −9,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −9,000
Equity
NOK −554,000

Financial health · 2024

Liquidity
11.94
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-55.5%
Weak
Equity as a share of total capital

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

Who owns STORSAND HOLDING AS?

ARNE NJØS
STORSAND HOLDING AS
NOK 0 rev. · NOK −9,000 profit

STORSAND HOLDING AS has 5 registered shareholders:

All shareholders and roles →

Which companies does STORSAND HOLDING AS own?

STORSAND HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about STORSAND HOLDING AS

Who owns STORSAND HOLDING AS?

ARNE NJØS is the largest registered owner, with 26.0%.

What is the revenue of STORSAND HOLDING AS?

STORSAND HOLDING AS had revenue of NOK 0 in 2024.

Where is STORSAND HOLDING AS based?

STORSAND HOLDING 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.