BIZTRAC BETA
Marine fishing

SIENNAFISK AS

Org. no. 920855288 Limited company (AS) Flekkefjord Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 2.6m
Operating profit NOK 573,000
Equity NOK 509,000
Incorporated 2018
Share capital NOK 30,000

SIENNAFISK AS is registered as a limited company in Flekkefjord, Agder with organisation number 920855288. The business is classified under marine fishing (NACE 03.110). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Drive hav- og kystfiske, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.6m in revenue and NOK 573,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.6m
Operating profit
NOK 573,000
Equity
NOK 509,000
Est. value
NOK 1.4m

Financial health · 2024

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

Who owns SIENNAFISK AS?

JOHN VIDAR LØVIK LARSEN
SIENNAFISK AS
NOK 2.6m rev. · NOK 573,000 profit

SIENNAFISK AS has 2 registered shareholders:

All shareholders and roles →

Which companies does SIENNAFISK AS own?

SIENNAFISK AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SIENNAFISK AS

Who owns SIENNAFISK AS?

JOHN VIDAR LØVIK LARSEN is the largest registered owner, with 66.0%.

What is the revenue of SIENNAFISK AS?

SIENNAFISK AS had revenue of NOK 2.6m in 2024.

Who is the general manager of SIENNAFISK AS?

John Vidar Løvik Larsen is registered as general manager of SIENNAFISK AS.

Where is SIENNAFISK AS based?

SIENNAFISK AS has its business address in Hidrasund.

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.