BIZTRAC BETA
COMPANY REGISTER PROFILE
926934856 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Other technical consultancy

BITVIS AS

Org. no. 926934856 Limited company (AS) Lier Incorporated 2021 Active
Ownership graph ↗
Operating profit NOK −5,000
Equity NOK 5,000
Incorporated 2021
Share capital NOK 30,000

Signals

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

BITVIS AS is registered as a limited company in Lier, Buskerud with organisation number 926934856. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Konsulentvirksomhet innen elektronikkutvikling.”.

Key figures · 2025

Operating profit
NOK −5,000
▼ −3 %
Equity
NOK 5,000
▼ −50 %
Est. value
NOK 8,000

Financial health · 2025

Liquidity
2.05
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
51.1%
Weak
Equity as a share of total capital

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

Who owns BITVIS AS?

BITVIS AS
· NOK −5,000 profit

BITVIS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BITVIS AS

Who owns BITVIS AS?

DIGIVIS AS is the largest registered owner, with 100.0%.

Where is BITVIS AS based?

BITVIS AS has its business address in Tranby.

Property

Business address Grindene 13, 3409 Tranby
Cadastral unit 3312-145/491/0/0
Building Enebolig m/hybel/sokkelleil. · 2 units

2 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

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

Report a problem

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