BIZTRAC BETA
Hotels and similar accommodation

STOREBAUG HOTELL OG KRO AS

Org. no. 919652969 Limited company (AS) Moss Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 24.8m
Operating profit NOK 3.7m
Equity NOK 2.4m
Incorporated 2017
Employees 38
Share capital NOK 100,000

STOREBAUG HOTELL OG KRO AS is registered as a limited company in Moss, Østfold with organisation number 919652969. The business is classified under hotels and similar accommodation (NACE 55.100). The company was incorporated in 2017 and has 38 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Drift av hoteller, pensjonater og moteller med restaurant samt utleie av fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 24.8m in revenue and NOK 3.7m in operating profit.

Key figures · 2024

Revenue
NOK 24.8m
Operating profit
NOK 3.7m
Equity
NOK 2.4m
Est. value
NOK 15.2m

Financial health · 2024

Liquidity
1.41
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
29.8%
Good
Equity as a share of total capital

Who owns STOREBAUG HOTELL OG KRO AS?

KJH EIENDOM AS
STOREBAUG HOTELL OG KRO AS
NOK 24.8m rev. · NOK 3.7m profit

STOREBAUG HOTELL OG KRO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STOREBAUG HOTELL OG KRO AS

Who owns STOREBAUG HOTELL OG KRO AS?

KJH EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of STOREBAUG HOTELL OG KRO AS?

STOREBAUG HOTELL OG KRO AS had revenue of NOK 24.8m in 2024.

Who is the general manager of STOREBAUG HOTELL OG KRO AS?

Therese Herje Dahlmann is registered as general manager of STOREBAUG HOTELL OG KRO AS.

Where is STOREBAUG HOTELL OG KRO AS based?

STOREBAUG HOTELL OG KRO AS has its business address in Moss.

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.