BIZTRAC BETA
Computer programming activities

BITWISE GROUP AS

Org. no. 932739216 Limited company (AS) Bergen Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −6,000
Equity NOK 29,000
Incorporated 2023
Share capital NOK 40,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−6k kr).

BITWISE GROUP AS is registered as a limited company in Bergen, Vestland with organisation number 932739216. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2023. Registered share capital is NOK 40,000, divided into 40000 shares. The company's stated purpose is: “Investering i næringsvirksomhet, herunder aksjer og andeler, samt deltagelse i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −6,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −6,000
Equity
NOK 29,000
Est. value
NOK 53,000

Financial health · 2024

Liquidity
0.82
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
83.9%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns BITWISE GROUP AS?

CASPER BEYER
BITWISE GROUP AS
NOK 0 rev. · NOK −6,000 profit

BITWISE GROUP AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BITWISE GROUP AS own?

BITWISE GROUP AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BITWISE GROUP AS

Who owns BITWISE GROUP AS?

CASPER BEYER is the largest registered owner, with 100.0%.

What is the revenue of BITWISE GROUP AS?

BITWISE GROUP AS had revenue of NOK 0 in 2024.

Where is BITWISE GROUP AS based?

BITWISE GROUP AS has its business address in Bjørndalstræ.

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.