BIZTRAC BETA
Other passenger transport in coastal waters

KVITSØY EVENT AS

Org. no. 927431742 Limited company (AS) Kvitsøy Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 918,000
Operating profit NOK 122,000
Equity NOK 1.2m
Incorporated 2021
Share capital NOK 1.2m

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

KVITSØY EVENT AS is registered as a limited company in Kvitsøy, Rogaland with organisation number 927431742. The business is classified under other passenger transport in coastal waters (NACE 50.109). The company was incorporated in 2021. Registered share capital is NOK 1.2m, divided into 1200 shares. The company's stated purpose is: “Persontransport, event- og opplevelsesturer på sjøen.”. The most recent filed accounts, for the 2025 financial year, show NOK 918,000 in revenue and NOK 122,000 in operating profit.

Key figures · 2025

Revenue
NOK 918,000
Operating profit
NOK 122,000
Equity
NOK 1.2m
Est. value
NOK 1.0m

Financial health · 2024

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

Who owns KVITSØY EVENT AS?

KVITSØY SJØTJENESTER AS
KVITSØY EVENT AS
NOK 918,000 rev. · NOK 122,000 profit

KVITSØY EVENT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KVITSØY EVENT AS

Who owns KVITSØY EVENT AS?

KVITSØY SJØTJENESTER AS is the largest registered owner, with 100.0%.

What is the revenue of KVITSØY EVENT AS?

KVITSØY EVENT AS had revenue of NOK 918,000 in 2025.

Who is the general manager of KVITSØY EVENT AS?

Bjarte Espevik is registered as general manager of KVITSØY EVENT AS.

Where is KVITSØY EVENT AS based?

KVITSØY EVENT AS has its business address in Kvitsø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.