BIZTRAC BETA
COMPANY REGISTER PROFILE
997104196 ORG. NO. 2024 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Development of building projects

LJONESVÅGEN HYTTEGREND AS

Org. no. 997104196 Limited company (AS) Kvam Incorporated 2011 Active
Ownership graph ↗
Revenue 2024 NOK 179,000
Operating profit NOK 54,000
Equity NOK 1.2m
Incorporated 2011
Share capital NOK 100,000

LJONESVÅGEN HYTTEGREND AS is registered as a limited company in Kvam, Vestland with organisation number 997104196. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2011. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Utvikling og sal av tomter til fritidsbustader.”. The most recent filed accounts, for the 2024 financial year, show NOK 179,000 in revenue and NOK 54,000 in operating profit.

Key figures · 2024

Revenue
NOK 179,000
Operating profit
NOK 54,000
Equity
NOK 1.2m
Est. value
NOK 1.1m

Financial health · 2024

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

Who owns LJONESVÅGEN HYTTEGREND AS?

ASBJØRN LJONES
LJONESVÅGEN HYTTEGREND AS
NOK 179,000 rev. · NOK 54,000 profit

LJONESVÅGEN HYTTEGREND AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LJONESVÅGEN HYTTEGREND AS

Who owns LJONESVÅGEN HYTTEGREND AS?

ASBJØRN LJONES is the largest registered owner, with 100.0%.

What is the revenue of LJONESVÅGEN HYTTEGREND AS?

LJONESVÅGEN HYTTEGREND AS had revenue of NOK 179,000 in 2024.

Who is the general manager of LJONESVÅGEN HYTTEGREND AS?

Asbjørn Ljones is registered as general manager of LJONESVÅGEN HYTTEGREND AS.

Where is LJONESVÅGEN HYTTEGREND AS based?

LJONESVÅGEN HYTTEGREND AS has its business address in Tørvikbygd.

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.