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

KVIK HOLDING AS

Org. no. 934948513 Limited company (AS) Øygarden Incorporated 2025 Active
Ownership graph ↗
Operating profit NOK −7,000
Equity NOK 23,000
Incorporated 2025
Share capital NOK 30,000

Signals

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

KVIK HOLDING AS is registered as a limited company in Øygarden, Vestland with organisation number 934948513. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Kjøp, salg og utleie av fast eiendom. Kjøp og salg verdipapirer.”.

Key figures · 2025

Operating profit
NOK −7,000
Equity
NOK 23,000
Est. value
NOK 27,000

Financial health · 2025

Liquidity
1.18
Satisfactory
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
24.5%
Weak
Equity as a share of total capital

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

Who owns KVIK HOLDING AS?

KVIK HOLDING AS
· NOK −7,000 profit

KVIK HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KVIK HOLDING AS

Who owns KVIK HOLDING AS?

KRISTIAN VIK is the largest registered owner, with 100.0%.

Where is KVIK HOLDING AS based?

KVIK HOLDING AS has its business address in Straume.

Property

Business address Søre Straume 5, 5353 Straume
Cadastral unit 4626-35/654/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.