BIZTRAC BETA
Rental and operating of own or leased real estate

NORDRE SØRØYA RORBUER AS

Org. no. 822772412 Limited company (AS) Hammerfest Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 7.2m
Operating profit NOK 681,000
Equity NOK 2.9m
Incorporated 2019
Employees 5
Share capital NOK 5.0m

NORDRE SØRØYA RORBUER AS is registered as a limited company in Hammerfest, Finnmark with organisation number 822772412. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2019 and has 5 registered employees. Registered share capital is NOK 5.0m, divided into 5000 shares. The company's stated purpose is: “Hvalsafari, utleie av hytter, båt, scootere og andre fasiliteter, herunder deltakelse i andre virksomheter som naturlig hører inn under foranstående. Selskapet kan delta i annen virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 7.2m in revenue and NOK 681,000 in operating profit.

Key figures · 2025

Revenue
NOK 7.2m
Operating profit
NOK 681,000
Equity
NOK 2.9m
Est. value
NOK 3.3m

Financial health · 2025

Liquidity
0.62
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
19.8%
Good
Equity as a share of total capital

Who owns NORDRE SØRØYA RORBUER AS?

ANDERSEN FISKEBÅTREDERI AS
NORDRE SØRØYA RORBUER AS
NOK 7.2m rev. · NOK 681,000 profit

NORDRE SØRØYA RORBUER AS has 6 registered shareholders:

All shareholders and roles →

Frequently asked questions about NORDRE SØRØYA RORBUER AS

Who owns NORDRE SØRØYA RORBUER AS?

ANDERSEN FISKEBÅTREDERI AS is the largest registered owner, with 30.0%.

What is the revenue of NORDRE SØRØYA RORBUER AS?

NORDRE SØRØYA RORBUER AS had revenue of NOK 7.2m in 2025.

Where is NORDRE SØRØYA RORBUER AS based?

NORDRE SØRØYA RORBUER AS has its business address in Akkarfjord.

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.