BIZTRAC BETA
Support activities for fishing and aquaculture

BEITVEIT HOLDING AS

Org. no. 818579152 Limited company (AS) Sande Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 57.5m
Operating profit NOK 10.3m
Equity NOK 56.4m
Incorporated 2017
Employees 23
Share capital NOK 10.0m

BEITVEIT HOLDING AS is registered as a limited company in Sande, Møre og Romsdal with organisation number 818579152. The business is classified under support activities for fishing and aquaculture (NACE 03.300). The company was incorporated in 2017 and has 23 registered employees. Registered share capital is NOK 10.0m, divided into 10000 shares. The company's stated purpose is: “Drift av fartøy og salg av tjenester rettet mot offshore- og aquakulturmarkedet.”. The most recent filed accounts, for the 2025 financial year, show NOK 57.5m in revenue and NOK 10.3m in operating profit.

Key figures · 2025

Revenue
NOK 57.5m
Operating profit
NOK 10.3m
Equity
NOK 56.4m
Est. value
NOK 61.1m

Financial health · 2025

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

Who owns BEITVEIT HOLDING AS?

BEITVEIT AS
BEITVEIT HOLDING AS
NOK 57.5m rev. · NOK 10.3m profit

BEITVEIT HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Group structure

BEITVEIT HOLDING AS er morselskap for 1 datterselskap:

Frequently asked questions about BEITVEIT HOLDING AS

Who owns BEITVEIT HOLDING AS?

BEITVEIT AS is the largest registered owner, with 100.0%.

What is the revenue of BEITVEIT HOLDING AS?

BEITVEIT HOLDING AS had revenue of NOK 57.5m in 2025.

Who is the general manager of BEITVEIT HOLDING AS?

Kenneth André Beitveit is registered as general manager of BEITVEIT HOLDING AS.

Where is BEITVEIT HOLDING AS based?

BEITVEIT HOLDING AS has its business address in Kvamsø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.