BIZTRAC BETA
Marine fishing

SANDMO KREPS OG KRABBE AS

Org. no. 917819238 Limited company (AS) Utsira Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 1.6m
Operating profit NOK 108,000
Equity NOK −15,000
Incorporated 2016
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−15k kr).

SANDMO KREPS OG KRABBE AS is registered as a limited company in Utsira, Rogaland with organisation number 917819238. The business is classified under marine fishing (NACE 03.110). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Å drive med fiskeri med garn og teiner langs kysten, samt hva hermed står i forbindelse, herunder å delta i andre foretak med tilsvarende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.6m in revenue and NOK 108,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.6m
Operating profit
NOK 108,000
Equity
NOK −15,000
Est. value
NOK 756,000

Financial health · 2025

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

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

Who owns SANDMO KREPS OG KRABBE AS?

BJØRN JOSTEIN SANDMO
SANDMO KREPS OG KRABBE AS
NOK 1.6m rev. · NOK 108,000 profit

SANDMO KREPS OG KRABBE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SANDMO KREPS OG KRABBE AS

Who owns SANDMO KREPS OG KRABBE AS?

BJØRN JOSTEIN SANDMO is the largest registered owner, with 50.3%.

What is the revenue of SANDMO KREPS OG KRABBE AS?

SANDMO KREPS OG KRABBE AS had revenue of NOK 1.6m in 2025.

Where is SANDMO KREPS OG KRABBE AS based?

SANDMO KREPS OG KRABBE AS has its business address in Utsira.

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.