biztrac. BETA
COMPANY REGISTER PROFILE
989247956 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
In liquidation UPDATED 03.10.2026
⚠STORGT. 25 HOLDING AS is registered as “In liquidation” with the Brønnøysund Register Centre.
Other captive investment companies

STORGT. 25 HOLDING AS

Org. no. 989247956 Limited company (AS) Ålesund Incorporated 2005 In liquidation
Ownership graph ↗
Revenue 2025 NOK 21.9m
Operating profit NOK 20.5m
Equity NOK 357,000
Incorporated 2005
Share capital NOK 300,000

Signals

1 flags
  • Under avvikling Selskapet er under frivillig avvikling.

STORGT. 25 HOLDING AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 989247956. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2005. Registered share capital is NOK 300,000, divided into 300 shares. The company's stated purpose is: “Investere eller delta i andre selskap og det som følger naturlig av en slik deltakelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 21.9m in revenue and NOK 20.5m in operating profit.

Key figures · 2025

Revenue
NOK 21.9m
Operating profit
NOK 20.5m
▲ +51046 %
Equity
NOK 357,000
▼ −93 %

Financial health · 2025

Liquidity
1.01
Satisfactory
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
1.4%
Not satisfactory
Equity as a share of total capital

Who owns STORGT. 25 HOLDING AS?

STORGT. 25 HOLDING AS has 5 registered shareholders:

All shareholders and roles →

Frequently asked questions about STORGT. 25 HOLDING AS

Who owns STORGT. 25 HOLDING AS?

Anne Vibeke Flem is the largest registered owner, with 33.3%.

What is the revenue of STORGT. 25 HOLDING AS?

STORGT. 25 HOLDING AS had revenue of NOK 21.9m in 2025.

Where is STORGT. 25 HOLDING AS based?

STORGT. 25 HOLDING AS has its business address in Ålesund.

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.