BIZTRAC BETA
Wholesale of fish, crustaceans and molluscs

SNØLAKS AS

Org. no. 936052932 Limited company (AS) Sortland Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 6.0m
Operating profit NOK −737,000
Equity NOK −225,000
Incorporated 2025
Share capital NOK 500,000

Signals

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

SNØLAKS AS is registered as a limited company in Sortland, Nordland with organisation number 936052932. 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 500,000, divided into 5000 shares. The company's stated purpose is: “Kjøp, salg og eksport av fiskeprodukter, samt annen virksomhet som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.0m in revenue and NOK −737,000 in operating profit.

Key figures · 2025

Revenue
NOK 6.0m
Operating profit
NOK −737,000
Equity
NOK −225,000

Financial health · 2025

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

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

Who owns SNØLAKS AS?

CHEE BOON LEE
SNØLAKS AS
NOK 6.0m rev. · NOK −737,000 profit

SNØLAKS AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about SNØLAKS AS

Who owns SNØLAKS AS?

CHEE BOON LEE is the largest registered owner, with 25.0%.

What is the revenue of SNØLAKS AS?

SNØLAKS AS had revenue of NOK 6.0m in 2025.

Who is the general manager of SNØLAKS AS?

Sigurd Voktor Pedersen is registered as general manager of SNØLAKS AS.

Where is SNØLAKS AS based?

SNØLAKS AS has its business address in Sortland.

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.