BIZTRAC BETA
Marine fishing

PREMIUM HARVEST AS

Org. no. 835402452 Limited company (AS) Bergen Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 191,000
Operating profit NOK −337,000
Equity NOK −346,000
Incorporated 2025
Share capital NOK 100,000

Signals

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

PREMIUM HARVEST AS is registered as a limited company in Bergen, Vestland with organisation number 835402452. The business is classified under marine fishing (NACE 03.110). The company was incorporated in 2025. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Kystfiske, salg/mottak av sjømat.”. The most recent filed accounts, for the 2025 financial year, show NOK 191,000 in revenue and NOK −337,000 in operating profit.

Key figures · 2025

Revenue
NOK 191,000
Operating profit
NOK −337,000
Equity
NOK −346,000

Financial health · 2025

Liquidity
7.24
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-21.1%
Weak
Equity as a share of total capital

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

Who owns PREMIUM HARVEST AS?

KÅRVIK INVEST AS
PREMIUM HARVEST AS
NOK 191,000 rev. · NOK −337,000 profit

PREMIUM HARVEST AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about PREMIUM HARVEST AS

Who owns PREMIUM HARVEST AS?

KÅRVIK INVEST AS is the largest registered owner, with 51.0%.

What is the revenue of PREMIUM HARVEST AS?

PREMIUM HARVEST AS had revenue of NOK 191,000 in 2025.

Who is the general manager of PREMIUM HARVEST AS?

Sebastian Bjørnsønn Ludvigsen is registered as general manager of PREMIUM HARVEST AS.

Where is PREMIUM HARVEST AS based?

PREMIUM HARVEST AS has its business address in Eidsvågneset.

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.