BIZTRAC BETA
Site preparation

TM ANLEGG AS

Org. no. 918840745 Limited company (AS) Kvinnherad Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 26.6m
Operating profit NOK 2.6m
Equity NOK 7.4m
Incorporated 2017
Employees 11
Share capital NOK 30,000

Signals

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

TM ANLEGG AS is registered as a limited company in Kvinnherad, Vestland with organisation number 918840745. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2017 and has 11 registered employees. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Arbeid innen grunnarbeide og betong Sjøarbeide med slepebåt og lekter- Kjøp og salg av maskiner og utstyr. Verksted av lannbruksredskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 26.6m in revenue and NOK 2.6m in operating profit.

Key figures · 2024

Revenue
NOK 26.6m
Operating profit
NOK 2.6m
Equity
NOK 7.4m
Est. value
NOK 12.6m

Financial health · 2024

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

Who owns TM ANLEGG AS?

TM EIGENDOM AS
TM ANLEGG AS
NOK 26.6m rev. · NOK 2.6m profit

TM ANLEGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TM ANLEGG AS

Who owns TM ANLEGG AS?

TM EIGENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of TM ANLEGG AS?

TM ANLEGG AS had revenue of NOK 26.6m in 2024.

Who is the general manager of TM ANLEGG AS?

Robert Myklebust is registered as general manager of TM ANLEGG AS.

Where is TM ANLEGG AS based?

TM ANLEGG AS has its business address in Herøysundet.

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.