BIZTRAC BETA
Other specialised construction activities n.e.c.

ASKER BETONGSAGING AS

Org. no. 927614650 Limited company (AS) Asker Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 14.0m
Operating profit NOK 4.6m
Equity NOK 1.0m
Incorporated 2021
Employees 5
Share capital NOK 1.0m

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

ASKER BETONGSAGING AS is registered as a limited company in Asker, Akershus with organisation number 927614650. The business is classified under other specialised construction activities n.e.c. (NACE 43.990). The company was incorporated in 2021 and has 5 registered employees. Registered share capital is NOK 1.0m, divided into 100 shares. The company's stated purpose is: “Riving.”. The most recent filed accounts, for the 2024 financial year, show NOK 14.0m in revenue and NOK 4.6m in operating profit.

Key figures · 2024

Revenue
NOK 14.0m
Operating profit
NOK 4.6m
Equity
NOK 1.0m
Est. value
NOK 13.0m

Financial health · 2024

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

Who owns ASKER BETONGSAGING AS?

VOKSTR AS
ASKER BETONGSAGING AS
NOK 14.0m rev. · NOK 4.6m profit

ASKER BETONGSAGING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ASKER BETONGSAGING AS

Who owns ASKER BETONGSAGING AS?

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

What is the revenue of ASKER BETONGSAGING AS?

ASKER BETONGSAGING AS had revenue of NOK 14.0m in 2024.

Who is the general manager of ASKER BETONGSAGING AS?

Frank Ruud is registered as general manager of ASKER BETONGSAGING AS.

Where is ASKER BETONGSAGING AS based?

ASKER BETONGSAGING AS has its business address in Nesbru.

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.