BIZTRAC BETA
Computer programming activities

OZ HOLDING AS

Org. no. 920203019 Limited company (AS) Gjerstad Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 236,000
Operating profit NOK 220,000
Equity NOK 2.0m
Incorporated 2017
Share capital NOK 30,000

OZ HOLDING AS is registered as a limited company in Gjerstad, Agder with organisation number 920203019. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Salg av konsulenttjenester, utleie av driftsmidler, kjøp og salg av varer, investere i aksjer og andeler i andre selskaper samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 236,000 in revenue and NOK 220,000 in operating profit.

Key figures · 2024

Revenue
NOK 236,000
Operating profit
NOK 220,000
Equity
NOK 2.0m
Est. value
NOK 1.9m

Financial health · 2025

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

Who owns OZ HOLDING AS?

YING ZHOU
OZ HOLDING AS
NOK 236,000 rev. · NOK 220,000 profit

OZ HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does OZ HOLDING AS own?

OZ HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about OZ HOLDING AS

Who owns OZ HOLDING AS?

YING ZHOU is the largest registered owner, with 50.0%.

What is the revenue of OZ HOLDING AS?

OZ HOLDING AS had revenue of NOK 236,000 in 2024.

Who is the general manager of OZ HOLDING AS?

Odd Øygarden is registered as general manager of OZ HOLDING AS.

Where is OZ HOLDING AS based?

OZ HOLDING AS has its business address in Gjerstad.

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.