BIZTRAC BETA
COMPANY REGISTER PROFILE
936117872 ORG. NO. 8 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

ML GROUP VENTURES AS

Org. no. 936117872 Limited company (AS) Stavanger Incorporated 2025 Active
Ownership graph ↗
Incorporated 2025
Share capital NOK 30,000

Signals

2 flags
  • Mangler regnskap Ingen årsregnskap er registrert for selskapet.
  • Nylig endring 2026-07-01 Adresseendring registrert 2026-07-01.

ML GROUP VENTURES AS is registered as a limited company in Stavanger, Rogaland with organisation number 936117872. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Kjøp og salg av eiendom, verdipapirer og aksjer, samt investeringer, oppstart og drift av selskap, hovedsakelig innen hotell og restaurantnæring og tilliggende næringer.”.

Former names: JEHS 84 825 AS

Who owns ML GROUP VENTURES AS?

ML GROUP VENTURES AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ML GROUP VENTURES AS

Who owns ML GROUP VENTURES AS?

MATHEW LEONG HOLDING AS is the largest registered owner, with 92.0%.

Who is the general manager of ML GROUP VENTURES AS?

Seng Chien Leong is registered as general manager of ML GROUP VENTURES AS.

Where is ML GROUP VENTURES AS based?

ML GROUP VENTURES AS has its business address in Stavanger.

Property

Business address U0101 Tinngata 12, 4014 Stavanger
Cadastral unit 1103-53/425/0/0
Building Stort frittliggende boligbygg på 5 etg el mer · 61 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.