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

TGL OIL EXPLORATION & CATTLE AS

Org. no. 937716311 Limited company (AS) Oslo Incorporated 2026 Active
Ownership graph ↗
Incorporated 2026
Share capital NOK 30,000

Signals

3 flags
  • Mangler regnskap Ingen årsregnskap er registrert for selskapet.
  • Nystiftet selskap Selskapet ble stiftet 2026-04-29.
  • Nylig endring 2026-08-04 Adresseendring registrert 2026-08-04.

TGL OIL EXPLORATION & CATTLE AS is registered as a limited company in Oslo, Oslo with organisation number 937716311. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2026. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Å foreta investeringer og annen virksomhet som står i forbindelse med dette.”.

Former names: AFAS 290426-09 AS

Who owns TGL OIL EXPLORATION & CATTLE AS?

No shareholders are registered for TGL OIL EXPLORATION & CATTLE AS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about TGL OIL EXPLORATION & CATTLE AS

Who is the general manager of TGL OIL EXPLORATION & CATTLE AS?

Tor Georg Liby is registered as general manager of TGL OIL EXPLORATION & CATTLE AS.

Where is TGL OIL EXPLORATION & CATTLE AS based?

TGL OIL EXPLORATION & CATTLE AS has its business address in Oslo.

Property

Business address Middelthuns gate 17G, 0368 Oslo
Cadastral unit 301-215/226/0/0
Building Stort frittliggende boligbygg på 5 etg el mer · 190 units

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