BIZTRAC BETA
Accounting and bookkeeping

VARGO KOMPETANSE AS

Org. no. 917275254 Limited company (AS) Oslo Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 83,000
Operating profit NOK −95,000
Equity NOK 1.7m
Incorporated 2016
Share capital NOK 536,000

Signals

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

VARGO KOMPETANSE AS is registered as a limited company in Oslo, Oslo with organisation number 917275254. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 2016. Registered share capital is NOK 536,000, divided into 267970 shares. The company's stated purpose is: “Konsulentvirksomhet, regnskapsføring og forretningsførsel for andre, samt virksomhet som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 83,000 in revenue and NOK −95,000 in operating profit.

Key figures · 2025

Revenue
NOK 83,000
Operating profit
NOK −95,000
Equity
NOK 1.7m
Est. value
NOK 1.9m

Financial health · 2025

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

Who owns VARGO KOMPETANSE AS?

VARGO KOMPETANSE AS
VARGO KOMPETANSE AS
NOK 83,000 rev. · NOK −95,000 profit

VARGO KOMPETANSE AS has 6 registered shareholders:

All shareholders and roles →

Which companies does VARGO KOMPETANSE AS own?

VARGO KOMPETANSE AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about VARGO KOMPETANSE AS

Who owns VARGO KOMPETANSE AS?

VARGO KOMPETANSE AS is the largest registered owner, with 93.3%.

What is the revenue of VARGO KOMPETANSE AS?

VARGO KOMPETANSE AS had revenue of NOK 83,000 in 2025.

Where is VARGO KOMPETANSE AS based?

VARGO KOMPETANSE 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.