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

CIPHER HOLDING AS

Org. no. 924688513 Limited company (AS) Bergen Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −73,000
Equity NOK 1.2m
Incorporated 2020
Share capital NOK 1.0m

Signals

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

CIPHER HOLDING AS is registered as a limited company in Bergen, Vestland with organisation number 924688513. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2020. Registered share capital is NOK 1.0m, divided into 1000000 shares. The company's stated purpose is: “Holdingselskap som investerer i aksjer i andre selskaper, alt som hører naturlig til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −73,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −73,000
▼ −7 %
Equity
NOK 1.2m
▼ −14 %
Est. value
NOK 19.5m

Financial health · 2025

Liquidity
1.31
Satisfactory
Current assets ÷ current liabilities
Profitability
79.1%
Very good
Return on total assets
Solidity
37.2%
Good
Equity as a share of total capital

Who owns CIPHER HOLDING AS?

CIPHER HOLDING AS has 4 registered shareholders:

All shareholders and roles →

Which companies does CIPHER HOLDING AS own?

CIPHER HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about CIPHER HOLDING AS

Who owns CIPHER HOLDING AS?

ABELSEN HOLDING AS is the largest registered owner, with 26.7%.

What is the revenue of CIPHER HOLDING AS?

CIPHER HOLDING AS had revenue of NOK 0 in 2025.

Where is CIPHER HOLDING AS based?

CIPHER HOLDING AS has its business address in Bergen.

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.