biztrac. BETA
COMPANY REGISTER PROFILE
998239524 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Construction of residential and non-residential buildings

LEVE HYTTER AS

Org. no. 998239524 Limited company (AS) Øyer Incorporated 2012 Active
Revenue 2025 NOK 71.7m
Operating profit NOK 2.8m
Equity NOK 23.1m
Incorporated 2012
Share capital NOK 500,000

LEVE HYTTER AS is registered as a limited company in Øyer, Innlandet with organisation number 998239524. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2012. Registered share capital is NOK 500,000, divided into 500 shares. The company's stated purpose is: “Oppføring av hytter. Selskapet kan også ved aksjetegning eller på annen måte gjøre seg interessert i andre foretagende, samt kjøpe, eie og selge fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 71.7m in revenue and NOK 2.8m in operating profit.

Key figures · 2025

Revenue
NOK 71.7m
▲ +38 %
Operating profit
NOK 2.8m
▲ +391 %
Equity
NOK 23.1m
▲ +2 %
Est. value
NOK 21.0m

Financial health · 2025

Liquidity
1.59
Good
Current assets ÷ current liabilities
Profitability
4.5%
Weak
Return on total assets
Solidity
40.8%
Very good
Equity as a share of total capital

Who owns LEVE HYTTER AS?

LEVE HYTTER AS
NOK 71.7m rev. · NOK 2.8m profit

LEVE HYTTER AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LEVE HYTTER AS own?

LEVE HYTTER AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about LEVE HYTTER AS

Who owns LEVE HYTTER AS?

FAUN GRUPPEN AS is the largest registered owner, with 100.0%.

What is the revenue of LEVE HYTTER AS?

LEVE HYTTER AS had revenue of NOK 71.7m in 2025.

Where is LEVE HYTTER AS based?

LEVE HYTTER AS has its business address in Øyer.

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

Report a problem

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