BIZTRAC BETA
Repair and maintenance of motor vehicles

MELHUS BILVASK AS

Org. no. 934551389 Limited company (AS) Melhus Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −22,000
Equity NOK 3,000
Incorporated 2024
Share capital NOK 30,000

Signals

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

MELHUS BILVASK AS is registered as a limited company in Melhus, Trøndelag with organisation number 934551389. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Selvbetjent bilvask, salg av bilvaskemaskiner, andre produkter/tjenester som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −22,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −22,000
Equity
NOK 3,000
Est. value
NOK 3,000

Financial health · 2024

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

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

Who owns MELHUS BILVASK AS?

KP HOLDING AS
MELHUS BILVASK AS
NOK 0 rev. · NOK −22,000 profit

MELHUS BILVASK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MELHUS BILVASK AS

Who owns MELHUS BILVASK AS?

KP HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of MELHUS BILVASK AS?

MELHUS BILVASK AS had revenue of NOK 0 in 2024.

Who is the general manager of MELHUS BILVASK AS?

Kristian Pettersen is registered as general manager of MELHUS BILVASK AS.

Where is MELHUS BILVASK AS based?

MELHUS BILVASK 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.