BIZTRAC BETA
Business and other management consultancy activities

GHS PROSJEKT OG PROSESS AS

Org. no. 916538383 Limited company (AS) Ørsta Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 2.4m
Operating profit NOK 891,000
Equity NOK 1.5m
Incorporated 2016
Share capital NOK 30,000

GHS PROSJEKT OG PROSESS AS is registered as a limited company in Ørsta, Møre og Romsdal with organisation number 916538383. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Selskapet sitt føremål er sal av konsulenttenester og prosjektleiingstenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.4m in revenue and NOK 891,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.4m
Operating profit
NOK 891,000
Equity
NOK 1.5m
Est. value
NOK 3.8m

Financial health · 2025

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

Who owns GHS PROSJEKT OG PROSESS AS?

GRY HELENE STAVSENG
GHS PROSJEKT OG PROSESS AS
NOK 2.4m rev. · NOK 891,000 profit

GHS PROSJEKT OG PROSESS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GHS PROSJEKT OG PROSESS AS

Who owns GHS PROSJEKT OG PROSESS AS?

GRY HELENE STAVSENG is the largest registered owner, with 100.0%.

What is the revenue of GHS PROSJEKT OG PROSESS AS?

GHS PROSJEKT OG PROSESS AS had revenue of NOK 2.4m in 2025.

Who is the general manager of GHS PROSJEKT OG PROSESS AS?

Gry Helene Stavseng is registered as general manager of GHS PROSJEKT OG PROSESS AS.

Where is GHS PROSJEKT OG PROSESS AS based?

GHS PROSJEKT OG PROSESS AS has its business address in Ørsta.

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.