BIZTRAC BETA
COMPANY REGISTER PROFILE
976525388 ORG. NO. 8 SECTIONS
Active UPDATED 02.09.2026
Other activities of other membership organisations

LIJORDET HUSEIERFORETAK SA

Org. no. 976525388 Co-operation (SA) Bærum Incorporated 1981 Active
Ownership graph ↗
Incorporated 1981

LIJORDET HUSEIERFORETAK SA is registered as a co-operation in Bærum, Akershus with organisation number 976525388. The business is classified under other activities of other membership organisations (NACE 94.992). The company was incorporated in 1981. The company's stated purpose is: “Å ivareta medlemmenes felles interesser i forbindelse med drift, vedlikehold og administrasjon av fellesareal på 1 224,1 m2 med bruksnr 35 og gårdsnr 10 i Bærum. Foretaket har videre til formål og administrere utvendig maling, vedlikehold av felles røropplegg, veier avløpskummer, samtlige tak, takrenner, piper og fyrhuset med 3 garasjer, samt utgifter til drift og vedlikehold av fyringsanlegget og snørydding av veiene. Felles røropplegg omfatter vann-, varme- og avløpsrør, samt dreneringsrør.”.

Former names: LIJORDET HUSEIERLAG BA

Who owns LIJORDET HUSEIERFORETAK SA?

No shareholders are registered for LIJORDET HUSEIERFORETAK SA in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about LIJORDET HUSEIERFORETAK SA

Where is LIJORDET HUSEIERFORETAK SA based?

LIJORDET HUSEIERFORETAK SA has its business address in Eiksmarka.

Property

Business address Nadderudveien 121B, 1359 Eiksmarka
Cadastral unit 3201-35/41/0/0
Building Rekkehus · 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.