BIZTRAC BETA
COMPANY REGISTER PROFILE
826351632 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

3 SVERD VENTURE AS

Org. no. 826351632 Limited company (AS) Stavanger Incorporated 2020 Active
Ownership graph ↗
Operating profit NOK −8,000
Equity NOK 12,000
Incorporated 2020
Share capital NOK 32,000

Signals

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

3 SVERD VENTURE AS is registered as a limited company in Stavanger, Rogaland with organisation number 826351632. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2020. Registered share capital is NOK 32,000, divided into 31920 shares. The company's stated purpose is: “Investering i andre aksjeselskap.”.

Key figures · 2025

Operating profit
NOK −8,000
▼ −24 %
Equity
NOK 12,000
▼ −39 %
Est. value
NOK 14,000

Financial health · 2025

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

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

Who owns 3 SVERD VENTURE AS?

3 SVERD VENTURE AS has 7 registered shareholders:

All shareholders and roles →

Frequently asked questions about 3 SVERD VENTURE AS

Who owns 3 SVERD VENTURE AS?

RØYS INVEST AS is the largest registered owner, with 14.3%.

Where is 3 SVERD VENTURE AS based?

3 SVERD VENTURE AS has its business address in Hafrsfjord.

Property

Business address c/o Martin Lima Ragbakken 9C, 4042 Hafrsfjord
Cadastral unit 1103-38/4077/0/0
Building Enebolig · 1 unit

2 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

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.