BIZTRAC BETA
Business and other management consultancy activities

F STORM AS

Org. no. 988120316 Limited company (AS) Sandnes Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 1.4m
Operating profit NOK −1.4m
Equity NOK 51.8m
Incorporated 2005
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1,4 mill kr).

F STORM AS is registered as a limited company in Sandnes, Rogaland with organisation number 988120316. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Konsulentbistand innen forretningsrådgivning, opplæringskonsulent, investeringsvirksomhet, eiendomsutvikling og drift av eiendom og agenturvirksomhet, og hva hermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.4m in revenue and NOK −1.4m in operating profit.

Key figures · 2024

Revenue
NOK 1.4m
Operating profit
NOK −1.4m
Equity
NOK 51.8m
Est. value
NOK 40.0m

Financial health · 2024

Liquidity
4.09
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
87.6%
Very good
Equity as a share of total capital

Who owns F STORM AS?

FRANK LOHNE STORM
F STORM AS
NOK 1.4m rev. · NOK −1.4m profit

F STORM AS has 4 registered shareholders:

All shareholders and roles →

Which companies does F STORM AS own?

F STORM AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about F STORM AS

Who owns F STORM AS?

FRANK LOHNE STORM is the largest registered owner, with 30.0%.

What is the revenue of F STORM AS?

F STORM AS had revenue of NOK 1.4m in 2024.

Where is F STORM AS based?

F STORM AS has its business address in Sandnes.

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.