biztrac. BETA
COMPANY REGISTER PROFILE
940106966 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Business and other management consultancy activities

Abacus Consult AS

Org. no. 940106966 Limited company (AS) Bærum Incorporated 1986 Active
Ownership graph ↗
Operating profit NOK −112,000
Equity NOK 4.8m
Incorporated 1986
Share capital NOK 870,000

Signals

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

Abacus Consult AS is registered as a limited company in Bærum, Akershus with organisation number 940106966. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 1986. Registered share capital is NOK 870,000, divided into 87000 shares. The company's stated purpose is: “Utføre bedriftsrådgivningsoppdrag for andre virksomheter. Selskapet skal videre aktivt forvalte overskuddslikviditet gjennom finans- og/eller realinvesteringer, herunder finansielle derivater.”.

Key figures · 2025

Operating profit
NOK −112,000
▲ +20 %
Equity
NOK 4.8m
▲ +3 %
Est. value
NOK 3.3m

Financial health · 2025

Liquidity
11.05
Very good
Current assets ÷ current liabilities
Profitability
2.4%
Weak
Return on total assets
Solidity
86.9%
Very good
Equity as a share of total capital

Who owns Abacus Consult AS?

Abacus Consult AS has 3 registered shareholders:

All shareholders and roles →

Which companies does Abacus Consult AS own?

Abacus Consult AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about Abacus Consult AS

Who owns Abacus Consult AS?

Dag Morten Iversen is the largest registered owner, with 45.7%.

Who is the general manager of Abacus Consult AS?

Dag Morten Iversen is registered as general manager of Abacus Consult AS.

Where is Abacus Consult AS based?

Abacus Consult AS has its business address in Rykkinn.

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.