BIZTRAC BETA
Rental and operating of own or leased real estate

TT EIENDOM HADSEL AS

Org. no. 991112626 Limited company (AS) Vestvågøy Incorporated 2007 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −958,000
Equity NOK 9.1m
Incorporated 2007
Share capital NOK 100,000

Signals

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

TT EIENDOM HADSEL AS is registered as a limited company in Vestvågøy, Nordland with organisation number 991112626. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2007. Registered share capital is NOK 100,000, divided into 528 shares. The company's stated purpose is: “Kjøp, salg og utleie av eiendom samt å eie i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −958,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −958,000
Equity
NOK 9.1m
Est. value
NOK 8.3m

Financial health · 2025

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

Who owns TT EIENDOM HADSEL AS?

BREKKEN EIENDOM AS
TT EIENDOM HADSEL AS
NOK 0 rev. · NOK −958,000 profit

TT EIENDOM HADSEL AS has 1 registered shareholder:

All shareholders and roles →

Which companies does TT EIENDOM HADSEL AS own?

TT EIENDOM HADSEL AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about TT EIENDOM HADSEL AS

Who owns TT EIENDOM HADSEL AS?

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

What is the revenue of TT EIENDOM HADSEL AS?

TT EIENDOM HADSEL AS had revenue of NOK 0 in 2025.

Where is TT EIENDOM HADSEL AS based?

TT EIENDOM HADSEL AS has its business address in Stamsund.

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.