BIZTRAC BETA
Marine fishing

BØMLO TRÅL AS

Org. no. 921599706 Limited company (AS) Bømlo Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 48.9m
Operating profit NOK 10.9m
Equity NOK 49.6m
Incorporated 2018
Employees 9
Share capital NOK 2.9m

Signals

1 flags
  • Nylig endring 2026-04-08 Aksjekapital registrert 2026-04-08.

BØMLO TRÅL AS is registered as a limited company in Bømlo, Vestland with organisation number 921599706. The business is classified under marine fishing (NACE 03.110). The company was incorporated in 2018 and has 9 registered employees. Registered share capital is NOK 2.9m, divided into 29100 shares. The company's stated purpose is: “Fiskeri og rederivirksomhet samt hva hermed står i forbindelse, herunder å delta i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 48.9m in revenue and NOK 10.9m in operating profit.

Key figures · 2024

Revenue
NOK 48.9m
Operating profit
NOK 10.9m
Equity
NOK 49.6m
Est. value
NOK 50.8m

Financial health · 2024

Liquidity
1.72
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
30.0%
Good
Equity as a share of total capital

Who owns BØMLO TRÅL AS?

E LØNNING AS
BØMLO TRÅL AS
NOK 48.9m rev. · NOK 10.9m profit

BØMLO TRÅL AS has 5 registered shareholders:

All shareholders and roles →

Which companies does BØMLO TRÅL AS own?

BØMLO TRÅL AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about BØMLO TRÅL AS

Who owns BØMLO TRÅL AS?

E LØNNING AS is the largest registered owner, with 35.0%.

What is the revenue of BØMLO TRÅL AS?

BØMLO TRÅL AS had revenue of NOK 48.9m in 2024.

Who is the general manager of BØMLO TRÅL AS?

Erlend Lønning is registered as general manager of BØMLO TRÅL AS.

Where is BØMLO TRÅL AS based?

BØMLO TRÅL AS has its business address in Bømlo.

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.