BIZTRAC BETA
Marine fishing

FROG OLSEN AS

Org. no. 920941281 Limited company (AS) Ørland Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 1.7m
Operating profit NOK −1.3m
Equity NOK 5.3m
Incorporated 2018
Share capital NOK 36,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−1,3 mill kr).

FROG OLSEN AS is registered as a limited company in Ørland, Trøndelag with organisation number 920941281. The business is classified under marine fishing (NACE 03.110). The company was incorporated in 2018. Registered share capital is NOK 36,000, divided into 300 shares. The company's stated purpose is: “Fiske og andre produkter/tjenester som naturlig hører til dette, 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. Selskapet kan også drive med kjøp/drift av fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.7m in revenue and NOK −1.3m in operating profit.

Key figures · 2025

Revenue
NOK 1.7m
Operating profit
NOK −1.3m
Equity
NOK 5.3m
Est. value
NOK 3.4m

Financial health · 2025

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

Who owns FROG OLSEN AS?

TROND OLSEN
FROG OLSEN AS
NOK 1.7m rev. · NOK −1.3m profit

FROG OLSEN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about FROG OLSEN AS

Who owns FROG OLSEN AS?

TROND OLSEN is the largest registered owner, with 51.0%.

What is the revenue of FROG OLSEN AS?

FROG OLSEN AS had revenue of NOK 1.7m in 2025.

Who is the general manager of FROG OLSEN AS?

Hilde Frog is registered as general manager of FROG OLSEN AS.

Where is FROG OLSEN AS based?

FROG OLSEN AS has its business address in Vallersund.

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.