biztrac. BETA
COMPANY REGISTER PROFILE
989259296 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Other captive investment companies

VIKØYR INVEST AS

Org. no. 989259296 Limited company (AS) Bergen Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −35,000
Equity NOK 9.5m
Incorporated 2005
Share capital NOK 100,000

Signals

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

VIKØYR INVEST AS is registered as a limited company in Bergen, Vestland with organisation number 989259296. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Investering i andre selskaper, aksjer, fond og eiendom, samt alt som hører naturlig til dette”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −35,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −35,000
▼ −11 %
Equity
NOK 9.5m
▲ +3 %
Est. value
NOK 8.6m

Financial health · 2025

Liquidity
318.97
Very good
Current assets ÷ current liabilities
Profitability
10.4%
Good
Return on total assets
Solidity
99.7%
Very good
Equity as a share of total capital

Who owns VIKØYR INVEST AS?

VIKØYR INVEST AS
NOK 0 rev. · NOK −35,000 profit

VIKØYR INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does VIKØYR INVEST AS own?

VIKØYR INVEST AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about VIKØYR INVEST AS

Who owns VIKØYR INVEST AS?

Gisle Vikøyr is the largest registered owner, with 100.0%.

What is the revenue of VIKØYR INVEST AS?

VIKØYR INVEST AS had revenue of NOK 0 in 2025.

Where is VIKØYR INVEST AS based?

VIKØYR INVEST AS has its business address in Paradis.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.