BIZTRAC BETA
Other captive investment companies

VIGINTI AS

Org. no. 925597317 Limited company (AS) Rælingen Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 1.5m
Operating profit NOK 1.3m
Equity NOK −39.7m
Incorporated 2020
Share capital NOK 120,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−39,7 mill kr).

VIGINTI AS is registered as a limited company in Rælingen, Akershus with organisation number 925597317. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2020. Registered share capital is NOK 120,000, divided into 30000 shares. The company's stated purpose is: “Investeringsselskap med muligheter for å investere i aksjer, fond, obligasjoner, derivater og eiendom og annen virksomhet som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.5m in revenue and NOK 1.3m in operating profit.

Key figures · 2024

Revenue
NOK 1.5m
Operating profit
NOK 1.3m
Equity
NOK −39.7m
Est. value
NOK 8.1m

Financial health · 2025

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

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

Who owns VIGINTI AS?

VIGINTI II AS
VIGINTI AS
NOK 1.5m rev. · NOK 1.3m profit

VIGINTI AS has 1 registered shareholder:

All shareholders and roles →

Which companies does VIGINTI AS own?

VIGINTI AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about VIGINTI AS

Who owns VIGINTI AS?

VIGINTI II AS is the largest registered owner, with 100.0%.

What is the revenue of VIGINTI AS?

VIGINTI AS had revenue of NOK 1.5m in 2024.

Where is VIGINTI AS based?

VIGINTI AS has its business address in Rælingen.

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.