BIZTRAC BETA
Buying and selling of own real estate

TRH PROSJEKT AS

Org. no. 999607594 Limited company (AS) Trondheim Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK 222,000
Equity NOK 12.5m
Incorporated 2013
Share capital NOK 100,000

TRH PROSJEKT AS is registered as a limited company in Trondheim, Trøndelag with organisation number 999607594. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2013. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Eie og leie ut fast eiendom, prosjektutvikling, bygging og salg av fast eiendom, herunder å delta i andre selskap med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretak som kan fremme Trh Prosjekt AS virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK 222,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK 222,000
Equity
NOK 12.5m
Est. value
NOK 9.3m

Financial health · 2025

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

Who owns TRH PROSJEKT AS?

BISMAR INVEST AS
TRH PROSJEKT AS
NOK 0 rev. · NOK 222,000 profit

TRH PROSJEKT AS has 3 registered shareholders:

All shareholders and roles →

Which companies does TRH PROSJEKT AS own?

TRH PROSJEKT AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about TRH PROSJEKT AS

Who owns TRH PROSJEKT AS?

BISMAR INVEST AS is the largest registered owner, with 45.0%.

What is the revenue of TRH PROSJEKT AS?

TRH PROSJEKT AS had revenue of NOK 0 in 2025.

Where is TRH PROSJEKT AS based?

TRH PROSJEKT AS has its business address in Trondheim.

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.