BIZTRAC BETA
Construction of residential and non-residential buildings

BETONGVERK AS

Org. no. 929983890 Limited company (AS) Oslo Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 339,000
Operating profit NOK −37,000
Equity NOK 46,000
Incorporated 2022
Share capital NOK 30,000

Signals

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

BETONGVERK AS is registered as a limited company in Oslo, Oslo with organisation number 929983890. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Oppføring av bygninger. Entreprenørvirksomhet. Konsulent innen bygg og anlegg.”. The most recent filed accounts, for the 2025 financial year, show NOK 339,000 in revenue and NOK −37,000 in operating profit.

Key figures · 2025

Revenue
NOK 339,000
Operating profit
NOK −37,000
Equity
NOK 46,000
Est. value
NOK 138,000

Financial health · 2024

Liquidity
1.73
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
42.1%
Weak
Equity as a share of total capital

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

Who owns BETONGVERK AS?

ANDRIJANA GASPAROVIC
BETONGVERK AS
NOK 339,000 rev. · NOK −37,000 profit

BETONGVERK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BETONGVERK AS

Who owns BETONGVERK AS?

ANDRIJANA GASPAROVIC is the largest registered owner, with 100.0%.

What is the revenue of BETONGVERK AS?

BETONGVERK AS had revenue of NOK 339,000 in 2025.

Who is the general manager of BETONGVERK AS?

Andrijana Gasparovic is registered as general manager of BETONGVERK AS.

Where is BETONGVERK AS based?

BETONGVERK AS has its business address in Oslo.

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.