BIZTRAC BETA
Marine fishing

PORSANGERFJORD REKER AS

Org. no. 916071779 Limited company (AS) Porsanger Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 3.2m
Operating profit NOK 1.1m
Equity NOK −204,000
Incorporated 2015
Share capital NOK 30,000

Signals

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

PORSANGERFJORD REKER AS is registered as a limited company in Porsanger, Finnmark with organisation number 916071779. The business is classified under marine fishing (NACE 03.110). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Fiske fra båt og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.2m in revenue and NOK 1.1m in operating profit.

Key figures · 2025

Revenue
NOK 3.2m
Operating profit
NOK 1.1m
Equity
NOK −204,000
Est. value
NOK 5.3m

Financial health · 2025

Liquidity
0.48
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-79.8%
Weak
Equity as a share of total capital

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

Who owns PORSANGERFJORD REKER AS?

ØYVIND HESJEVIK
PORSANGERFJORD REKER AS
NOK 3.2m rev. · NOK 1.1m profit

PORSANGERFJORD REKER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PORSANGERFJORD REKER AS

Who owns PORSANGERFJORD REKER AS?

ØYVIND HESJEVIK is the largest registered owner, with 100.0%.

What is the revenue of PORSANGERFJORD REKER AS?

PORSANGERFJORD REKER AS had revenue of NOK 3.2m in 2025.

Who is the general manager of PORSANGERFJORD REKER AS?

Øyvind Hesjevik is registered as general manager of PORSANGERFJORD REKER AS.

Where is PORSANGERFJORD REKER AS based?

PORSANGERFJORD REKER AS has its business address in Lakselv.

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.