BIZTRAC BETA
Refrigeration installation, heat pump installation and installation of fireplaces

MELLINGEN SERVICE AS

Org. no. 920402992 Limited company (AS) Narvik Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 2.5m
Operating profit NOK 372,000
Equity NOK 565,000
Incorporated 2018
Share capital NOK 30,000

MELLINGEN SERVICE AS is registered as a limited company in Narvik, Nordland with organisation number 920402992. The business is classified under refrigeration installation, heat pump installation and installation of fireplaces (NACE 43.222). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Montering/service på varmepumper med fokus på kvalitet og inneklima. Energisparing med grønn, fornybar energi.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.5m in revenue and NOK 372,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.5m
Operating profit
NOK 372,000
Equity
NOK 565,000
Est. value
NOK 1.1m

Financial health · 2025

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

Who owns MELLINGEN SERVICE AS?

STIAN MELLINGEN
MELLINGEN SERVICE AS
NOK 2.5m rev. · NOK 372,000 profit

MELLINGEN SERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MELLINGEN SERVICE AS

Who owns MELLINGEN SERVICE AS?

STIAN MELLINGEN is the largest registered owner, with 100.0%.

What is the revenue of MELLINGEN SERVICE AS?

MELLINGEN SERVICE AS had revenue of NOK 2.5m in 2025.

Who is the general manager of MELLINGEN SERVICE AS?

Stian Mellingen is registered as general manager of MELLINGEN SERVICE AS.

Where is MELLINGEN SERVICE AS based?

MELLINGEN SERVICE AS has its business address in Narvik.

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.