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

LEISUND AS

Org. no. 913706226 Limited company (AS) Måsøy Incorporated 2014 Active
Revenue 2025 NOK 2.5m
Operating profit NOK 587,000
Equity NOK 4.3m
Incorporated 2014
Employees 6
Share capital NOK 36,000

LEISUND AS is registered as a limited company in Måsøy, Finnmark with organisation number 913706226. The business is classified under marine fishing (NACE 03.110). The company was incorporated in 2014 and has 6 registered employees. Registered share capital is NOK 36,000, divided into 36 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 selsksap 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.5m in revenue and NOK 587,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.5m
▼ −2 %
Operating profit
NOK 587,000
▲ +132 %
Equity
NOK 4.3m
▲ +24 %
Est. value
NOK 4.1m

Financial health · 2025

Liquidity
5.67
Very good
Current assets ÷ current liabilities
Profitability
22.5%
Very good
Return on total assets
Solidity
86.1%
Very good
Equity as a share of total capital

Who owns LEISUND AS?

LEISUND AS
NOK 2.5m rev. · NOK 587,000 profit

LEISUND AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LEISUND AS own?

LEISUND AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about LEISUND AS

Who owns LEISUND AS?

Erlend Amund Hesten is the largest registered owner, with 100.0%.

What is the revenue of LEISUND AS?

LEISUND AS had revenue of NOK 2.5m in 2025.

Where is LEISUND AS based?

LEISUND 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 03.10.2026.

Report a problem

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