biztrac. BETA
COMPANY REGISTER PROFILE
935357306 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Freezing and further processing of fish, crustaceans and molluscs

SEA GROWTH AS

Org. no. 935357306 Limited company (AS) Værøy Incorporated 2025 Active
Revenue 2025 NOK 0
Operating profit NOK −2,000
Equity NOK 22,000
Incorporated 2025
Share capital NOK 30,000

Signals

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

SEA GROWTH AS is registered as a limited company in Værøy, Nordland with organisation number 935357306. The business is classified under freezing and further processing of fish, crustaceans and molluscs (NACE 10.203). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Full utnyttelse av bi-produkter.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −2,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −2,000
Equity
NOK 22,000
Est. value
NOK 26,000

Financial health · 2025

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

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

Who owns SEA GROWTH AS?

SEA GROWTH AS
NOK 0 rev. · NOK −2,000 profit

SEA GROWTH AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SEA GROWTH AS

Who owns SEA GROWTH AS?

Erlend Voldset is the largest registered owner, with 50.0%.

What is the revenue of SEA GROWTH AS?

SEA GROWTH AS had revenue of NOK 0 in 2025.

Who is the general manager of SEA GROWTH AS?

Erlend Voldset is registered as general manager of SEA GROWTH AS.

Where is SEA GROWTH AS based?

SEA GROWTH AS has its business address in Værøy.

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.