BIZTRAC BETA
Geological surveying

GREEN MINING AS

Org. no. 937746571 Limited company (AS) Tønsberg Incorporated 1985 Active
Ownership graph ↗
Operating profit NOK −12,000
Equity NOK 3.0m
Incorporated 1985
Share capital NOK 100,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−12k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

GREEN MINING AS is registered as a limited company in Tønsberg, Vestfold with organisation number 937746571. The business is classified under geological surveying (NACE 71.122). The company was incorporated in 1985. Registered share capital is NOK 100,000, divided into 20000000 shares. The company's stated purpose is: “Drive utvikling og industrialisering av malm og mineralforekomster og andre naturressurser med fokus på utvikling og bruk av naturvennlige og miljøvennlige produksjonsmetoder, samt drive prospektering og gruvedrift og deltakelse i nye forekomster, deltagelse i andre selskaper og alt som kan settes i forbindelse med dette.”.

Key figures · 2024

Operating profit
NOK −12,000
Equity
NOK 3.0m
Est. value
NOK 1.9m

Financial health · 2024

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

Who owns GREEN MINING AS?

TERRA CONTROL AS
GREEN MINING AS
· NOK −12,000 profit

GREEN MINING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GREEN MINING AS

Who owns GREEN MINING AS?

TERRA CONTROL AS is the largest registered owner, with 100.0%.

Who is the general manager of GREEN MINING AS?

Arne Nicander is registered as general manager of GREEN MINING AS.

Where is GREEN MINING AS based?

GREEN MINING AS has its business address in Tønsberg.

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.