BIZTRAC BETA
Hotels and similar accommodation

KRONEN GAARD AS

Org. no. 939522352 Limited company (AS) Sandnes Incorporated 1986 Active
Ownership graph ↗
Revenue 2024 NOK 28.1m
Operating profit NOK 2.0m
Equity NOK 8.9m
Incorporated 1986
Employees 53
Share capital NOK 1.1m

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

KRONEN GAARD AS is registered as a limited company in Sandnes, Rogaland with organisation number 939522352. The business is classified under hotels and similar accommodation (NACE 55.100). The company was incorporated in 1986 and has 53 registered employees. Registered share capital is NOK 1.1m, divided into 200 shares. The company's stated purpose is: “Hotel- og restaurantdrift samt utleie av hytter og alt som hermed er forbundet.”. The most recent filed accounts, for the 2024 financial year, show NOK 28.1m in revenue and NOK 2.0m in operating profit.

Key figures · 2024

Revenue
NOK 28.1m
Operating profit
NOK 2.0m
Equity
NOK 8.9m
Est. value
NOK 11.8m

Financial health · 2024

Liquidity
0.23
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
15.8%
Satisfactory
Equity as a share of total capital

Who owns KRONEN GAARD AS?

KRONENGRUPPEN AS
KRONEN GAARD AS
NOK 28.1m rev. · NOK 2.0m profit

KRONEN GAARD AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KRONEN GAARD AS own?

KRONEN GAARD AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about KRONEN GAARD AS

Who owns KRONEN GAARD AS?

KRONENGRUPPEN AS is the largest registered owner, with 100.0%.

What is the revenue of KRONEN GAARD AS?

KRONEN GAARD AS had revenue of NOK 28.1m in 2024.

Where is KRONEN GAARD AS based?

KRONEN GAARD AS has its business address in Sandnes.

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.