BIZTRAC BETA
COMPANY REGISTER PROFILE
935718953 ORG. NO. 7 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

TINGELING HOLDING AS

Org. no. 935718953 Limited company (AS) Asker Incorporated 2025 Active
Ownership graph ↗
Incorporated 2025
Share capital NOK 3.0m

Signals

1 flags
  • Mangler regnskap Ingen årsregnskap er registrert for selskapet.

TINGELING HOLDING AS is registered as a limited company in Asker, Akershus with organisation number 935718953. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2025. Registered share capital is NOK 3.0m, divided into 100 shares. The company's stated purpose is: “Deltakelse i andre selskap, rådgivningsvirksomhet og forvaltning av selskapets kapital gjennom annen investeringsvirksomhet og utlån, kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak, og andre produkter/tjenester som naturlig hører til dette. Selskapet kan også drive med kjøp/drift av fast eiendom.”.

Who owns TINGELING HOLDING AS?

TINGELING HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does TINGELING HOLDING AS own?

TINGELING HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about TINGELING HOLDING AS

Who owns TINGELING HOLDING AS?

DAVID JOHN WEICHBRODT is the largest registered owner, with 100.0%.

Where is TINGELING HOLDING AS based?

TINGELING HOLDING AS has its business address in Vollen.

Property

Business address Heslebergveien 28, 1390 Vollen
Cadastral unit 3203-65/46/0/0
Building Enebolig · 1 unit

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.