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

BISPØYAN HYTTEEIERLAG SA

Org. no. 893552812 Co-operation (SA) Trondheim Incorporated 1978 Active
Ownership graph ↗
Incorporated 1978

BISPØYAN HYTTEEIERLAG SA is registered as a co-operation in Trondheim, Trøndelag with organisation number 893552812. The business is classified under other activities of other membership organisations (NACE 94.992). The company was incorporated in 1978. The company's stated purpose is: “Å ivareta andelseiernes interesse som tomtefestere/tomteeiere eller eiere av hytter og fritidsboliger i Bispøyan, og være kontaktledd mellom den enkelte tomtefester/tomteeier/hytteeier på den ene side, og kommune og offentlige og private organer på den andre side. Alle andelseierne har samme rettigheter og plikter i forhold til hytteeierlaget. BHL SA skal ivareta andelseiernes behov for marina-anlegg og parkeringsplasser bl. i Grefsnesvågen ved å etablere og drifte slike anlegg.”.

Former names: BISPØYAN HYTTEEIERLAG BA

Who owns BISPØYAN HYTTEEIERLAG SA?

No shareholders are registered for BISPØYAN HYTTEEIERLAG SA in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about BISPØYAN HYTTEEIERLAG SA

Where is BISPØYAN HYTTEEIERLAG SA based?

BISPØYAN HYTTEEIERLAG SA has its business address in Tiller.

Property

Business address c/o KL Økonomi og HR AS Vestre Rosten 81, 7075 Tiller
Cadastral unit 5001-315/425/0/0
Building Annen kontorbygning · 1 unit

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