BIZTRAC BETA
Support activities for other mining and quarrying

ESG MINERALS AS

Org. no. 926051490 Limited company (AS) Horten Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −3,000
Equity NOK −7,000
Incorporated 2020
Share capital NOK 32,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−7k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−3k kr).

ESG MINERALS AS is registered as a limited company in Horten, Vestfold with organisation number 926051490. The business is classified under support activities for other mining and quarrying (NACE 09.900). The company was incorporated in 2020. Registered share capital is NOK 32,000, divided into 96000 shares. The company's stated purpose is: “Investeringer i bergrettigheter, undersøkelse og utvinningsrettigheter av mineraler, eierskap og drift av gruver, samt andre tilhørende aktiviteter.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −3,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −3,000
Equity
NOK −7,000

Financial health · 2025

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

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

Who owns ESG MINERALS AS?

PER-CHRISTIAN WILLOCH FETT
ESG MINERALS AS
NOK 0 rev. · NOK −3,000 profit

ESG MINERALS AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ESG MINERALS AS

Who owns ESG MINERALS AS?

PER-CHRISTIAN WILLOCH FETT is the largest registered owner, with 50.0%.

What is the revenue of ESG MINERALS AS?

ESG MINERALS AS had revenue of NOK 0 in 2025.

Where is ESG MINERALS AS based?

ESG MINERALS AS has its business address in Åsgårdstrand.

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.