BIZTRAC BETA
Construction of residential and non-residential buildings

CU BYGG AS

Org. no. 828471872 Limited company (AS) Aurskog-Høland Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 1.1m
Operating profit NOK −162,000
Equity NOK −521,000
Incorporated 2021
Share capital NOK 30,000

Signals

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

CU BYGG AS is registered as a limited company in Aurskog-Høland, Akershus with organisation number 828471872. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Byggevirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.1m in revenue and NOK −162,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.1m
Operating profit
NOK −162,000
Equity
NOK −521,000

Financial health · 2025

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

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

Who owns CU BYGG AS?

KRUNOSLAV DZIMBEG
CU BYGG AS
NOK 1.1m rev. · NOK −162,000 profit

CU BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about CU BYGG AS

Who owns CU BYGG AS?

KRUNOSLAV DZIMBEG is the largest registered owner, with 100.0%.

What is the revenue of CU BYGG AS?

CU BYGG AS had revenue of NOK 1.1m in 2025.

Who is the general manager of CU BYGG AS?

Krunoslav Dzimbeg is registered as general manager of CU BYGG AS.

Where is CU BYGG AS based?

CU BYGG AS has its business address in Løken.

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.