BIZTRAC BETA
Rental and operating of own or leased real estate

TORVGATA EIENDOM AS

Org. no. 990117004 Limited company (AS) Kragerø Incorporated 2006 Active
Ownership graph ↗
Operating profit NOK −44,000
Equity NOK 5.7m
Incorporated 2006
Share capital NOK 141,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−44k kr).

TORVGATA EIENDOM AS is registered as a limited company in Kragerø, Telemark with organisation number 990117004. 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 141,000, divided into 70463 shares. The company's stated purpose is: “Selv gjennom hel- eller deleide selskaper eller ved samarbeid med andre virksomheter å eie og forestå investeringer i aksjer og andre finansielle instrumenter, fast eiendom, kjøp og salg av fordringer og valuta og annen virksomhet beslektet med dette. Selskapet vil også drive med utleie av arbeidskraft i forbindelse med drift og vedlikehold av eiendommer.”.

Key figures · 2025

Operating profit
NOK −44,000
Equity
NOK 5.7m
Est. value
NOK 5.2m

Financial health · 2025

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

Who owns TORVGATA EIENDOM AS?

BJØRN UBERG ANDERSEN
TORVGATA EIENDOM AS
· NOK −44,000 profit

TORVGATA EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does TORVGATA EIENDOM AS own?

TORVGATA EIENDOM AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about TORVGATA EIENDOM AS

Who owns TORVGATA EIENDOM AS?

BJØRN UBERG ANDERSEN is the largest registered owner, with 100.0%.

Where is TORVGATA EIENDOM AS based?

TORVGATA EIENDOM AS has its business address in Kragerø.

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.