BIZTRAC BETA
COMPANY REGISTER PROFILE
936758479 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

GENBA INVEST AS

Org. no. 936758479 Limited company (AS) Bærum Incorporated 2025 Active
Ownership graph ↗
Equity NOK 3.8m
Incorporated 2025
Share capital NOK 30,000

Signals

1 flags
  • Nystiftet selskap Selskapet ble stiftet 2025-11-24.

GENBA INVEST AS is registered as a limited company in Bærum, Akershus with organisation number 936758479. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 100000 shares. The company's stated purpose is: “Investere i aksjer og verdipapirer samt det som naturlig står i forbindelse med dette.”.

Key figures · 2025

Equity
NOK 3.8m
Est. value
NOK 4.4m

Financial health · 2025

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

Who owns GENBA INVEST AS?

GENBA INVEST AS has 4 registered shareholders:

All shareholders and roles →

Which companies does GENBA INVEST AS own?

GENBA INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about GENBA INVEST AS

Who owns GENBA INVEST AS?

FANUS AS is the largest registered owner, with 39.5%.

Where is GENBA INVEST AS based?

GENBA INVEST AS has its business address in Sandvika.

Property

Business address c/o Johs. Hansen & Co AS Sandviksveien 163, 1337 Sandvika
Cadastral unit 3201-7/18/0/0
Building Butikkbygning · 2 units

33 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.