BIZTRAC BETA
Rental and operating of own or leased real estate

LIDAR HOLDING AS

Org. no. 914092132 Limited company (AS) Inderøy Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −30,000
Equity NOK 2.3m
Incorporated 2014
Share capital NOK 500,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−30k kr).

LIDAR HOLDING AS is registered as a limited company in Inderøy, Trøndelag with organisation number 914092132. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2014. Registered share capital is NOK 500,000, divided into 500 shares. The company's stated purpose is: “Eie, utvikle, drive eiendommer og annet som naturlig kan ha tilhørighet til dette. Herunder delta i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −30,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −30,000
Equity
NOK 2.3m
Est. value
NOK 2.1m

Financial health · 2024

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

Who owns LIDAR HOLDING AS?

KJELL GRAN
LIDAR HOLDING AS
NOK 0 rev. · NOK −30,000 profit

LIDAR HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does LIDAR HOLDING AS own?

LIDAR HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about LIDAR HOLDING AS

Who owns LIDAR HOLDING AS?

KJELL GRAN is the largest registered owner, with 80.0%.

What is the revenue of LIDAR HOLDING AS?

LIDAR HOLDING AS had revenue of NOK 0 in 2024.

Where is LIDAR HOLDING AS based?

LIDAR HOLDING AS has its business address in Inderøy.

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.