BIZTRAC BETA
Hotels and similar accommodation

BYRKJEDALSTUNET AS

Org. no. 989762699 Limited company (AS) Gjesdal Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 22.0m
Operating profit NOK −1.6m
Equity NOK 4.9m
Incorporated 2006
Employees 48
Share capital NOK 4.8m

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1,6 mill kr).

BYRKJEDALSTUNET AS is registered as a limited company in Gjesdal, Rogaland with organisation number 989762699. The business is classified under hotels and similar accommodation (NACE 55.100). The company was incorporated in 2006 and has 48 registered employees. Registered share capital is NOK 4.8m, divided into 500 shares. The company's stated purpose is: “Restaurant- og hotelldrift, drift overnatting og hva hermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 22.0m in revenue and NOK −1.6m in operating profit.

Key figures · 2024

Revenue
NOK 22.0m
Operating profit
NOK −1.6m
Equity
NOK 4.9m
Est. value
NOK 17.7m

Financial health · 2024

Liquidity
1.44
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
59.5%
Very good
Equity as a share of total capital

Who owns BYRKJEDALSTUNET AS?

BYRKJEDALSTUNET LYS AS
BYRKJEDALSTUNET AS
NOK 22.0m rev. · NOK −1.6m profit

BYRKJEDALSTUNET AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BYRKJEDALSTUNET AS

Who owns BYRKJEDALSTUNET AS?

BYRKJEDALSTUNET LYS AS is the largest registered owner, with 100.0%.

What is the revenue of BYRKJEDALSTUNET AS?

BYRKJEDALSTUNET AS had revenue of NOK 22.0m in 2024.

Who is the general manager of BYRKJEDALSTUNET AS?

Randi Øvstebø is registered as general manager of BYRKJEDALSTUNET AS.

Where is BYRKJEDALSTUNET AS based?

BYRKJEDALSTUNET AS has its business address in Dirdal.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.