BIZTRAC BETA
COMPANY REGISTER PROFILE
960735773 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Marine fishing

RANGSUNDFISK AS

Org. no. 960735773 Limited company (AS) Rødøy Incorporated 1991 Active
Ownership graph ↗
Revenue 2025 NOK 143,000
Operating profit NOK −92,000
Equity NOK −272,000
Incorporated 1991
Share capital NOK 478,000

Signals

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

RANGSUNDFISK AS is registered as a limited company in Rødøy, Nordland with organisation number 960735773. The business is classified under marine fishing (NACE 03.110). The company was incorporated in 1991. Registered share capital is NOK 478,000, divided into 478 shares. The company's stated purpose is: “Drive fiske.”. The most recent filed accounts, for the 2025 financial year, show NOK 143,000 in revenue and NOK −92,000 in operating profit.

Key figures · 2025

Revenue
NOK 143,000
▼ −54 %
Operating profit
NOK −92,000
▼ −33 %
Equity
NOK −272,000
▼ −51 %

Financial health · 2025

Liquidity
0.44
Not satisfactory
Current assets ÷ current liabilities
Profitability
-23.7%
Not satisfactory
Return on total assets
Solidity
-78.9%
Weak
Equity as a share of total capital

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

Who owns RANGSUNDFISK AS?

RANGSUNDFISK AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about RANGSUNDFISK AS

Who owns RANGSUNDFISK AS?

TROND EDVARD ROALDSETH is the largest registered owner, with 51.0%.

What is the revenue of RANGSUNDFISK AS?

RANGSUNDFISK AS had revenue of NOK 143,000 in 2025.

Who is the general manager of RANGSUNDFISK AS?

Bjørn Eilif Johan Pedersen is registered as general manager of RANGSUNDFISK AS.

Where is RANGSUNDFISK AS based?

RANGSUNDFISK AS has its business address in Selsøyvik.

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

Report a problem

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