BIZTRAC BETA
Rental and operating of own or leased real estate

MULTISTORAGE AS

Org. no. 989557645 Limited company (AS) Halden Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 40,000
Operating profit NOK −278,000
Equity NOK −288,000
Incorporated 2006
Share capital NOK 100,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−288k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−278k kr).

MULTISTORAGE AS is registered as a limited company in Halden, Østfold with organisation number 989557645. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2006. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Kjøp, salg og utleie av fast eiendom. Lagerutleie, vaktmestertjenester, økonomitjenester og alt som hører naturlig til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 40,000 in revenue and NOK −278,000 in operating profit.

Key figures · 2024

Revenue
NOK 40,000
Operating profit
NOK −278,000
Equity
NOK −288,000

Financial health · 2024

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

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

Who owns MULTISTORAGE AS?

KENNETH TORGALSBØEN
MULTISTORAGE AS
NOK 40,000 rev. · NOK −278,000 profit

MULTISTORAGE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about MULTISTORAGE AS

Who owns MULTISTORAGE AS?

KENNETH TORGALSBØEN is the largest registered owner, with 50.0%.

What is the revenue of MULTISTORAGE AS?

MULTISTORAGE AS had revenue of NOK 40,000 in 2024.

Where is MULTISTORAGE AS based?

MULTISTORAGE AS has its business address in Tistedal.

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.