BIZTRAC BETA
Rental and operating of own or leased real estate

LYNGBAKKEN AS

Org. no. 918917047 Limited company (AS) Haram Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 776,000
Operating profit NOK 269,000
Equity NOK 779,000
Incorporated 2017
Share capital NOK 350,000

LYNGBAKKEN AS is registered as a limited company in Haram, Møre og Romsdal with organisation number 918917047. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2017. Registered share capital is NOK 350,000, divided into 35 shares. The company's stated purpose is: “Drift av oppbevaringsplass og utleie av anleggsutstyr og hva hermed naturlig står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 776,000 in revenue and NOK 269,000 in operating profit.

Key figures · 2024

Revenue
NOK 776,000
Operating profit
NOK 269,000
Equity
NOK 779,000
Est. value
NOK 1.2m

Financial health · 2024

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

Who owns LYNGBAKKEN AS?

ROY PETTER NORMANN
LYNGBAKKEN AS
NOK 776,000 rev. · NOK 269,000 profit

LYNGBAKKEN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LYNGBAKKEN AS own?

LYNGBAKKEN AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about LYNGBAKKEN AS

Who owns LYNGBAKKEN AS?

ROY PETTER NORMANN is the largest registered owner, with 100.0%.

What is the revenue of LYNGBAKKEN AS?

LYNGBAKKEN AS had revenue of NOK 776,000 in 2024.

Who is the general manager of LYNGBAKKEN AS?

Roy Petter Normann is registered as general manager of LYNGBAKKEN AS.

Where is LYNGBAKKEN AS based?

LYNGBAKKEN AS has its business address in Hildre.

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.