BIZTRAC BETA
Construction of residential and non-residential buildings

ARROW-NORWAY AS

Org. no. 932321467 Limited company (AS) Sandefjord Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 19.1m
Operating profit NOK 2.0m
Equity NOK 1.4m
Incorporated 2023
Employees 25
Share capital NOK 30,000

ARROW-NORWAY AS is registered as a limited company in Sandefjord, Vestfold with organisation number 932321467. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2023 and has 25 registered employees. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Rivning av bygninger og andre konstruksjoner. Service-oppdrag inklusiv tømreroppdrag. Selskapets formål er også å kunne gi gaver til humanitære og veldedige formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 19.1m in revenue and NOK 2.0m in operating profit.

Key figures · 2024

Revenue
NOK 19.1m
Operating profit
NOK 2.0m
Equity
NOK 1.4m
Est. value
NOK 6.8m

Financial health · 2024

Liquidity
0.99
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
15.3%
Satisfactory
Equity as a share of total capital

Who owns ARROW-NORWAY AS?

CANADIAN CORPORATION
ARROW-NORWAY AS
NOK 19.1m rev. · NOK 2.0m profit

ARROW-NORWAY AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ARROW-NORWAY AS

Who owns ARROW-NORWAY AS?

CANADIAN CORPORATION is the largest registered owner, with 51.0%.

What is the revenue of ARROW-NORWAY AS?

ARROW-NORWAY AS had revenue of NOK 19.1m in 2024.

Who is the general manager of ARROW-NORWAY AS?

Aleksander Olsen is registered as general manager of ARROW-NORWAY AS.

Where is ARROW-NORWAY AS based?

ARROW-NORWAY AS has its business address in Sandefjord.

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.