BIZTRAC BETA
COMPANY REGISTER PROFILE
928832449 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

G-CAPITAL AS

Org. no. 928832449 Limited company (AS) Bærum Incorporated 2022 Active
Ownership graph ↗
Operating profit NOK −8,000
Equity NOK 315,000
Incorporated 2022
Share capital NOK 60,000

Signals

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

G-CAPITAL AS is registered as a limited company in Bærum, Akershus with organisation number 928832449. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2022. Registered share capital is NOK 60,000, divided into 30000 shares. The company's stated purpose is: “Investeringer i aksjer, andre verdier og eiendom.”.

Key figures · 2025

Operating profit
NOK −8,000
▼ −9 %
Equity
NOK 315,000
▲ +70 %
Est. value
NOK 1.0m

Financial health · 2025

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

Who owns G-CAPITAL AS?

G-CAPITAL AS
· NOK −8,000 profit

G-CAPITAL AS has 1 registered shareholder:

All shareholders and roles →

Which companies does G-CAPITAL AS own?

G-CAPITAL AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about G-CAPITAL AS

Who owns G-CAPITAL AS?

STEPHAN GÄBLER is the largest registered owner, with 100.0%.

Where is G-CAPITAL AS based?

G-CAPITAL AS has its business address in Jar.

Property

Business address Velliveien 26A, 1358 Jar
Cadastral unit 3201-36/93/0/0
Building Enebolig · 1 unit

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.