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

JULSUND AS

Org. no. 991677062 Limited company (AS) Hustadvika Incorporated 2007 Active
Revenue 2025 NOK 0
Operating profit NOK −79,000
Equity NOK 6.6m
Incorporated 2007
Share capital NOK 3.0m

Signals

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

JULSUND AS is registered as a limited company in Hustadvika, Møre og Romsdal with organisation number 991677062. The business is classified under marine fishing (NACE 03.110). The company was incorporated in 2007. Registered share capital is NOK 3.0m, divided into 2990 shares. The company's stated purpose is: “Drift av fiskefartøy og det som står i forbindelse, herunder deltakelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −79,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −79,000
▼ −23 %
Equity
NOK 6.6m
▼ −2 %
Est. value
NOK 6.3m

Financial health · 2025

Liquidity
1.77
Good
Current assets ÷ current liabilities
Profitability
-1.0%
Not satisfactory
Return on total assets
Solidity
89.8%
Very good
Equity as a share of total capital

Who owns JULSUND AS?

JULSUND AS
NOK 0 rev. · NOK −79,000 profit

JULSUND AS has 2 registered shareholders:

All shareholders and roles →

Which companies does JULSUND AS own?

JULSUND AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about JULSUND AS

Who owns JULSUND AS?

Roy Magne Gjerstad is the largest registered owner, with 70.2%.

What is the revenue of JULSUND AS?

JULSUND AS had revenue of NOK 0 in 2025.

Who is the general manager of JULSUND AS?

Roy Magne Gjerstad is registered as general manager of JULSUND AS.

Where is JULSUND AS based?

JULSUND AS has its business address in Aureosen.

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.