BIZTRAC BETA
Rental and operating of own or leased real estate

RESTAURANTHUSET EIENDOM AS

Org. no. 931925792 Limited company (AS) Larvik Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 2.1m
Operating profit NOK −152,000
Equity NOK 10.3m
Incorporated 2023
Share capital NOK 120,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−152k kr).

RESTAURANTHUSET EIENDOM AS is registered as a limited company in Larvik, Vestfold with organisation number 931925792. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2023. Registered share capital is NOK 120,000, divided into 30000 shares. The company's stated purpose is: “Kjøp, salg, utleie og utvikling av eiendom samt investeringer i andre selskap og annet som naturlig faller innunder dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.1m in revenue and NOK −152,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.1m
Operating profit
NOK −152,000
Equity
NOK 10.3m
Est. value
NOK 9.4m

Financial health · 2025

Liquidity
2.40
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
23.6%
Good
Equity as a share of total capital

Who owns RESTAURANTHUSET EIENDOM AS?

RESTAURANTHUSET HOLDING AS
RESTAURANTHUSET EIENDOM AS
NOK 2.1m rev. · NOK −152,000 profit

RESTAURANTHUSET EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RESTAURANTHUSET EIENDOM AS

Who owns RESTAURANTHUSET EIENDOM AS?

RESTAURANTHUSET HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of RESTAURANTHUSET EIENDOM AS?

RESTAURANTHUSET EIENDOM AS had revenue of NOK 2.1m in 2024.

Where is RESTAURANTHUSET EIENDOM AS based?

RESTAURANTHUSET EIENDOM AS has its business address in Larvik.

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.