BIZTRAC BETA
Site preparation

TMK SERVICE AS

Org. no. 823470142 Limited company (AS) Vennesla Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 452,000
Operating profit NOK −449,000
Equity NOK −238,000
Incorporated 2019
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−238k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−449k kr).

TMK SERVICE AS is registered as a limited company in Vennesla, Agder with organisation number 823470142. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Anleggsvirksomhet, vinter- og sommervedlikehold, transport, brøyting, graving og alle typer aktiviteter som naturlig hører inn under dette. Samt kjøp/salg/investering i eiendom og andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 452,000 in revenue and NOK −449,000 in operating profit.

Key figures · 2024

Revenue
NOK 452,000
Operating profit
NOK −449,000
Equity
NOK −238,000

Financial health · 2024

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns TMK SERVICE AS?

MAGNE WEDEGE NYGAARD
TMK SERVICE AS
NOK 452,000 rev. · NOK −449,000 profit

TMK SERVICE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about TMK SERVICE AS

Who owns TMK SERVICE AS?

MAGNE WEDEGE NYGAARD is the largest registered owner, with 50.0%.

What is the revenue of TMK SERVICE AS?

TMK SERVICE AS had revenue of NOK 452,000 in 2024.

Where is TMK SERVICE AS based?

TMK SERVICE AS has its business address in Vennesla.

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.