BIZTRAC BETA
COMPANY REGISTER PROFILE
928760723 ORG. NO. 7 SECTIONS
Active UPDATED 02.09.2026
Other real estate activities on a fee or contract basis

SJØBUA HETLEVIK SA

Org. no. 928760723 Co-operation (SA) Askøy Incorporated 2022 Active
Ownership graph ↗
Incorporated 2022

SJØBUA HETLEVIK SA is registered as a co-operation in Askøy, Vestland with organisation number 928760723. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2022. The company's stated purpose is: “Felles drift av kran og bryggeanlegg for medlemmene. Foretaket har som formål å fremme medlemmenes økonomiske interesser gjennom deres deltakelse i virksomheten som kjøpere av varer eller tjenester fra foretaket. Virksomhetens avkastning, bortsett fra en normal forrentning av innskutt kapital, blir enten stående i virksomheten eller fordelt blant medlemmene på grunnlag av deres andel i omsetningen med foretaket.”.

Who owns SJØBUA HETLEVIK SA?

No shareholders are registered for SJØBUA HETLEVIK SA in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about SJØBUA HETLEVIK SA

Who is the general manager of SJØBUA HETLEVIK SA?

Pål-Stian Pedersen is registered as general manager of SJØBUA HETLEVIK SA.

Where is SJØBUA HETLEVIK SA based?

SJØBUA HETLEVIK SA has its business address in Hetlevik.

Property

Business address Hetlevikvegen 89, 5304 Hetlevik
Cadastral unit 4627-12/145/0/0
Building Stort frittliggende boligbygg på 3 og 4 etg · 36 units

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