BIZTRAC BETA
Uoppgitt

KRISTVIKA NÆRINGSPARK 2 AS

Org. no. 914922704 Limited company (AS) Averøy Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −41,000
Equity NOK 1.6m
Incorporated 2015
Share capital NOK 3.9m

Signals

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

KRISTVIKA NÆRINGSPARK 2 AS is registered as a limited company in Averøy, Møre og Romsdal with organisation number 914922704. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2015. Registered share capital is NOK 3.9m, divided into 39000 shares. The company's stated purpose is: “Kjøp og utvikling av eiendom, herunder utleie, samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −41,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −41,000
Equity
NOK 1.6m
Est. value
NOK 1.9m

Financial health · 2025

Liquidity
3.33
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
13.3%
Satisfactory
Equity as a share of total capital

Who owns KRISTVIKA NÆRINGSPARK 2 AS?

SPAREBANK 1 NORDMØRE
KRISTVIKA NÆRINGSPARK 2 AS
NOK 0 rev. · NOK −41,000 profit

KRISTVIKA NÆRINGSPARK 2 AS has 6 registered shareholders:

All shareholders and roles →

Frequently asked questions about KRISTVIKA NÆRINGSPARK 2 AS

Who owns KRISTVIKA NÆRINGSPARK 2 AS?

SPAREBANK 1 NORDMØRE is the largest registered owner, with 50.0%.

What is the revenue of KRISTVIKA NÆRINGSPARK 2 AS?

KRISTVIKA NÆRINGSPARK 2 AS had revenue of NOK 0 in 2025.

Who is the general manager of KRISTVIKA NÆRINGSPARK 2 AS?

Tommy Vebenstad is registered as general manager of KRISTVIKA NÆRINGSPARK 2 AS.

Where is KRISTVIKA NÆRINGSPARK 2 AS based?

KRISTVIKA NÆRINGSPARK 2 AS has its business address in Averøy.

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.