BIZTRAC BETA
Retail sale of information and communication equipment

ZETSTOR DATA AS

Org. no. 911733714 Limited company (AS) Bærum Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 452,000
Operating profit NOK 11,000
Equity NOK 680,000
Incorporated 2013
Share capital NOK 100,000

Signals

1 flags
  • Nylig endring 2026-02-09 Adresseendring registrert 2026-02-09.

ZETSTOR DATA AS is registered as a limited company in Bærum, Akershus with organisation number 911733714. The business is classified under retail sale of information and communication equipment (NACE 47.400). The company was incorporated in 2013. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Salg, service og support av IKT produkter, og andre produkter som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender.”. The most recent filed accounts, for the 2025 financial year, show NOK 452,000 in revenue and NOK 11,000 in operating profit.

Key figures · 2025

Revenue
NOK 452,000
Operating profit
NOK 11,000
Equity
NOK 680,000
Est. value
NOK 423,000

Financial health · 2025

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

Who owns ZETSTOR DATA AS?

ARVE DAN ISAKSEN
ZETSTOR DATA AS
NOK 452,000 rev. · NOK 11,000 profit

ZETSTOR DATA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ZETSTOR DATA AS

Who owns ZETSTOR DATA AS?

ARVE DAN ISAKSEN is the largest registered owner, with 100.0%.

What is the revenue of ZETSTOR DATA AS?

ZETSTOR DATA AS had revenue of NOK 452,000 in 2025.

Where is ZETSTOR DATA AS based?

ZETSTOR DATA AS has its business address in Fornebu.

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.