BIZTRAC BETA
Rental and operating of own or leased real estate

VEST DYKKERSERVICE AS

Org. no. 913411099 Limited company (AS) Stad Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 1.6m
Operating profit NOK −430,000
Equity NOK 44.2m
Incorporated 2014
Share capital NOK 216,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−430k kr).

VEST DYKKERSERVICE AS is registered as a limited company in Stad, Vestland with organisation number 913411099. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2014. Registered share capital is NOK 216,000, divided into 21558 shares. The company's stated purpose is: “Entreprenørvirksomhet og utleie av eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.6m in revenue and NOK −430,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.6m
Operating profit
NOK −430,000
Equity
NOK 44.2m
Est. value
NOK 36.0m

Financial health · 2024

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

Who owns VEST DYKKERSERVICE AS?

PER-KÅRE NAVEKVIEN
VEST DYKKERSERVICE AS
NOK 1.6m rev. · NOK −430,000 profit

VEST DYKKERSERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VEST DYKKERSERVICE AS

Who owns VEST DYKKERSERVICE AS?

PER-KÅRE NAVEKVIEN is the largest registered owner, with 100.0%.

What is the revenue of VEST DYKKERSERVICE AS?

VEST DYKKERSERVICE AS had revenue of NOK 1.6m in 2024.

Who is the general manager of VEST DYKKERSERVICE AS?

Per-Kåre Navekvien is registered as general manager of VEST DYKKERSERVICE AS.

Where is VEST DYKKERSERVICE AS based?

VEST DYKKERSERVICE AS has its business address in Nordfjordeid.

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.