BIZTRAC BETA
Supply and other sea transport offshore services

BOA TUGS AS

Org. no. 992982985 Limited company (AS) Trondheim Incorporated 2008 Active
Ownership graph ↗
Revenue 2024 NOK 238.9m
Operating profit NOK 30.8m
Equity NOK 147.8m
Incorporated 2008
Share capital NOK 33.8m

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

BOA TUGS AS is registered as a limited company in Trondheim, Trøndelag with organisation number 992982985. The business is classified under supply and other sea transport offshore services (NACE 50.203). The company was incorporated in 2008. Registered share capital is NOK 33.8m, divided into 338 shares. The company's stated purpose is: “Rederi og befraktningsvirksomhet, samt dertil tilhørende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 238.9m in revenue and NOK 30.8m in operating profit.

Key figures · 2024

Revenue
NOK 238.9m
Operating profit
NOK 30.8m
Equity
NOK 147.8m
Est. value
NOK 154.5m

Financial health · 2024

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

Who owns BOA TUGS AS?

BOA SHIPPING AS
BOA TUGS AS
NOK 238.9m rev. · NOK 30.8m profit

BOA TUGS AS has 1 registered shareholder:

All shareholders and roles →

Group structure

BOA TUGS AS er morselskap for 8 datterselskaper:

Frequently asked questions about BOA TUGS AS

Who owns BOA TUGS AS?

BOA SHIPPING AS is the largest registered owner, with 100.0%.

What is the revenue of BOA TUGS AS?

BOA TUGS AS had revenue of NOK 238.9m in 2024.

Who is the general manager of BOA TUGS AS?

Ole Torberg Bjørnevik is registered as general manager of BOA TUGS AS.

Where is BOA TUGS AS based?

BOA TUGS AS has its business address in Trondheim.

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.