BIZTRAC BETA
Support activities for fishing and aquaculture

EIDESVIK RENSEFISK AS

Org. no. 911763680 Limited company (AS) Bømlo Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 881,000
Operating profit NOK 19,000
Equity NOK 3.5m
Incorporated 2013
Share capital NOK 553,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

EIDESVIK RENSEFISK AS is registered as a limited company in Bømlo, Vestland with organisation number 911763680. The business is classified under support activities for fishing and aquaculture (NACE 03.300). The company was incorporated in 2013. Registered share capital is NOK 553,000, divided into 552739 shares. The company's stated purpose is: “Fiskeri knyttet til rensefisk for oppdrettsanlegg samt tilhørende øvrige fiskerelaterte aktiviteter og alt hva hermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 881,000 in revenue and NOK 19,000 in operating profit.

Key figures · 2024

Revenue
NOK 881,000
Operating profit
NOK 19,000
Equity
NOK 3.5m
Est. value
NOK 1.8m

Financial health · 2024

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

Who owns EIDESVIK RENSEFISK AS?

EIDESVIK SEAFARM AS
EIDESVIK RENSEFISK AS
NOK 881,000 rev. · NOK 19,000 profit

EIDESVIK RENSEFISK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about EIDESVIK RENSEFISK AS

Who owns EIDESVIK RENSEFISK AS?

EIDESVIK SEAFARM AS is the largest registered owner, with 100.0%.

What is the revenue of EIDESVIK RENSEFISK AS?

EIDESVIK RENSEFISK AS had revenue of NOK 881,000 in 2024.

Where is EIDESVIK RENSEFISK AS based?

EIDESVIK RENSEFISK AS has its business address in Bømlo.

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.