BIZTRAC BETA
Computer programming activities

GARGOIL AS

Org. no. 990109826 Limited company (AS) Oslo Incorporated 2006 Active
Ownership graph ↗
Revenue 2025 NOK 68
Operating profit NOK −91,000
Equity NOK 1.4m
Incorporated 2006
Share capital NOK 100,000

Signals

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

GARGOIL AS is registered as a limited company in Oslo, Oslo with organisation number 990109826. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2006. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Selskapets virksomhet er it-relaterte tjenester, investeringer i verdipapirer/eiendom, import/eksport av varer, samt salg av disse. ”. The most recent filed accounts, for the 2025 financial year, show NOK 68 in revenue and NOK −91,000 in operating profit.

Key figures · 2025

Revenue
NOK 68
Operating profit
NOK −91,000
Equity
NOK 1.4m
Est. value
NOK 23.0m

Financial health · 2025

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

Who owns GARGOIL AS?

ØYVIND DALE SPØRCK
GARGOIL AS
NOK 68 rev. · NOK −91,000 profit

GARGOIL AS has 1 registered shareholder:

All shareholders and roles →

Which companies does GARGOIL AS own?

GARGOIL AS holds stakes in 10 companies:

See the full ownership structure →

Frequently asked questions about GARGOIL AS

Who owns GARGOIL AS?

ØYVIND DALE SPØRCK is the largest registered owner, with 100.0%.

What is the revenue of GARGOIL AS?

GARGOIL AS had revenue of NOK 68 in 2025.

Who is the general manager of GARGOIL AS?

Sandy Iracema Valencia Spørck is registered as general manager of GARGOIL AS.

Where is GARGOIL AS based?

GARGOIL AS has its business address in Oslo.

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.