BIZTRAC BETA
Freight ocean transport

BTG ARROW III AS

Org. no. 922874867 Limited company (AS) Bergen Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 14.2m
Operating profit NOK 2.8m
Equity NOK 70.3m
Incorporated 2019
Share capital NOK 300,000

Signals

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

BTG ARROW III AS is registered as a limited company in Bergen, Vestland with organisation number 922874867. The business is classified under freight ocean transport (NACE 50.201). The company was incorporated in 2019. Registered share capital is NOK 300,000, divided into 1000 shares. The company's stated purpose is: “Eie skip, herunder kjøpe, selge og leie skip, drive shippingvirksomhet og næringsdrift av enhver art og delta i andre selskaper med annet eller lignende formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 14.2m in revenue and NOK 2.8m in operating profit.

Key figures · 2025

Revenue
NOK 14.2m
Operating profit
NOK 2.8m
Equity
NOK 70.3m
Est. value
NOK 43.0m

Financial health · 2025

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

Who owns BTG ARROW III AS?

BULK TRADING GROUP AS
BTG ARROW III AS
NOK 14.2m rev. · NOK 2.8m profit

BTG ARROW III AS has 1 registered shareholder:

All shareholders and roles →

Group structure

BTG ARROW III AS er morselskap for 14 datterselskaper:

Frequently asked questions about BTG ARROW III AS

Who owns BTG ARROW III AS?

BULK TRADING GROUP AS is the largest registered owner, with 100.0%.

What is the revenue of BTG ARROW III AS?

BTG ARROW III AS had revenue of NOK 14.2m in 2025.

Where is BTG ARROW III AS based?

BTG ARROW III AS has its business address in Bergen.

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.