BIZTRAC BETA
Wholesale of hardware, plumbing and heating equipment and supplies

ECO SOLUTIONS AS

Org. no. 819818932 Limited company (AS) Øyer Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 30.0m
Operating profit NOK 979,000
Equity NOK 1.5m
Incorporated 2017
Share capital NOK 833,000

ECO SOLUTIONS AS is registered as a limited company in Øyer, Innlandet with organisation number 819818932. The business is classified under wholesale of hardware, plumbing and heating equipment and supplies (NACE 46.840). The company was incorporated in 2017. Registered share capital is NOK 833,000, divided into 833332 shares. The company's stated purpose is: “Kjøp og salg av varer og tjenester til VA/VVS-anlegg og hva som hører inn under dette. Virksomheten skal utøves i egen regi eller ved å investere i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 30.0m in revenue and NOK 979,000 in operating profit.

Key figures · 2024

Revenue
NOK 30.0m
Operating profit
NOK 979,000
Equity
NOK 1.5m
Est. value
NOK 4.5m

Financial health · 2025

Liquidity
1.26
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
25.4%
Good
Equity as a share of total capital

Who owns ECO SOLUTIONS AS?

VITALE PRODUKTER AS
ECO SOLUTIONS AS
NOK 30.0m rev. · NOK 979,000 profit

ECO SOLUTIONS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ECO SOLUTIONS AS

Who owns ECO SOLUTIONS AS?

VITALE PRODUKTER AS is the largest registered owner, with 100.0%.

What is the revenue of ECO SOLUTIONS AS?

ECO SOLUTIONS AS had revenue of NOK 30.0m in 2024.

Who is the general manager of ECO SOLUTIONS AS?

Morten Gudbrandsen is registered as general manager of ECO SOLUTIONS AS.

Where is ECO SOLUTIONS AS based?

ECO SOLUTIONS AS has its business address in Tretten.

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.