BIZTRAC BETA
COMPANY REGISTER PROFILE
921259719 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 15.06.2026
Construction of residential and non-residential buildings

ZIAREKBYGG AS

Org. no. 921259719 Limited company (AS) Oslo Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 2.2m
Operating profit NOK −12,000
Equity NOK 18,000
Incorporated 2018
Share capital NOK 30,000

Signals

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

ZIAREKBYGG AS is registered as a limited company in Oslo, Oslo with organisation number 921259719. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Oppføring av bygninger.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.2m in revenue and NOK −12,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.2m
Operating profit
NOK −12,000
Equity
NOK 18,000
Est. value
NOK 767,000

Financial health · 2025

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

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

Who owns ZIAREKBYGG AS?

LUKASZ HENRYK ZIAREK
ZIAREKBYGG AS
NOK 2.2m rev. · NOK −12,000 profit

ZIAREKBYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ZIAREKBYGG AS

Who owns ZIAREKBYGG AS?

LUKASZ HENRYK ZIAREK is the largest registered owner, with 100.0%.

What is the revenue of ZIAREKBYGG AS?

ZIAREKBYGG AS had revenue of NOK 2.2m in 2025.

Who is the general manager of ZIAREKBYGG AS?

Lukasz Henryk Ziarek is registered as general manager of ZIAREKBYGG AS.

Where is ZIAREKBYGG AS based?

ZIAREKBYGG 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.