BIZTRAC BETA
Computer consultancy and computer facilities management activities

GAMBIT INVEST AS

Org. no. 911996243 Limited company (AS) Oslo Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −28,000
Equity NOK 1.8m
Incorporated 2013
Share capital NOK 2.1m

Signals

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

GAMBIT INVEST AS is registered as a limited company in Oslo, Oslo with organisation number 911996243. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2013. Registered share capital is NOK 2.1m, divided into 71000 shares. The company's stated purpose is: “Tilby rådgivnings- og driftstjenester, investere i fast eiendom og aksjer, samt deltagelse i annen virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −28,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −28,000
Equity
NOK 1.8m
Est. value
NOK 3.2m

Financial health · 2025

Liquidity
47.20
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
18.9%
Good
Equity as a share of total capital

Who owns GAMBIT INVEST AS?

ANDREAS PARR BJØRNSUND
GAMBIT INVEST AS
NOK 0 rev. · NOK −28,000 profit

GAMBIT INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does GAMBIT INVEST AS own?

GAMBIT INVEST AS holds stakes in 9 companies:

See the full ownership structure →

Frequently asked questions about GAMBIT INVEST AS

Who owns GAMBIT INVEST AS?

ANDREAS PARR BJØRNSUND is the largest registered owner, with 100.0%.

What is the revenue of GAMBIT INVEST AS?

GAMBIT INVEST AS had revenue of NOK 0 in 2025.

Where is GAMBIT INVEST AS based?

GAMBIT INVEST AS has its business address in Oslo.

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.