BIZTRAC BETA
Construction of residential and non-residential buildings

GH NEXUS AS

Org. no. 929629981 Limited company (AS) Askøy Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 176,000
Operating profit NOK 25,000
Equity NOK 17.5m
Incorporated 2022
Share capital NOK 100,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

GH NEXUS AS is registered as a limited company in Askøy, Vestland with organisation number 929629981. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2022. Registered share capital is NOK 100,000, divided into 25 shares. The company's stated purpose is: “Bedriftsrådgivning og annen administrativ rådgivning, samt investeringsvirksomhet av enhver art.”. The most recent filed accounts, for the 2025 financial year, show NOK 176,000 in revenue and NOK 25,000 in operating profit.

Key figures · 2025

Revenue
NOK 176,000
Operating profit
NOK 25,000
Equity
NOK 17.5m
Est. value
NOK 10.7m

Financial health · 2025

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

Who owns GH NEXUS AS?

HÅKON JOHAN GRANHEIM
GH NEXUS AS
NOK 176,000 rev. · NOK 25,000 profit

GH NEXUS AS has 1 registered shareholder:

All shareholders and roles →

Which companies does GH NEXUS AS own?

GH NEXUS AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about GH NEXUS AS

Who owns GH NEXUS AS?

HÅKON JOHAN GRANHEIM is the largest registered owner, with 100.0%.

What is the revenue of GH NEXUS AS?

GH NEXUS AS had revenue of NOK 176,000 in 2025.

Where is GH NEXUS AS based?

GH NEXUS AS has its business address in Hauglandshella.

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.