BIZTRAC BETA
Marine fishing

FRØYBAS AS

Org. no. 894867132 Limited company (AS) Bremanger Incorporated 2009 Active
Ownership graph ↗
Revenue 2024 NOK 30.8m
Operating profit NOK 5.9m
Equity NOK 95.9m
Incorporated 2009
Share capital NOK 199,000

Signals

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

FRØYBAS AS is registered as a limited company in Bremanger, Vestland with organisation number 894867132. The business is classified under marine fishing (NACE 03.110). The company was incorporated in 2009. Registered share capital is NOK 199,000, divided into 19859 shares. The company's stated purpose is: “Fiskeriverksemd samt verksemd med tilknytning til dette, her medrekna deltaking i andre selskap med liknande verksemd. Selskapet skal og kunne drive investeringsvirksomhet, herunder å eie aksjer og andeler i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 30.8m in revenue and NOK 5.9m in operating profit.

Key figures · 2024

Revenue
NOK 30.8m
Operating profit
NOK 5.9m
Equity
NOK 95.9m
Est. value
NOK 59.4m

Financial health · 2024

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

Who owns FRØYBAS AS?

RLS INVEST AS
FRØYBAS AS
NOK 30.8m rev. · NOK 5.9m profit

FRØYBAS AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about FRØYBAS AS

Who owns FRØYBAS AS?

RLS INVEST AS is the largest registered owner, with 96.1%.

What is the revenue of FRØYBAS AS?

FRØYBAS AS had revenue of NOK 30.8m in 2024.

Who is the general manager of FRØYBAS AS?

Ronny Larsen is registered as general manager of FRØYBAS AS.

Where is FRØYBAS AS based?

FRØYBAS AS has its business address in Kalvåg.

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.