BIZTRAC BETA
Site preparation

TM ANLEGGSERVICE AS

Org. no. 928990907 Limited company (AS) Alta Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 3.5m
Operating profit NOK −225,000
Equity NOK 254,000
Incorporated 2022
Share capital NOK 30,000

Signals

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

TM ANLEGGSERVICE AS is registered as a limited company in Alta, Finnmark with organisation number 928990907. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Anleggs- og vedlikeholdsarbeid, utleie av arbeidskraft og utstyr, samt fiske og fangst og som faller naturlig inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.5m in revenue and NOK −225,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.5m
Operating profit
NOK −225,000
Equity
NOK 254,000
Est. value
NOK 1.3m

Financial health · 2025

Liquidity
1.28
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
4.5%
Weak
Equity as a share of total capital

Who owns TM ANLEGGSERVICE AS?

TM THOMASSEN HOLDING AS
TM ANLEGGSERVICE AS
NOK 3.5m rev. · NOK −225,000 profit

TM ANLEGGSERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TM ANLEGGSERVICE AS

Who owns TM ANLEGGSERVICE AS?

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

What is the revenue of TM ANLEGGSERVICE AS?

TM ANLEGGSERVICE AS had revenue of NOK 3.5m in 2025.

Who is the general manager of TM ANLEGGSERVICE AS?

Tor Magne Thomassen is registered as general manager of TM ANLEGGSERVICE AS.

Where is TM ANLEGGSERVICE AS based?

TM ANLEGGSERVICE AS has its business address in Tverrelvdalen.

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.