BIZTRAC BETA
Computer programming activities

ZEIPT AS

Org. no. 916809026 Limited company (AS) Oslo Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 54,000
Operating profit NOK −679,000
Equity NOK 1.9m
Incorporated 2016
Share capital NOK 643,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−679k kr).
  • Nylig endring 2026-02-04 Adresseendring registrert 2026-02-04.

ZEIPT AS is registered as a limited company in Oslo, Oslo with organisation number 916809026. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2016. Registered share capital is NOK 643,000, divided into 1285212 shares. The company's stated purpose is: “Zeipt skal tilby en kommunikasjons plattform for digitale kvitteringer for banker, butikker og forbrukere, ved å tilby butikker muligheten til å levere kundenes kvitteringer over nett.”. The most recent filed accounts, for the 2024 financial year, show NOK 54,000 in revenue and NOK −679,000 in operating profit.

Key figures · 2024

Revenue
NOK 54,000
Operating profit
NOK −679,000
Equity
NOK 1.9m
Est. value
NOK 3.5m

Financial health · 2024

Liquidity
0.08
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
30.3%
Good
Equity as a share of total capital

Who owns ZEIPT AS?

VENTURESDEV AB
ZEIPT AS
NOK 54,000 rev. · NOK −679,000 profit

ZEIPT AS has 20+ registered shareholders:

All shareholders and roles →

Which companies does ZEIPT AS own?

ZEIPT AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ZEIPT AS

Who owns ZEIPT AS?

VENTURESDEV AB is the largest registered owner, with 53.4%.

What is the revenue of ZEIPT AS?

ZEIPT AS had revenue of NOK 54,000 in 2024.

Where is ZEIPT AS based?

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