BIZTRAC BETA
COMPANY REGISTER PROFILE
988041912 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Hotels and similar accommodation

LIOSTUGU AS

Org. no. 988041912 Limited company (AS) Hemsedal Incorporated 2004 Active
Ownership graph ↗
Revenue 2025 NOK 1.1m
Operating profit NOK 116,000
Equity NOK 10.3m
Incorporated 2004
Share capital NOK 10.0m

LIOSTUGU AS is registered as a limited company in Hemsedal, Buskerud with organisation number 988041912. The business is classified under hotels and similar accommodation (NACE 55.100). The company was incorporated in 2004. Registered share capital is NOK 10.0m, divided into 100000 shares. The company's stated purpose is: “Utleie og utvikling av selskapets eiendom i samsvar med god forvaltning og eiernes interesser. Selskapet vil legge til rette for kristen og rusfri virksomhet. Målet er å inspirere og utruste unge mennesker til å kjenne Jesus og følge han.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.1m in revenue and NOK 116,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.1m
▲ +0 %
Operating profit
NOK 116,000
▲ +134 %
Equity
NOK 10.3m
▼ −0 %
Est. value
NOK 13.7m

Financial health · 2025

Liquidity
3.18
Very good
Current assets ÷ current liabilities
Profitability
1.1%
Weak
Return on total assets
Solidity
79.0%
Very good
Equity as a share of total capital

Who owns LIOSTUGU AS?

LIOSTUGU AS has 20+ registered shareholders:

All shareholders and roles →

Frequently asked questions about LIOSTUGU AS

Who owns LIOSTUGU AS?

OLA ARNFINN HARALDSET is the largest registered owner, with 29.4%.

What is the revenue of LIOSTUGU AS?

LIOSTUGU AS had revenue of NOK 1.1m in 2025.

Who is the general manager of LIOSTUGU AS?

Ola Arnfinn Haraldset is registered as general manager of LIOSTUGU AS.

Where is LIOSTUGU AS based?

LIOSTUGU AS has its business address in Hemsedal.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.