BIZTRAC BETA
Buying and selling of own real estate

TORVEN EIENDOM AS

Org. no. 915214169 Limited company (AS) Trondheim Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −55,000
Equity NOK 139,000
Incorporated 2015
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−55k kr).

TORVEN EIENDOM AS is registered as a limited company in Trondheim, Trøndelag with organisation number 915214169. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Kjøp, salg og utvikling og utleie av fast eiendom, samt hva hermed står i forbindelse. Selskapet kan i tillegg foreta investeringer i andre selskap.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −55,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −55,000
Equity
NOK 139,000
Est. value
NOK 127,000

Financial health · 2024

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

Who owns TORVEN EIENDOM AS?

TORVEN HOLDING AS
TORVEN EIENDOM AS
NOK 0 rev. · NOK −55,000 profit

TORVEN EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TORVEN EIENDOM AS

Who owns TORVEN EIENDOM AS?

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

What is the revenue of TORVEN EIENDOM AS?

TORVEN EIENDOM AS had revenue of NOK 0 in 2024.

Who is the general manager of TORVEN EIENDOM AS?

Kjetil Ulstad is registered as general manager of TORVEN EIENDOM AS.

Where is TORVEN EIENDOM AS based?

TORVEN EIENDOM AS has its business address in Klæbu.

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.