BIZTRAC BETA
Uoppgitt

MELTING HOLDING AS

Org. no. 920233872 Limited company (AS) Trondheim Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −31,000
Equity NOK 2.6m
Incorporated 2018
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−31k kr).

MELTING HOLDING AS is registered as a limited company in Trondheim, Trøndelag with organisation number 920233872. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Erverve, eie og forvalte aksjer, og virksomhet forbundet med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −31,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −31,000
Equity
NOK 2.6m
Est. value
NOK 11.1m

Financial health · 2025

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

Who owns MELTING HOLDING AS?

KNUT MELTING
MELTING HOLDING AS
NOK 0 rev. · NOK −31,000 profit

MELTING HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MELTING HOLDING AS own?

MELTING HOLDING AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about MELTING HOLDING AS

Who owns MELTING HOLDING AS?

KNUT MELTING is the largest registered owner, with 100.0%.

What is the revenue of MELTING HOLDING AS?

MELTING HOLDING AS had revenue of NOK 0 in 2025.

Who is the general manager of MELTING HOLDING AS?

Knut Melting is registered as general manager of MELTING HOLDING AS.

Where is MELTING HOLDING AS based?

MELTING HOLDING 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.