BIZTRAC BETA
Development of building projects

ZIRKON EIENDOM AS

Org. no. 931724991 Limited company (AS) Stjørdal Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −9,000
Equity NOK 1.2m
Incorporated 2023
Share capital NOK 1.2m

Signals

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

ZIRKON EIENDOM AS is registered as a limited company in Stjørdal, Trøndelag with organisation number 931724991. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2023. Registered share capital is NOK 1.2m, divided into 1200 shares. The company's stated purpose is: “Å erverve, eie, utvikle og forvalte eiendom, og alt hva dermed står i forbindelse. Selskapet kan med aksjeinnskudd eller på annen måte delta i virksomhet med tilsvarende formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −9,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −9,000
Equity
NOK 1.2m
Est. value
NOK 1.1m

Financial health · 2025

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

Who owns ZIRKON EIENDOM AS?

ONYX HOLDING AS
ZIRKON EIENDOM AS
NOK 0 rev. · NOK −9,000 profit

ZIRKON EIENDOM AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about ZIRKON EIENDOM AS

Who owns ZIRKON EIENDOM AS?

ONYX HOLDING AS is the largest registered owner, with 33.3%.

What is the revenue of ZIRKON EIENDOM AS?

ZIRKON EIENDOM AS had revenue of NOK 0 in 2025.

Who is the general manager of ZIRKON EIENDOM AS?

Casper Arntzen is registered as general manager of ZIRKON EIENDOM AS.

Where is ZIRKON EIENDOM AS based?

ZIRKON EIENDOM AS has its business address in Stjørdal.

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.