BIZTRAC BETA
Activities of tour guides

FISHING CLUB VEIHOLMEN AS

Org. no. 919362979 Limited company (AS) Smøla Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 2.8m
Operating profit NOK 563,000
Equity NOK 2.0m
Incorporated 2017
Share capital NOK 1.0m

Signals

1 flags
  • Nylig endring 2026-06-22 Adresseendring registrert 2026-06-22.

FISHING CLUB VEIHOLMEN AS is registered as a limited company in Smøla, Møre og Romsdal with organisation number 919362979. The business is classified under activities of tour guides (NACE 79.902). The company was incorporated in 2017. Registered share capital is NOK 1.0m, divided into 1000 shares. The company's stated purpose is: “Drive fisketurisme, samt hva som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.8m in revenue and NOK 563,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.8m
Operating profit
NOK 563,000
Equity
NOK 2.0m
Est. value
NOK 2.6m

Financial health · 2025

Liquidity
0.13
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
17.3%
Satisfactory
Equity as a share of total capital

Who owns FISHING CLUB VEIHOLMEN AS?

TOMAS VRTIS
FISHING CLUB VEIHOLMEN AS
NOK 2.8m rev. · NOK 563,000 profit

FISHING CLUB VEIHOLMEN AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about FISHING CLUB VEIHOLMEN AS

Who owns FISHING CLUB VEIHOLMEN AS?

TOMAS VRTIS is the largest registered owner, with 50.0%.

What is the revenue of FISHING CLUB VEIHOLMEN AS?

FISHING CLUB VEIHOLMEN AS had revenue of NOK 2.8m in 2025.

Who is the general manager of FISHING CLUB VEIHOLMEN AS?

Jiri Svab is registered as general manager of FISHING CLUB VEIHOLMEN AS.

Where is FISHING CLUB VEIHOLMEN AS based?

FISHING CLUB VEIHOLMEN AS has its business address in Smøla.

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.