BIZTRAC BETA
COMPANY REGISTER PROFILE
993528919 ORG. NO. 2019 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Freezing and further processing of fish, crustaceans and molluscs

SEGELVIK FISKEMOTTAK SA

Org. no. 993528919 Co-operation (SA) Kvænangen Incorporated 2009 Active
Ownership graph ↗
Revenue 2019 NOK 31,000
Operating profit NOK −28,000
Equity NOK 913
Incorporated 2009

Signals

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

SEGELVIK FISKEMOTTAK SA is registered as a co-operation in Kvænangen, Troms with organisation number 993528919. The business is classified under freezing and further processing of fish, crustaceans and molluscs (NACE 10.203). The company was incorporated in 2009. The company's stated purpose is: “Fiskemottak for videresending av fiske råstogg til fiskekjøper, samt fremme medlemmenes økonomiske interesser gjennom deres deltakelse i virksomheten som kjøper av varer(eller tjenester) fra foretaket.”. The most recent filed accounts, for the 2019 financial year, show NOK 31,000 in revenue and NOK −28,000 in operating profit.

Key figures · 2019

Revenue
NOK 31,000
Operating profit
NOK −28,000
Equity
NOK 913
Est. value
NOK 1,000

Financial health · 2019

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

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

Who owns SEGELVIK FISKEMOTTAK SA?

No shareholders are registered for SEGELVIK FISKEMOTTAK SA in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about SEGELVIK FISKEMOTTAK SA

What is the revenue of SEGELVIK FISKEMOTTAK SA?

SEGELVIK FISKEMOTTAK SA had revenue of NOK 31,000 in 2019.

Where is SEGELVIK FISKEMOTTAK SA based?

SEGELVIK FISKEMOTTAK SA has its business address in Seglvik.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.