BIZTRAC BETA
Freight ocean transport

BTG ARROW II AS

Org. no. 820616812 Limited company (AS) Bergen Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 5.1m
Operating profit NOK 1.3m
Equity NOK 16.0m
Incorporated 2018
Share capital NOK 200,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 II AS is registered as a limited company in Bergen, Vestland with organisation number 820616812. The business is classified under freight ocean transport (NACE 50.201). The company was incorporated in 2018. Registered share capital is NOK 200,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 5.1m in revenue and NOK 1.3m in operating profit.

Key figures · 2025

Revenue
NOK 5.1m
Operating profit
NOK 1.3m
Equity
NOK 16.0m
Est. value
NOK 11.5m

Financial health · 2025

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

Who owns BTG ARROW II AS?

KGJ BULK HOLDING AS
BTG ARROW II AS
NOK 5.1m rev. · NOK 1.3m profit

BTG ARROW II AS has 1 registered shareholder:

All shareholders and roles →

Group structure

BTG ARROW II AS er morselskap for 14 datterselskaper:

Frequently asked questions about BTG ARROW II AS

Who owns BTG ARROW II AS?

KGJ BULK HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of BTG ARROW II AS?

BTG ARROW II AS had revenue of NOK 5.1m in 2025.

Where is BTG ARROW II AS based?

BTG ARROW II 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.