BIZTRAC BETA
Rental and operating of own or leased real estate

S.TORV 8 AS

Org. no. 889122722 Limited company (AS) Ringerike Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 2.0m
Operating profit NOK 538,000
Equity NOK −793,000
Incorporated 2005
Share capital NOK 2.0m

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−793k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

S.TORV 8 AS is registered as a limited company in Ringerike, Buskerud with organisation number 889122722. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2005. Registered share capital is NOK 2.0m, divided into 670 shares. The company's stated purpose is: “Engasjement i andre virksomheter, eie og drive fast eiendom samt salg av tjenester innenfor anleggsvirksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.0m in revenue and NOK 538,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.0m
Operating profit
NOK 538,000
Equity
NOK −793,000
Est. value
NOK 3.7m

Financial health · 2024

Liquidity
6.64
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-4.2%
Weak
Equity as a share of total capital

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

Who owns S.TORV 8 AS?

MURUDALEN AS
S.TORV 8 AS
NOK 2.0m rev. · NOK 538,000 profit

S.TORV 8 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about S.TORV 8 AS

Who owns S.TORV 8 AS?

MURUDALEN AS is the largest registered owner, with 100.0%.

What is the revenue of S.TORV 8 AS?

S.TORV 8 AS had revenue of NOK 2.0m in 2024.

Where is S.TORV 8 AS based?

S.TORV 8 AS has its business address in Hønefoss.

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.