BIZTRAC BETA
Buying and selling of own real estate

SAGENE TECH VENTURES AS

Org. no. 917405883 Limited company (AS) Bærum Incorporated 2016 Active
Ownership graph ↗
Operating profit NOK −73,000
Equity NOK 409,000
Incorporated 2016
Share capital NOK 35,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−73k kr).
  • Nylig endring 2026-06-08 Adresseendring registrert 2026-06-08.

SAGENE TECH VENTURES AS is registered as a limited company in Bærum, Akershus with organisation number 917405883. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2016. Registered share capital is NOK 35,000, divided into 35000 shares. The company's stated purpose is: “Investering i og handel med verdipapirer, eiendom og andre formuesgoder, samt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender.”.

Key figures · 2024

Operating profit
NOK −73,000
Equity
NOK 409,000
Est. value
NOK 373,000

Financial health · 2024

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

Who owns SAGENE TECH VENTURES AS?

HKG HOLDING AS
SAGENE TECH VENTURES AS
· NOK −73,000 profit

SAGENE TECH VENTURES AS has 7 registered shareholders:

All shareholders and roles →

Which companies does SAGENE TECH VENTURES AS own?

SAGENE TECH VENTURES AS holds stakes in 11 companies:

See the full ownership structure →

Frequently asked questions about SAGENE TECH VENTURES AS

Who owns SAGENE TECH VENTURES AS?

HKG HOLDING AS is the largest registered owner, with 14.3%.

Where is SAGENE TECH VENTURES AS based?

SAGENE TECH VENTURES AS has its business address in Stabekk.

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.