BIZTRAC BETA
Business and other management consultancy activities

ECOGRAVE SOLUTIONS AS

Org. no. 929509587 Limited company (AS) Sandefjord Incorporated 2022 Active
Ownership graph ↗
Operating profit NOK −4,000
Equity NOK 24,000
Incorporated 2022
Share capital NOK 40,000

Signals

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

ECOGRAVE SOLUTIONS AS is registered as a limited company in Sandefjord, Vestfold with organisation number 929509587. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2022. Registered share capital is NOK 40,000, divided into 400000 shares. The company's stated purpose is: “Selge komplette systemer med tilhørende service- og vedlikeholdsavtaler og tilhørende reservedeler, samt eventuelle ombygginger av eksisterende anlegg. Selskapet skal også kunne etablere nye selskaper i inn/utland, samt å etablere lisensavtaler og franchiseavtaler i inn/utland, eie aksjer i datterselskaper og i joint venture, samt å investere i andre selskaper og eiendom, og dertil hørende aktiviteter.”.

Key figures · 2025

Operating profit
NOK −4,000
Equity
NOK 24,000
Est. value
NOK 39,000

Financial health · 2025

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

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

Who owns ECOGRAVE SOLUTIONS AS?

ECOGRAVE AS
ECOGRAVE SOLUTIONS AS
· NOK −4,000 profit

ECOGRAVE SOLUTIONS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ECOGRAVE SOLUTIONS AS

Who owns ECOGRAVE SOLUTIONS AS?

ECOGRAVE AS is the largest registered owner, with 100.0%.

Where is ECOGRAVE SOLUTIONS AS based?

ECOGRAVE SOLUTIONS AS has its business address in Sandefjord.

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.