BIZTRAC BETA
Marine fishing

TROLLSUND AS

Org. no. 914636485 Limited company (AS) Måsøy Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 2.0m
Operating profit NOK 773,000
Equity NOK 4.8m
Incorporated 2014
Share capital NOK 30,000

TROLLSUND AS is registered as a limited company in Måsøy, Finnmark with organisation number 914636485. The business is classified under marine fishing (NACE 03.110). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Fiskeri, eie fiskebåter med tilhørende kvoter og hva naturlig faller inn under dette, herunder å delta i andre selskap med lignende virksomhet og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.0m in revenue and NOK 773,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.0m
Operating profit
NOK 773,000
Equity
NOK 4.8m
Est. value
NOK 4.3m

Financial health · 2025

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

Who owns TROLLSUND AS?

ERLEND AMUND HESTEN
TROLLSUND AS
NOK 2.0m rev. · NOK 773,000 profit

TROLLSUND AS has 1 registered shareholder:

All shareholders and roles →

Which companies does TROLLSUND AS own?

TROLLSUND AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about TROLLSUND AS

Who owns TROLLSUND AS?

ERLEND AMUND HESTEN is the largest registered owner, with 46.7%.

What is the revenue of TROLLSUND AS?

TROLLSUND AS had revenue of NOK 2.0m in 2025.

Who is the general manager of TROLLSUND AS?

Erlend Amund Hesten is registered as general manager of TROLLSUND AS.

Where is TROLLSUND AS based?

TROLLSUND AS has its business address in Ingøy.

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.