BIZTRAC BETA
COMPANY REGISTER PROFILE
924420758 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Residential care activities in other types of accommodation n.e.c.

GJESTEHUSET ÅLGÅRD AS

Org. no. 924420758 Limited company (AS) Gjesdal Incorporated 2019 Active
Ownership graph ↗
Equity NOK 19
Incorporated 2019
Share capital NOK 30,000

GJESTEHUSET ÅLGÅRD AS is registered as a limited company in Gjesdal, Rogaland with organisation number 924420758. The business is classified under residential care activities in other types of accommodation n.e.c. (NACE 87.999). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Drift av et omsorgssenter samt andre produkter/tjenester som naturlig hører til dette.”.

Key figures · 2025

Equity
NOK 19
▲ +0 %
Est. value
NOK 30

Financial health · 2025

Liquidity
Not available
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
100.0%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns GJESTEHUSET ÅLGÅRD AS?

GJESTEHUSET ÅLGÅRD AS

GJESTEHUSET ÅLGÅRD AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GJESTEHUSET ÅLGÅRD AS

Who owns GJESTEHUSET ÅLGÅRD AS?

KRISTKIRKEN ÅLGÅRD is the largest registered owner, with 100.0%.

Where is GJESTEHUSET ÅLGÅRD AS based?

GJESTEHUSET ÅLGÅRD AS has its business address in Ålgård.

Property

Business address Opstadveien 3, 4331 Ålgård
Cadastral unit 1122-6/581/0/0

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