biztrac. BETA
COMPANY REGISTER PROFILE
997977939 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Site preparation

MTM ANLEGG AS

Org. no. 997977939 Limited company (AS) Kviteseid Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 28.6m
Operating profit NOK 1.9m
Equity NOK 2.9m
Incorporated 2012
Employees 24
Share capital NOK 101,000

MTM ANLEGG AS is registered as a limited company in Kviteseid, Telemark with organisation number 997977939. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2012 and has 24 registered employees. Registered share capital is NOK 101,000, divided into 101 shares. The company's stated purpose is: “Drive entreprenørverksemd og konsulentverksemd innanfor bygg og anlegg og alt som naturleg høyrer saman med slik verksemd, herunder deltaking i andre selskap.”. The most recent filed accounts, for the 2025 financial year, show NOK 28.6m in revenue and NOK 1.9m in operating profit.

Key figures · 2025

Revenue
NOK 28.6m
▲ +47 %
Operating profit
NOK 1.9m
▲ +396 %
Equity
NOK 2.9m
▲ +71 %
Est. value
NOK 6.3m

Financial health · 2025

Liquidity
1.24
Satisfactory
Current assets ÷ current liabilities
Profitability
13.3%
Good
Return on total assets
Solidity
18.2%
Good
Equity as a share of total capital

Who owns MTM ANLEGG AS?

MTM ANLEGG AS
NOK 28.6m rev. · NOK 1.9m profit

MTM ANLEGG AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about MTM ANLEGG AS

Who owns MTM ANLEGG AS?

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

What is the revenue of MTM ANLEGG AS?

MTM ANLEGG AS had revenue of NOK 28.6m in 2025.

Who is the general manager of MTM ANLEGG AS?

Ståle Andre Moen is registered as general manager of MTM ANLEGG AS.

Where is MTM ANLEGG AS based?

MTM ANLEGG AS has its business address in Morgedal.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.