BIZTRAC BETA
Combined facilities support activities

MELHUS VAKTMESTERSERVICE AS

Org. no. 979484976 Limited company (AS) Trondheim Incorporated 1997 Active
Ownership graph ↗
Revenue 2024 NOK 5.5m
Operating profit NOK 139,000
Equity NOK 9.1m
Incorporated 1997
Share capital NOK 300,000

MELHUS VAKTMESTERSERVICE AS is registered as a limited company in Trondheim, Trøndelag with organisation number 979484976. The business is classified under combined facilities support activities (NACE 81.100). The company was incorporated in 1997. Registered share capital is NOK 300,000, divided into 150 shares. The company's stated purpose is: “Å tilby ulike håndtverks- og vaktmestertjenester, samt beslektet virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 5.5m in revenue and NOK 139,000 in operating profit.

Key figures · 2024

Revenue
NOK 5.5m
Operating profit
NOK 139,000
Equity
NOK 9.1m
Est. value
NOK 5.2m

Financial health · 2024

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

Who owns MELHUS VAKTMESTERSERVICE AS?

SVEIN ERIK HUSTØFT
MELHUS VAKTMESTERSERVICE AS
NOK 5.5m rev. · NOK 139,000 profit

MELHUS VAKTMESTERSERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MELHUS VAKTMESTERSERVICE AS

Who owns MELHUS VAKTMESTERSERVICE AS?

SVEIN ERIK HUSTØFT is the largest registered owner, with 100.0%.

What is the revenue of MELHUS VAKTMESTERSERVICE AS?

MELHUS VAKTMESTERSERVICE AS had revenue of NOK 5.5m in 2024.

Who is the general manager of MELHUS VAKTMESTERSERVICE AS?

Svein Erik Hustøft is registered as general manager of MELHUS VAKTMESTERSERVICE AS.

Where is MELHUS VAKTMESTERSERVICE AS based?

MELHUS VAKTMESTERSERVICE AS has its business address in Trondheim.

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.