BIZTRAC BETA
Wholesale of wood, construction materials and sanitary equipment

CRAIG AS

Org. no. 931063235 Limited company (AS) Bergen Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 967,000
Operating profit NOK −110,000
Equity NOK −89,000
Incorporated 2023
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−89k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−110k kr).

CRAIG AS is registered as a limited company in Bergen, Vestland with organisation number 931063235. The business is classified under wholesale of wood, construction materials and sanitary equipment (NACE 46.830). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Kjøp, salg, import av varer. Utleie og drift av fly. Utleie og drift av eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 967,000 in revenue and NOK −110,000 in operating profit.

Key figures · 2025

Revenue
NOK 967,000
Operating profit
NOK −110,000
Equity
NOK −89,000

Financial health · 2025

Liquidity
0.59
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-37.5%
Weak
Equity as a share of total capital

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

Who owns CRAIG AS?

Øystein Aarø
CRAIG AS
NOK 967,000 rev. · NOK −110,000 profit

CRAIG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about CRAIG AS

Who owns CRAIG AS?

Øystein Aarø is the largest registered owner, with 100.0%.

What is the revenue of CRAIG AS?

CRAIG AS had revenue of NOK 967,000 in 2025.

Who is the general manager of CRAIG AS?

Øystein Aarø is registered as general manager of CRAIG AS.

Where is CRAIG AS based?

CRAIG AS has its business address in Straumsgrend.

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.