BIZTRAC BETA
Rental and operating of own or leased real estate

TRONDHEIM HELSEBYGG AS

Org. no. 996263088 Limited company (AS) Oslo Incorporated 2010 Active
Ownership graph ↗
Revenue 2025 NOK 25.6m
Operating profit NOK 18.2m
Equity NOK 188.0m
Incorporated 2010
Share capital NOK 2.0m

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

TRONDHEIM HELSEBYGG AS is registered as a limited company in Oslo, Oslo with organisation number 996263088. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2010. Registered share capital is NOK 2.0m, divided into 1000 shares. The company's stated purpose is: “Investere i fast eiendom eller selskaper som eier fast eiendom, og alt som dermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 25.6m in revenue and NOK 18.2m in operating profit.

Key figures · 2025

Revenue
NOK 25.6m
Operating profit
NOK 18.2m
Equity
NOK 188.0m
Est. value
NOK 173.1m

Financial health · 2025

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

Who owns TRONDHEIM HELSEBYGG AS?

TRONDHEIM HELSEBYGG HOLDING AS
TRONDHEIM HELSEBYGG AS
NOK 25.6m rev. · NOK 18.2m profit

TRONDHEIM HELSEBYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TRONDHEIM HELSEBYGG AS

Who owns TRONDHEIM HELSEBYGG AS?

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

What is the revenue of TRONDHEIM HELSEBYGG AS?

TRONDHEIM HELSEBYGG AS had revenue of NOK 25.6m in 2025.

Where is TRONDHEIM HELSEBYGG AS based?

TRONDHEIM HELSEBYGG AS has its business address in Oslo.

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.