biztrac. BETA
COMPANY REGISTER PROFILE
926941674 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

ARROW HOLDING AS

Org. no. 926941674 Limited company (AS) Sandefjord Incorporated 2021 Active
Revenue 2025 NOK 0
Operating profit NOK −17,000
Equity NOK 13,000
Incorporated 2021
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−17k kr).

ARROW HOLDING AS is registered as a limited company in Sandefjord, Vestfold with organisation number 926941674. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Investering i aksjer og andeler samt levering av tjenester innen gravearbeid.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −17,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −17,000
Equity
NOK 13,000
▼ −55 %
Est. value
NOK 16,000

Financial health · 2025

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns ARROW HOLDING AS?

ARROW HOLDING AS
NOK 0 rev. · NOK −17,000 profit

ARROW HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ARROW HOLDING AS

Who owns ARROW HOLDING AS?

Alexander Gabrielsen is the largest registered owner, with 100.0%.

What is the revenue of ARROW HOLDING AS?

ARROW HOLDING AS had revenue of NOK 0 in 2025.

Who is the general manager of ARROW HOLDING AS?

Aleksander Olsen is registered as general manager of ARROW HOLDING AS.

Where is ARROW HOLDING AS based?

ARROW HOLDING AS has its business address in Stokke.

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.