BIZTRAC BETA
COMPANY REGISTER PROFILE
934907930 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 25.08.2026
Uoppgitt

S. STORØY INVEST AS

Org. no. 934907930 Limited company (AS) Trondheim Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK 0
Equity NOK 24,000
Incorporated 2025
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-04-02 Adresseendring registrert 2026-04-02.

S. STORØY INVEST AS is registered as a limited company in Trondheim, Trøndelag with organisation number 934907930. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investere i, eie, forvalte og selge andeler i andre selskaper, samt å utøve aktiviteter som er komplementære til disse, inkludert, men ikke begrenset til, finansiell rådgivning og forvaltning.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 24,000
Est. value
NOK 28,000

Financial health · 2025

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

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

Who owns S. STORØY INVEST AS?

S. STORØY INVEST AS
NOK 0 rev. · NOK 0 profit

S. STORØY INVEST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about S. STORØY INVEST AS

Who owns S. STORØY INVEST AS?

SARA MARTINE HESTDAL STORØY is the largest registered owner, with 100.0%.

What is the revenue of S. STORØY INVEST AS?

S. STORØY INVEST AS had revenue of NOK 0 in 2025.

Where is S. STORØY INVEST AS based?

S. STORØY INVEST 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 25.08.2026.

Report a problem

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