BIZTRAC BETA
COMPANY REGISTER PROFILE
917628955 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Civil engineering activities

STORM AS

Org. no. 917628955 Limited company (AS) Moss Incorporated 1976 Active
Ownership graph ↗
Revenue 2025 NOK 54,000
Operating profit NOK −153,000
Equity NOK 164,000
Incorporated 1976
Share capital NOK 101,000

Signals

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

STORM AS is registered as a limited company in Moss, Østfold with organisation number 917628955. The business is classified under civil engineering activities (NACE 71.121). The company was incorporated in 1976. Registered share capital is NOK 101,000, divided into 4600 shares. The company's stated purpose is: “Å drive rådgivning og konsulentvirksomhet innenfor bygg og eiendom. Videre kjøp og salg av varer, eiendom og aksjer.”. The most recent filed accounts, for the 2025 financial year, show NOK 54,000 in revenue and NOK −153,000 in operating profit.

Key figures · 2025

Revenue
NOK 54,000
Operating profit
NOK −153,000
Equity
NOK 164,000
Est. value
NOK 137,000

Financial health · 2025

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

Who owns STORM AS?

RUNE ALFRED EHLERS ARNESEN
STORM AS
NOK 54,000 rev. · NOK −153,000 profit

STORM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STORM AS

Who owns STORM AS?

RUNE ALFRED EHLERS ARNESEN is the largest registered owner, with 100.0%.

What is the revenue of STORM AS?

STORM AS had revenue of NOK 54,000 in 2025.

Who is the general manager of STORM AS?

Rune Alfred Ehlers Arnesen is registered as general manager of STORM AS.

Where is STORM AS based?

STORM AS has its business address in Moss.

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.