BIZTRAC BETA
Marine fishing

VEABØ KYSTFISKE AS

Org. no. 916109849 Limited company (AS) Tromsø Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 10.1m
Operating profit NOK 2.4m
Equity NOK 8.9m
Incorporated 2015
Share capital NOK 500,000

VEABØ KYSTFISKE AS is registered as a limited company in Tromsø, Troms with organisation number 916109849. The business is classified under marine fishing (NACE 03.110). The company was incorporated in 2015. Registered share capital is NOK 500,000, divided into 5000 shares. The company's stated purpose is: “Fiske og og andre tjenester og produkter som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender samt kjøp, salg og utleie av fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 10.1m in revenue and NOK 2.4m in operating profit.

Key figures · 2024

Revenue
NOK 10.1m
Operating profit
NOK 2.4m
Equity
NOK 8.9m
Est. value
NOK 8.9m

Financial health · 2024

Liquidity
1.64
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
24.2%
Good
Equity as a share of total capital

Who owns VEABØ KYSTFISKE AS?

TOR ANDERS VEABØ
VEABØ KYSTFISKE AS
NOK 10.1m rev. · NOK 2.4m profit

VEABØ KYSTFISKE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about VEABØ KYSTFISKE AS

Who owns VEABØ KYSTFISKE AS?

TOR ANDERS VEABØ is the largest registered owner, with 90.0%.

What is the revenue of VEABØ KYSTFISKE AS?

VEABØ KYSTFISKE AS had revenue of NOK 10.1m in 2024.

Who is the general manager of VEABØ KYSTFISKE AS?

Tor Anders Veabø is registered as general manager of VEABØ KYSTFISKE AS.

Where is VEABØ KYSTFISKE AS based?

VEABØ KYSTFISKE AS has its business address in Tromsø.

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.