BIZTRAC BETA
Rental and operating of own or leased real estate

TT EIENDOM MYRE AS

Org. no. 935685036 Limited company (AS) Øksnes Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 603,000
Operating profit NOK −455,000
Equity NOK 1.1m
Incorporated 2025
Share capital NOK 1.5m

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−455k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

TT EIENDOM MYRE AS is registered as a limited company in Øksnes, Nordland with organisation number 935685036. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2025. Registered share capital is NOK 1.5m, divided into 5100 shares. The company's stated purpose is: “Kjøp, salg, utvikling og utleie av fast eiendom, samt alt som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 603,000 in revenue and NOK −455,000 in operating profit.

Key figures · 2025

Revenue
NOK 603,000
Operating profit
NOK −455,000
Equity
NOK 1.1m
Est. value
NOK 1.3m

Financial health · 2025

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

Who owns TT EIENDOM MYRE AS?

TT-HOLDING AS
TT EIENDOM MYRE AS
NOK 603,000 rev. · NOK −455,000 profit

TT EIENDOM MYRE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TT EIENDOM MYRE AS

Who owns TT EIENDOM MYRE AS?

TT-HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of TT EIENDOM MYRE AS?

TT EIENDOM MYRE AS had revenue of NOK 603,000 in 2025.

Where is TT EIENDOM MYRE AS based?

TT EIENDOM MYRE AS has its business address in Myre.

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.