BIZTRAC BETA
Marine fishing

MARIT ELISE HASNES AS

Org. no. 989278363 Limited company (AS) Flakstad Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −65,000
Equity NOK 19.3m
Incorporated 2005
Share capital NOK 121,000

Signals

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

MARIT ELISE HASNES AS is registered as a limited company in Flakstad, Nordland with organisation number 989278363. The business is classified under marine fishing (NACE 03.110). The company was incorporated in 2005. Registered share capital is NOK 121,000, divided into 121 shares. The company's stated purpose is: “Eie andeler i andre selskaper, investere i andre selskaper og forvalte selskapets midler gjennom ulike finansielle plasseringer.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −65,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −65,000
Equity
NOK 19.3m
Est. value
NOK 13.7m

Financial health · 2024

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

Who owns MARIT ELISE HASNES AS?

MARIT ELISE HASNES
MARIT ELISE HASNES AS
NOK 0 rev. · NOK −65,000 profit

MARIT ELISE HASNES AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MARIT ELISE HASNES AS own?

MARIT ELISE HASNES AS holds stakes in 5 companies:

See the full ownership structure →

Frequently asked questions about MARIT ELISE HASNES AS

Who owns MARIT ELISE HASNES AS?

MARIT ELISE HASNES is the largest registered owner, with 100.0%.

What is the revenue of MARIT ELISE HASNES AS?

MARIT ELISE HASNES AS had revenue of NOK 0 in 2025.

Where is MARIT ELISE HASNES AS based?

MARIT ELISE HASNES AS has its business address in Sund I Lofoten.

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.