BIZTRAC BETA
Manufacture of fasteners and screw machine products

ASCARO AS

Org. no. 910291955 Limited company (AS) Bærum Incorporated 1965 Active
Ownership graph ↗
Revenue 2024 NOK 540,000
Operating profit NOK −251,000
Equity NOK 1.1m
Incorporated 1965
Share capital NOK 200,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−251k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

ASCARO AS is registered as a limited company in Bærum, Akershus with organisation number 910291955. The business is classified under manufacture of fasteners and screw machine products (NACE 25.940). The company was incorporated in 1965. Registered share capital is NOK 200,000, divided into 100 shares. The company's stated purpose is: “Fabrikasjon og deltagelse i andre selskaper, samt agenturvirksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 540,000 in revenue and NOK −251,000 in operating profit.

Key figures · 2024

Revenue
NOK 540,000
Operating profit
NOK −251,000
Equity
NOK 1.1m
Est. value
NOK 858,000

Financial health · 2024

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

Who owns ASCARO AS?

MATERIALHOLDING AS
ASCARO AS
NOK 540,000 rev. · NOK −251,000 profit

ASCARO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ASCARO AS

Who owns ASCARO AS?

MATERIALHOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of ASCARO AS?

ASCARO AS had revenue of NOK 540,000 in 2024.

Who is the general manager of ASCARO AS?

Jørund Woll is registered as general manager of ASCARO AS.

Where is ASCARO AS based?

ASCARO AS has its business address in Rud.

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.