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

M. EILERTSEN FISKEBÅT AS

Org. no. 934968719 Limited company (AS) Hadsel Incorporated 2024 Active
Revenue 2025 NOK 2.3m
Operating profit NOK 282,000
Equity NOK 128,000
Incorporated 2024
Share capital NOK 30,000

M. EILERTSEN FISKEBÅT AS is registered as a limited company in Hadsel, Nordland with organisation number 934968719. The business is classified under marine fishing (NACE 03.110). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Drive fiske og fangst, eie fiskebåter samt kunne delta i annen virksomhet med økonomisk formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.3m in revenue and NOK 282,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.3m
Operating profit
NOK 282,000
Equity
NOK 128,000
Est. value
NOK 399,000

Financial health · 2025

Liquidity
0.97
Weak
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
2.8%
Not satisfactory
Equity as a share of total capital

Who owns M. EILERTSEN FISKEBÅT AS?

M. EILERTSEN FISKEBÅT AS
NOK 2.3m rev. · NOK 282,000 profit

M. EILERTSEN FISKEBÅT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about M. EILERTSEN FISKEBÅT AS

Who owns M. EILERTSEN FISKEBÅT AS?

Mette Elise Eilertsen is the largest registered owner, with 100.0%.

What is the revenue of M. EILERTSEN FISKEBÅT AS?

M. EILERTSEN FISKEBÅT AS had revenue of NOK 2.3m in 2025.

Who is the general manager of M. EILERTSEN FISKEBÅT AS?

Mette Elise Eilertsen is registered as general manager of M. EILERTSEN FISKEBÅT AS.

Where is M. EILERTSEN FISKEBÅT AS based?

M. EILERTSEN FISKEBÅT AS has its business address in Stokmarknes.

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.