BIZTRAC BETA
Wholesale of fish, crustaceans and molluscs

NORCOAST SEAFOOD AS

Org. no. 935739144 Limited company (AS) Giske Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 270,000
Operating profit NOK 13,000
Equity NOK 35,000
Incorporated 2025
Share capital NOK 30,000

NORCOAST SEAFOOD AS is registered as a limited company in Giske, Møre og Romsdal with organisation number 935739144. The business is classified under wholesale of fish, crustaceans and molluscs (NACE 46.322). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Slakting, bearbeiding og konservering av fisk og fiskevarer og Produksjons utleie av fisk og fiskevarer.”. The most recent filed accounts, for the 2025 financial year, show NOK 270,000 in revenue and NOK 13,000 in operating profit.

Key figures · 2025

Revenue
NOK 270,000
Operating profit
NOK 13,000
Equity
NOK 35,000
Est. value
NOK 68,000

Financial health · 2025

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

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

Who owns NORCOAST SEAFOOD AS?

HANS KRISTIAN MIKKELSEN
NORCOAST SEAFOOD AS
NOK 270,000 rev. · NOK 13,000 profit

NORCOAST SEAFOOD AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about NORCOAST SEAFOOD AS

Who owns NORCOAST SEAFOOD AS?

HANS KRISTIAN MIKKELSEN is the largest registered owner, with 50.0%.

What is the revenue of NORCOAST SEAFOOD AS?

NORCOAST SEAFOOD AS had revenue of NOK 270,000 in 2025.

Who is the general manager of NORCOAST SEAFOOD AS?

Chris Fredrik Auflem Lorenzen is registered as general manager of NORCOAST SEAFOOD AS.

Where is NORCOAST SEAFOOD AS based?

NORCOAST SEAFOOD AS has its business address in Valderøya.

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.