biztrac. BETA
COMPANY REGISTER PROFILE
993974811 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Marine fishing

SAGPLASSEN FISK AS

Org. no. 993974811 Limited company (AS) Suldal Incorporated 2009 Active
Ownership graph ↗
Revenue 2025 NOK 1.1m
Operating profit NOK −145,000
Equity NOK 1.4m
Incorporated 2009
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−145k kr).

SAGPLASSEN FISK AS is registered as a limited company in Suldal, Rogaland with organisation number 993974811. The business is classified under marine fishing (NACE 03.110). The company was incorporated in 2009. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Driva kystfiske og andre aktivitetar som kan vera knytta til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.1m in revenue and NOK −145,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.1m
▲ +144 %
Operating profit
NOK −145,000
▲ +66 %
Equity
NOK 1.4m
▼ −7 %
Est. value
NOK 1.2m

Financial health · 2025

Liquidity
2.09
Very good
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
83.1%
Very good
Equity as a share of total capital

Who owns SAGPLASSEN FISK AS?

SAGPLASSEN FISK AS
NOK 1.1m rev. · NOK −145,000 profit

SAGPLASSEN FISK AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SAGPLASSEN FISK AS

Who owns SAGPLASSEN FISK AS?

Lars Harald Sildelid is the largest registered owner, with 59.0%.

What is the revenue of SAGPLASSEN FISK AS?

SAGPLASSEN FISK AS had revenue of NOK 1.1m in 2025.

Who is the general manager of SAGPLASSEN FISK AS?

Lars Harald Sildelid is registered as general manager of SAGPLASSEN FISK AS.

Where is SAGPLASSEN FISK AS based?

SAGPLASSEN FISK AS has its business address in Hebnes.

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

Report a problem

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