BIZTRAC BETA
Site preparation

MTM EIGEDOM AS

Org. no. 912901483 Limited company (AS) Kviteseid Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 156,000
Operating profit NOK −25,000
Equity NOK −585,000
Incorporated 2013
Share capital NOK 30,000

Signals

3 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−585k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−25k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

MTM EIGEDOM AS is registered as a limited company in Kviteseid, Telemark with organisation number 912901483. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Utleige av næringsbygg. Selskapet kan og delta i andre selskap.”. The most recent filed accounts, for the 2024 financial year, show NOK 156,000 in revenue and NOK −25,000 in operating profit.

Key figures · 2024

Revenue
NOK 156,000
Operating profit
NOK −25,000
Equity
NOK −585,000

Financial health · 2024

Liquidity
3.36
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-25.2%
Weak
Equity as a share of total capital

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

Who owns MTM EIGEDOM AS?

MOEN TRANSPORT & MASKIN AS
MTM EIGEDOM AS
NOK 156,000 rev. · NOK −25,000 profit

MTM EIGEDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MTM EIGEDOM AS

Who owns MTM EIGEDOM AS?

MOEN TRANSPORT & MASKIN AS is the largest registered owner, with 100.0%.

What is the revenue of MTM EIGEDOM AS?

MTM EIGEDOM AS had revenue of NOK 156,000 in 2024.

Where is MTM EIGEDOM AS based?

MTM EIGEDOM AS has its business address in Kviteseid.

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.