BIZTRAC BETA
Business and other management consultancy activities

STARGI HOLDING AS

Org. no. 916837895 Limited company (AS) Gjesdal Incorporated 2016 Active
Ownership graph ↗
Operating profit NOK −19,000
Equity NOK −389,000
Incorporated 2016
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−389k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−19k kr).

STARGI HOLDING AS is registered as a limited company in Gjesdal, Rogaland with organisation number 916837895. 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 30000 shares. The company's stated purpose is: “Utvikling og investering i andre selskaper og eller andre former for investeringer, og alt som står i forbindelse med de forannevnte virksomheter.”.

Key figures · 2025

Operating profit
NOK −19,000
Equity
NOK −389,000

Financial health · 2025

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

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

Who owns STARGI HOLDING AS?

STIG ARE GILJA
STARGI HOLDING AS
· NOK −19,000 profit

STARGI HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does STARGI HOLDING AS own?

STARGI HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about STARGI HOLDING AS

Who owns STARGI HOLDING AS?

STIG ARE GILJA is the largest registered owner, with 100.0%.

Who is the general manager of STARGI HOLDING AS?

Stig Are Gilja is registered as general manager of STARGI HOLDING AS.

Where is STARGI HOLDING AS based?

STARGI HOLDING AS has its business address in Dirdal.

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.