BIZTRAC BETA
COMPANY REGISTER PROFILE
971477288 ORG. NO. 8 SECTIONS
Active UPDATED 02.09.2026
Activities of business and employers membership organisations

LEVERANDØRFORENING FOR KOSTTILSKUDD OG NÆRINGSMIDLER (LKN)

Org. no. 971477288 Association/club/organisation (FLI) Oslo Incorporated 1988 Active
Ownership graph ↗
Incorporated 1988

LEVERANDØRFORENING FOR KOSTTILSKUDD OG NÆRINGSMIDLER (LKN) is registered as a association/club/organisation in Oslo, Oslo with organisation number 971477288. The business is classified under activities of business and employers membership organisations (NACE 94.110). The company was incorporated in 1988.

Former names: HELSEKOSTRÅDET, HELSEKOSTBRANSJENS LEVERANDØR- FORENING, NATURMIDDELINDUSTRIFORENINGEN

Who owns LEVERANDØRFORENING FOR KOSTTILSKUDD OG NÆRINGSMIDLER (LKN)?

No shareholders are registered for LEVERANDØRFORENING FOR KOSTTILSKUDD OG NÆRINGSMIDLER (LKN) in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about LEVERANDØRFORENING FOR KOSTTILSKUDD OG NÆRINGSMIDLER (LKN)

Who is the general manager of LEVERANDØRFORENING FOR KOSTTILSKUDD OG NÆRINGSMIDLER (LKN)?

Hogne Vik is registered as general manager of LEVERANDØRFORENING FOR KOSTTILSKUDD OG NÆRINGSMIDLER (LKN).

Where is LEVERANDØRFORENING FOR KOSTTILSKUDD OG NÆRINGSMIDLER (LKN) based?

LEVERANDØRFORENING FOR KOSTTILSKUDD OG NÆRINGSMIDLER (LKN) has its business address in Oslo.

Property

Business address c/o Hogne Vik Holmenkollveien 87A, 0784 Oslo
Cadastral unit 301-33/366/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.