BIZTRAC BETA
Rental and operating of own or leased real estate

TORP KONTORINVEST AS

Org. no. 914093015 Limited company (AS) Drammen Incorporated 2014 Active
Ownership graph ↗
Operating profit NOK −22,000
Equity NOK 5.7m
Incorporated 2014
Share capital NOK 1.0m

Signals

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

TORP KONTORINVEST AS is registered as a limited company in Drammen, Buskerud with organisation number 914093015. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2014. Registered share capital is NOK 1.0m, divided into 10000 shares. The company's stated purpose is: “Eie samtlige aksjer i Nordre Kullerød 1 AS, org.nr. 990 760 063, hvis formål er å eie, drive og leie ut eiendommen i Nordre Kullerød 1 (gnr 34, bnr 101 i Sandefjord kommune), samt hva som står i forbindelse med dette.”.

Key figures · 2024

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

Financial health · 2024

Liquidity
0.08
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
9.2%
Weak
Equity as a share of total capital

Who owns TORP KONTORINVEST AS?

ORIGO EIENDOM AS
TORP KONTORINVEST AS
· NOK −22,000 profit

TORP KONTORINVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does TORP KONTORINVEST AS own?

TORP KONTORINVEST AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about TORP KONTORINVEST AS

Who owns TORP KONTORINVEST AS?

ORIGO EIENDOM AS is the largest registered owner, with 100.0%.

Who is the general manager of TORP KONTORINVEST AS?

Christer Pedersen is registered as general manager of TORP KONTORINVEST AS.

Where is TORP KONTORINVEST AS based?

TORP KONTORINVEST AS has its business address in Drammen.

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.