biztrac. BETA
COMPANY REGISTER PROFILE
922973318 ORG. NO. 2025 ACCOUNTS 11 SECTIONS
Active UPDATED 03.10.2026
Other software publishing

ARITMA AS

Org. no. 922973318 Limited company (AS) Bergen Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 85.7m
Operating profit NOK 4.8m
Equity NOK 11.9m
Incorporated 2019
Employees 67
Share capital NOK 845,000

ARITMA AS is registered as a limited company in Bergen, Vestland with organisation number 922973318. The business is classified under other software publishing (NACE 58.290). The company was incorporated in 2019 and has 67 registered employees. Registered share capital is NOK 845,000, divided into 38424 shares. The company's stated purpose is: “Utvikling og salg av standard og skreddersydd programvare samt salg av EDB relaterte konsulent- tjenester og virksomhet som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 85.7m in revenue and NOK 4.8m in operating profit.

Former names: ZDATA DRIFT AS, ZDATA AS

Key figures · 2025

Revenue
NOK 85.7m
▲ +66 %
Operating profit
NOK 4.8m
▲ +404 %
Equity
NOK 11.9m
▲ +363 %
Est. value
NOK 27.5m

Financial health · 2025

Liquidity
1.24
Satisfactory
Current assets ÷ current liabilities
Profitability
19.9%
Very good
Return on total assets
Solidity
31.2%
Good
Equity as a share of total capital

Who owns ARITMA AS?

ARITMA AS
NOK 85.7m rev. · NOK 4.8m profit

ARITMA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ARITMA AS

Who owns ARITMA AS?

ARITMA INTERNATIONAL AS is the largest registered owner, with 100.0%.

What is the revenue of ARITMA AS?

ARITMA AS had revenue of NOK 85.7m in 2025.

Who is the general manager of ARITMA AS?

Thor Kristian Ravnanger Seth is registered as general manager of ARITMA AS.

Where is ARITMA AS based?

ARITMA AS has its business address in Laksevåg.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.