BIZTRAC BETA
Uoppgitt

MELHUS SNEKKERSERVICE AS

Org. no. 927572338 Limited company (AS) Melhus Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −9,000
Equity NOK 43,000
Incorporated 2021
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−9k kr).

MELHUS SNEKKERSERVICE AS is registered as a limited company in Melhus, Trøndelag with organisation number 927572338. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Å investere i selskaper og eiendom, kjøp og salg av aksjer.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −9,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −9,000
Equity
NOK 43,000
Est. value
NOK 50,000

Financial health · 2024

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

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

Who owns MELHUS SNEKKERSERVICE AS?

MARIUS DVARIONAS
MELHUS SNEKKERSERVICE AS
NOK 0 rev. · NOK −9,000 profit

MELHUS SNEKKERSERVICE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MELHUS SNEKKERSERVICE AS own?

MELHUS SNEKKERSERVICE AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about MELHUS SNEKKERSERVICE AS

Who owns MELHUS SNEKKERSERVICE AS?

MARIUS DVARIONAS is the largest registered owner, with 100.0%.

What is the revenue of MELHUS SNEKKERSERVICE AS?

MELHUS SNEKKERSERVICE AS had revenue of NOK 0 in 2024.

Where is MELHUS SNEKKERSERVICE AS based?

MELHUS SNEKKERSERVICE AS has its business address in Melhus.

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.