BIZTRAC BETA
Marine fishing

RONDO FISKERI AS

Org. no. 926933256 Limited company (AS) Bømlo Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 873,000
Operating profit NOK 6,000
Equity NOK −116,000
Incorporated 2021
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−116k kr).

RONDO FISKERI AS is registered as a limited company in Bømlo, Vestland with organisation number 926933256. The business is classified under marine fishing (NACE 03.110). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Fiskeri og rederivirksomhet, samt annet som står i den forbindelse, herunder deltagelse i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 873,000 in revenue and NOK 6,000 in operating profit.

Key figures · 2024

Revenue
NOK 873,000
Operating profit
NOK 6,000
Equity
NOK −116,000
Est. value
NOK 25,000

Financial health · 2025

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns RONDO FISKERI AS?

HANS LEIF MØGSTER
RONDO FISKERI AS
NOK 873,000 rev. · NOK 6,000 profit

RONDO FISKERI AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about RONDO FISKERI AS

Who owns RONDO FISKERI AS?

HANS LEIF MØGSTER is the largest registered owner, with 76.0%.

What is the revenue of RONDO FISKERI AS?

RONDO FISKERI AS had revenue of NOK 873,000 in 2024.

Who is the general manager of RONDO FISKERI AS?

Hans Leif Møgster is registered as general manager of RONDO FISKERI AS.

Where is RONDO FISKERI AS based?

RONDO FISKERI AS has its business address in Finnås.

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.