biztrac. BETA
COMPANY REGISTER PROFILE
920178707 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

STASØ AS

Org. no. 920178707 Limited company (AS) Trondheim Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −116
Equity NOK 19,000
Incorporated 2017
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−116 kr).

STASØ AS is registered as a limited company in Trondheim, Trøndelag with organisation number 920178707. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selv, eller gjennom hel- eller deleide selskaper eller ved samarbeide med andre virksomheter, å forestå investeringsvirksomhet samt hva hermed står i naturlig forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −116 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −116
Equity
NOK 19,000
▼ −2 %
Est. value
NOK 22,000

Financial health · 2025

Liquidity
25.31
Very good
Current assets ÷ current liabilities
Profitability
-0.0%
Not satisfactory
Return on total assets
Solidity
0.8%
Weak
Equity as a share of total capital

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

Who owns STASØ AS?

STASØ AS
NOK 0 rev. · NOK −116 profit

STASØ AS has 2 registered shareholders:

All shareholders and roles →

Which companies does STASØ AS own?

STASØ AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about STASØ AS

Who owns STASØ AS?

Arne Stadsøy is the largest registered owner, with 50.0%.

What is the revenue of STASØ AS?

STASØ AS had revenue of NOK 0 in 2025.

Where is STASØ AS based?

STASØ 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 03.10.2026.

Report a problem

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