BIZTRAC BETA
Computer consultancy and computer facilities management activities

BET IT AS

Org. no. 919944102 Limited company (AS) Ullensaker Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −61,000
Equity NOK −999,000
Incorporated 2017
Share capital NOK 10.0m

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−999k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−61k kr).

BET IT AS is registered as a limited company in Ullensaker, Akershus with organisation number 919944102. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2017. Registered share capital is NOK 10.0m, divided into 1000 shares. The company's stated purpose is: “Investere i selskaper som driver innen IT- og applikasjonsprogramvarebransjen.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −61,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −61,000
Equity
NOK −999,000

Financial health · 2024

Liquidity
0.08
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-2.9%
Weak
Equity as a share of total capital

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

Who owns BET IT AS?

KGI AS
BET IT AS
NOK 0 rev. · NOK −61,000 profit

BET IT AS has 2 registered shareholders:

All shareholders and roles →

Which companies does BET IT AS own?

BET IT AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about BET IT AS

Who owns BET IT AS?

KGI AS is the largest registered owner, with 98.0%.

What is the revenue of BET IT AS?

BET IT AS had revenue of NOK 0 in 2024.

Where is BET IT AS based?

BET IT AS has its business address in Jessheim.

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.