BIZTRAC BETA
Marine fishing

FIOLIN HOLDING AS

Org. no. 920285198 Limited company (AS) Vestvågøy Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −134,000
Equity NOK 16.3m
Incorporated 2018
Share capital NOK 35,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−134k kr).

FIOLIN HOLDING AS is registered as a limited company in Vestvågøy, Nordland with organisation number 920285198. The business is classified under marine fishing (NACE 03.110). The company was incorporated in 2018. Registered share capital is NOK 35,000, divided into 17615 shares. The company's stated purpose is: “Investering i aksjer og andeler i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −134,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −134,000
Equity
NOK 16.3m
Est. value
NOK 19.5m

Financial health · 2025

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

Who owns FIOLIN HOLDING AS?

TOM OLAV NILSEN
FIOLIN HOLDING AS
NOK 0 rev. · NOK −134,000 profit

FIOLIN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does FIOLIN HOLDING AS own?

FIOLIN HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about FIOLIN HOLDING AS

Who owns FIOLIN HOLDING AS?

TOM OLAV NILSEN is the largest registered owner, with 100.0%.

What is the revenue of FIOLIN HOLDING AS?

FIOLIN HOLDING AS had revenue of NOK 0 in 2025.

Who is the general manager of FIOLIN HOLDING AS?

Tom Olav Nilsen is registered as general manager of FIOLIN HOLDING AS.

Where is FIOLIN HOLDING AS based?

FIOLIN HOLDING AS has its business address in Sennesvik.

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.