BIZTRAC BETA
COMPANY REGISTER PROFILE
970015302 ORG. NO. 2009 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Sports activities n.e.c.

NORGES TENNIS- OG PADELFORBUND

Org. no. 970015302 Association/club/organisation (FLI) Oslo Incorporated 1909 Active
Ownership graph ↗
Incorporated 1909
Employees 17

NORGES TENNIS- OG PADELFORBUND is registered as a association/club/organisation in Oslo, Oslo with organisation number 970015302. The business is classified under sports activities n.e.c. (NACE 93.190). The company was incorporated in 1909 and has 17 registered employees. The company's stated purpose is: “NTFs formål er å fremme tennis- og padelidretten i Norge, og representere idrettene internasjonalt.”.

Former names: NORGES TENNISFORBUND V/B KALSTAD, NORGES TENNISFORBUND

Who owns NORGES TENNIS- OG PADELFORBUND?

No shareholders are registered for NORGES TENNIS- OG PADELFORBUND in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Which companies does NORGES TENNIS- OG PADELFORBUND own?

NORGES TENNIS- OG PADELFORBUND holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about NORGES TENNIS- OG PADELFORBUND

Who is the general manager of NORGES TENNIS- OG PADELFORBUND?

Aslak Juliebø Paulsen is registered as general manager of NORGES TENNIS- OG PADELFORBUND.

Where is NORGES TENNIS- OG PADELFORBUND based?

NORGES TENNIS- OG PADELFORBUND has its business address in Oslo.

Property

Business address Eikenga 4, 0579 Oslo
Cadastral unit 301-122/416/0/0
Building Annen idrettsbygning · 2 units

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