BIZTRAC BETA
Uoppgitt

GVALUESTONE AS

Org. no. 923533699 Limited company (AS) Asker Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −40,000
Equity NOK −52,000
Incorporated 2019
Share capital NOK 81,000

Signals

3 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−52k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−40k kr).
  • Nylig endring 2026-05-20 Aksjekapital registrert 2026-05-20.

GVALUESTONE AS is registered as a limited company in Asker, Akershus with organisation number 923533699. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2019. Registered share capital is NOK 81,000, divided into 30000 shares. The company's stated purpose is: “Investering i aksjer, andeler, verdipapirer og eiendom samt dertil hørende virksomheter.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −40,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −40,000
Equity
NOK −52,000

Financial health · 2024

Liquidity
3.08
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-1.3%
Weak
Equity as a share of total capital

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

Who owns GVALUESTONE AS?

Stein Erik Moe
GVALUESTONE AS
NOK 0 rev. · NOK −40,000 profit

GVALUESTONE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does GVALUESTONE AS own?

GVALUESTONE AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about GVALUESTONE AS

Who owns GVALUESTONE AS?

Stein Erik Moe is the largest registered owner, with 100.0%.

What is the revenue of GVALUESTONE AS?

GVALUESTONE AS had revenue of NOK 0 in 2024.

Where is GVALUESTONE AS based?

GVALUESTONE AS has its business address in Nesøya.

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.