BIZTRAC BETA
Development of building projects

TROMS HUS AS

Org. no. 871168512 Limited company (AS) Tromsø Incorporated 1994 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −53,000
Equity NOK 3.1m
Incorporated 1994
Share capital NOK 1.0m

Signals

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

TROMS HUS AS is registered as a limited company in Tromsø, Troms with organisation number 871168512. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 1994. Registered share capital is NOK 1.0m, divided into 1010 shares. The company's stated purpose is: “Kjøp og salg av tomter, utvikling og utbygging av tomteområder med boliger, utleieboliger, forretningsbygg o.l., samt annen virksomhet som faller naturlig inn under dette. Selskapet kan delta i andre virksomheter i samme eller lignende bransje.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −53,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −53,000
Equity
NOK 3.1m
Est. value
NOK 2.8m

Financial health · 2024

Liquidity
0.48
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
12.1%
Satisfactory
Equity as a share of total capital

Who owns TROMS HUS AS?

TOVI AS
TROMS HUS AS
NOK 0 rev. · NOK −53,000 profit

TROMS HUS AS has 2 registered shareholders:

All shareholders and roles →

Which companies does TROMS HUS AS own?

TROMS HUS AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about TROMS HUS AS

Who owns TROMS HUS AS?

TOVI AS is the largest registered owner, with 50.0%.

What is the revenue of TROMS HUS AS?

TROMS HUS AS had revenue of NOK 0 in 2024.

Where is TROMS HUS AS based?

TROMS HUS AS has its business address in Tromsø.

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.