BIZTRAC BETA
COMPANY REGISTER PROFILE
989225847 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Other captive investment companies

NILS RUNE SJURSEIKE AS

Org. no. 989225847 Limited company (AS) Vindafjord Incorporated 2005 Active
Ownership graph ↗
Operating profit NOK −18,000
Equity NOK 8.0m
Incorporated 2005
Share capital NOK 100,000

Signals

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

NILS RUNE SJURSEIKE AS is registered as a limited company in Vindafjord, Rogaland with organisation number 989225847. 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 1000 shares. The company's stated purpose is: “Eie aksjer, samt kjøpe, eie, utvikle, forvalte og selge eiendommer, samt delta i andre selskaper med lignende formål.”.

Key figures · 2025

Operating profit
NOK −18,000
▲ +56 %
Equity
NOK 8.0m
▼ −6 %
Est. value
NOK 7.3m

Financial health · 2025

Liquidity
1.05
Satisfactory
Current assets ÷ current liabilities
Profitability
0.5%
Not satisfactory
Return on total assets
Solidity
79.4%
Very good
Equity as a share of total capital

Who owns NILS RUNE SJURSEIKE AS?

NILS RUNE SJURSEIKE AS
· NOK −18,000 profit

NILS RUNE SJURSEIKE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does NILS RUNE SJURSEIKE AS own?

NILS RUNE SJURSEIKE AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about NILS RUNE SJURSEIKE AS

Who owns NILS RUNE SJURSEIKE AS?

NILS RUNE SJURSEIKE is the largest registered owner, with 100.0%.

Who is the general manager of NILS RUNE SJURSEIKE AS?

Nils Rune Sjurseike is registered as general manager of NILS RUNE SJURSEIKE AS.

Where is NILS RUNE SJURSEIKE AS based?

NILS RUNE SJURSEIKE AS has its business address in Øvre Vats.

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

Report a problem

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