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

MOSS KJØLESERVICE AS

Org. no. 928791033 Limited company (AS) Moss Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 4.9m
Operating profit NOK 611,000
Equity NOK 1.2m
Incorporated 2022
Share capital NOK 30,000

MOSS KJØLESERVICE AS is registered as a limited company in Moss, Østfold with organisation number 928791033. The business is classified under refrigeration installation, heat pump installation and installation of fireplaces (NACE 43.222). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Salg, installasjon og service på kjøleanlegg og andre produkter/tjenester som naturlig hører sammen med dette, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.9m in revenue and NOK 611,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.9m
Operating profit
NOK 611,000
Equity
NOK 1.2m
Est. value
NOK 2.5m

Financial health · 2025

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

Who owns MOSS KJØLESERVICE AS?

STIG EMANUELSSON
MOSS KJØLESERVICE AS
NOK 4.9m rev. · NOK 611,000 profit

MOSS KJØLESERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MOSS KJØLESERVICE AS

Who owns MOSS KJØLESERVICE AS?

STIG EMANUELSSON is the largest registered owner, with 100.0%.

What is the revenue of MOSS KJØLESERVICE AS?

MOSS KJØLESERVICE AS had revenue of NOK 4.9m in 2025.

Where is MOSS KJØLESERVICE AS based?

MOSS KJØLESERVICE AS has its business address in Moss.

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.