BIZTRAC BETA
Rental and operating of own or leased real estate

FORUS LAGERHOTELL AS

Org. no. 924977396 Limited company (AS) Time Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 468,000
Operating profit NOK 44,000
Equity NOK 74,000
Incorporated 2020
Share capital NOK 30,000

FORUS LAGERHOTELL AS is registered as a limited company in Time, Rogaland with organisation number 924977396. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Utleie av eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 468,000 in revenue and NOK 44,000 in operating profit.

Key figures · 2025

Revenue
NOK 468,000
Operating profit
NOK 44,000
Equity
NOK 74,000
Est. value
NOK 158,000

Financial health · 2025

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

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

Who owns FORUS LAGERHOTELL AS?

NORSKE LAGERHOTELL AS
FORUS LAGERHOTELL AS
NOK 468,000 rev. · NOK 44,000 profit

FORUS LAGERHOTELL AS has 1 registered shareholder:

All shareholders and roles →

Group structure

FORUS LAGERHOTELL AS er morselskap for 1 datterselskap:

Frequently asked questions about FORUS LAGERHOTELL AS

Who owns FORUS LAGERHOTELL AS?

NORSKE LAGERHOTELL AS is the largest registered owner, with 100.0%.

What is the revenue of FORUS LAGERHOTELL AS?

FORUS LAGERHOTELL AS had revenue of NOK 468,000 in 2025.

Who is the general manager of FORUS LAGERHOTELL AS?

Henning Bonnez is registered as general manager of FORUS LAGERHOTELL AS.

Where is FORUS LAGERHOTELL AS based?

FORUS LAGERHOTELL AS has its business address in Bryne.

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.