biztrac. BETA
COMPANY REGISTER PROFILE
932346249 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

GPH CAPITAL AS

Org. no. 932346249 Limited company (AS) Asker Incorporated 2023 Active
Revenue 2025 NOK 0
Operating profit NOK −18,000
Equity NOK 745,000
Incorporated 2023
Share capital NOK 30,000

Signals

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

GPH CAPITAL AS is registered as a limited company in Asker, Akershus with organisation number 932346249. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Å være et investeringsselskap, herunder å investere i aksjer, obligasjoner, fast eiendom, andeler i selskap etter selskapsloven og alt som dermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −18,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −18,000
▲ +2 %
Equity
NOK 745,000
▲ +55 %
Est. value
NOK 2.1m

Financial health · 2025

Liquidity
145.79
Very good
Current assets ÷ current liabilities
Profitability
48.4%
Very good
Return on total assets
Solidity
99.3%
Very good
Equity as a share of total capital

Who owns GPH CAPITAL AS?

GPH CAPITAL AS
NOK 0 rev. · NOK −18,000 profit

GPH CAPITAL AS has 1 registered shareholder:

All shareholders and roles →

Which companies does GPH CAPITAL AS own?

GPH CAPITAL AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about GPH CAPITAL AS

Who owns GPH CAPITAL AS?

Vegard Nyhus is the largest registered owner, with 100.0%.

What is the revenue of GPH CAPITAL AS?

GPH CAPITAL AS had revenue of NOK 0 in 2025.

Where is GPH CAPITAL AS based?

GPH CAPITAL AS has its business address in Nærsnes.

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

Report a problem

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