BIZTRAC BETA
Rental and operating of own or leased real estate

TORSTENSRUD EIENDOM AS

Org. no. 932477041 Limited company (AS) Horten Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 258,000
Operating profit NOK 35,000
Equity NOK −113,000
Incorporated 2023
Share capital NOK 30,000

Signals

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

TORSTENSRUD EIENDOM AS is registered as a limited company in Horten, Vestfold with organisation number 932477041. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Å kjøpe, selge, eie, leie ut, utvikle og drifte fast eiendom, samt eie aksjer og andeler i andre selskap.”. The most recent filed accounts, for the 2025 financial year, show NOK 258,000 in revenue and NOK 35,000 in operating profit.

Key figures · 2025

Revenue
NOK 258,000
Operating profit
NOK 35,000
Equity
NOK −113,000
Est. value
NOK 373,000

Financial health · 2025

Liquidity
0.19
Not satisfactory
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 TORSTENSRUD EIENDOM AS?

KEBET HOLDING AS
TORSTENSRUD EIENDOM AS
NOK 258,000 rev. · NOK 35,000 profit

TORSTENSRUD EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TORSTENSRUD EIENDOM AS

Who owns TORSTENSRUD EIENDOM AS?

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

What is the revenue of TORSTENSRUD EIENDOM AS?

TORSTENSRUD EIENDOM AS had revenue of NOK 258,000 in 2025.

Where is TORSTENSRUD EIENDOM AS based?

TORSTENSRUD EIENDOM AS has its business address in Horten.

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.