biztrac. BETA
COMPANY REGISTER PROFILE
925578770 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Marine fishing

RAPPEN AS

Org. no. 925578770 Limited company (AS) Stord Incorporated 2020 Active
Ownership graph ↗
Operating profit NOK −121,000
Equity NOK −192,000
Incorporated 2020
Share capital NOK 200,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−192k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−121k kr).

RAPPEN AS is registered as a limited company in Stord, Vestland with organisation number 925578770. The business is classified under marine fishing (NACE 03.110). The company was incorporated in 2020. Registered share capital is NOK 200,000, divided into 200 shares. The company's stated purpose is: “Hav- og kystfiske, herunder salg og kaisalg av sjømat og sjømatprodukter. Selskapet skal også drive engroshandel med skipsutstyr og fiskeredskap og drive forskning og annet utviklingsarbeid av nye produkter. Selskapet skal drive utleie av fiskefartøy. Selskapet skal samle inn biologisk materiale for bioprospektering.”.

Key figures · 2025

Operating profit
NOK −121,000
▼ −399 %
Equity
NOK −192,000
▼ −168 %

Financial health · 2025

Liquidity
1.28
Satisfactory
Current assets ÷ current liabilities
Profitability
-42.9%
Not satisfactory
Return on total assets
Solidity
-72.5%
Weak
Equity as a share of total capital

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

Who owns RAPPEN AS?

RAPPEN AS
· NOK −121,000 profit

RAPPEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RAPPEN AS

Who owns RAPPEN AS?

OSLAND INVEST AS is the largest registered owner, with 100.0%.

Who is the general manager of RAPPEN AS?

Helge Osland is registered as general manager of RAPPEN AS.

Where is RAPPEN AS based?

RAPPEN AS has its business address in Stord.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.