BIZTRAC BETA
Hotels and similar accommodation

LAMPELAND HOTELL AS

Org. no. 994263862 Limited company (AS) Flesberg Incorporated 2009 Active
Ownership graph ↗
Revenue 2024 NOK 40.1m
Operating profit NOK 1.5m
Equity NOK 13.8m
Incorporated 2009
Employees 68
Share capital NOK 510,000

LAMPELAND HOTELL AS is registered as a limited company in Flesberg, Buskerud with organisation number 994263862. The business is classified under hotels and similar accommodation (NACE 55.100). The company was incorporated in 2009 and has 68 registered employees. Registered share capital is NOK 510,000, divided into 510000 shares. The company's stated purpose is: “Hotellvirksomhet, drift av restaurant og kafe, dessuten kjøp, salg, drift av fast eiendom, samt ved kjøp av aksjer eller på annen måte delta i andre virksomheter.”. The most recent filed accounts, for the 2024 financial year, show NOK 40.1m in revenue and NOK 1.5m in operating profit.

Key figures · 2024

Revenue
NOK 40.1m
Operating profit
NOK 1.5m
Equity
NOK 13.8m
Est. value
NOK 14.5m

Financial health · 2024

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

Who owns LAMPELAND HOTELL AS?

ASTRID TVEITEN
LAMPELAND HOTELL AS
NOK 40.1m rev. · NOK 1.5m profit

LAMPELAND HOTELL AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about LAMPELAND HOTELL AS

Who owns LAMPELAND HOTELL AS?

ASTRID TVEITEN is the largest registered owner, with 33.3%.

What is the revenue of LAMPELAND HOTELL AS?

LAMPELAND HOTELL AS had revenue of NOK 40.1m in 2024.

Who is the general manager of LAMPELAND HOTELL AS?

Kari Tveiten is registered as general manager of LAMPELAND HOTELL AS.

Where is LAMPELAND HOTELL AS based?

LAMPELAND HOTELL AS has its business address in Lampeland.

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.