BIZTRAC BETA
Rental and operating of own or leased real estate

SYVENDE STORAGE24 AS

Org. no. 897744562 Limited company (AS) Horten Incorporated 2011 Active
Ownership graph ↗
Revenue 2024 NOK 1.2m
Operating profit NOK 620,000
Equity NOK −266,000
Incorporated 2011
Share capital NOK 150,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−266k kr).

SYVENDE STORAGE24 AS is registered as a limited company in Horten, Vestfold with organisation number 897744562. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2011. Registered share capital is NOK 150,000, divided into 100 shares. The company's stated purpose is: “Kjøp, drift, salg og utleie av fast eiendom og det som står i forbindelse med dette, herunder å delta i andre selskaper med slikt formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.2m in revenue and NOK 620,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.2m
Operating profit
NOK 620,000
Equity
NOK −266,000
Est. value
NOK 2.6m

Financial health · 2024

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

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

Who owns SYVENDE STORAGE24 AS?

S24 NORWAY HOLDING AS
SYVENDE STORAGE24 AS
NOK 1.2m rev. · NOK 620,000 profit

SYVENDE STORAGE24 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SYVENDE STORAGE24 AS

Who owns SYVENDE STORAGE24 AS?

S24 NORWAY HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of SYVENDE STORAGE24 AS?

SYVENDE STORAGE24 AS had revenue of NOK 1.2m in 2024.

Where is SYVENDE STORAGE24 AS based?

SYVENDE STORAGE24 AS has its business address in Skoppum.

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.