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

FISKESKJÆR BERLEVÅG AS

Org. no. 990013713 Limited company (AS) Berlevåg Incorporated 2006 Active
Revenue 2025 NOK 1.2m
Operating profit NOK −28,000
Equity NOK 12.8m
Incorporated 2006
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−28k kr).

FISKESKJÆR BERLEVÅG AS is registered as a limited company in Berlevåg, Finnmark with organisation number 990013713. The business is classified under marine fishing (NACE 03.110). The company was incorporated in 2006. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Fiske og fangst.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.2m in revenue and NOK −28,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.2m
▲ +52 %
Operating profit
NOK −28,000
▲ +97 %
Equity
NOK 12.8m
▲ +3 %
Est. value
NOK 7.4m

Financial health · 2025

Liquidity
24.94
Very good
Current assets ÷ current liabilities
Profitability
3.3%
Weak
Return on total assets
Solidity
87.7%
Very good
Equity as a share of total capital

Who owns FISKESKJÆR BERLEVÅG AS?

FISKESKJÆR BERLEVÅG AS
NOK 1.2m rev. · NOK −28,000 profit

FISKESKJÆR BERLEVÅG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FISKESKJÆR BERLEVÅG AS

Who owns FISKESKJÆR BERLEVÅG AS?

Petter Arvid Gregersen is the largest registered owner, with 100.0%.

What is the revenue of FISKESKJÆR BERLEVÅG AS?

FISKESKJÆR BERLEVÅG AS had revenue of NOK 1.2m in 2025.

Who is the general manager of FISKESKJÆR BERLEVÅG AS?

Petter Arvid Gregersen is registered as general manager of FISKESKJÆR BERLEVÅG AS.

Where is FISKESKJÆR BERLEVÅG AS based?

FISKESKJÆR BERLEVÅG AS has its business address in Berlevåg.

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.