BIZTRAC BETA
COMPANY REGISTER PROFILE
916757379 ORG. NO. 8 SECTIONS
Active UPDATED 02.09.2026
Regulation of health care, education, cultural services and other social services

LILLEHAMMER KOMMUNE OPPVEKST UTDANNING OG KULTUR

Org. no. 916757379 Organisation section (ORGL) Lillehammer Incorporated 2013 Active
Ownership graph ↗
Incorporated 2013
Employees 1407

LILLEHAMMER KOMMUNE OPPVEKST UTDANNING OG KULTUR is registered as a organisation section in Lillehammer, Innlandet with organisation number 916757379. The business is classified under regulation of health care, education, cultural services and other social services (NACE 84.120). The company was incorporated in 2013 and has 1407 registered employees.

Former names: LILLEHAMMER KOMMUNE OPPVEKST, UTDANNING OG KULTUR

Who owns LILLEHAMMER KOMMUNE OPPVEKST UTDANNING OG KULTUR?

No shareholders are registered for LILLEHAMMER KOMMUNE OPPVEKST UTDANNING OG KULTUR in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about LILLEHAMMER KOMMUNE OPPVEKST UTDANNING OG KULTUR

Who is the general manager of LILLEHAMMER KOMMUNE OPPVEKST UTDANNING OG KULTUR?

Tord Buer Olsen is registered as general manager of LILLEHAMMER KOMMUNE OPPVEKST UTDANNING OG KULTUR.

Where is LILLEHAMMER KOMMUNE OPPVEKST UTDANNING OG KULTUR based?

LILLEHAMMER KOMMUNE OPPVEKST UTDANNING OG KULTUR has its business address in Lillehammer.

Property

Business address Storgata 51, 2609 Lillehammer
Cadastral unit 3405-200/25/0/0
Building Kontor- og administrasjonsbygning, rådhus · 6 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.