BIZTRAC BETA
Rental and operating of own or leased real estate

LIGO EIENDOM AS

Org. no. 965324887 Limited company (AS) Sandnes Incorporated 1992 Active
Ownership graph ↗
Revenue 2024 NOK 918,000
Operating profit NOK 369,000
Equity NOK 18.2m
Incorporated 1992
Share capital NOK 5.4m

LIGO EIENDOM AS is registered as a limited company in Sandnes, Rogaland with organisation number 965324887. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1992. Registered share capital is NOK 5.4m, divided into 1080 shares. The company's stated purpose is: “Å eie eiendommer, drive utleie, samt hva hermed står i forbindelse, og i tillegg delta/ investere i andre selskaper med lignende eller annen virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 918,000 in revenue and NOK 369,000 in operating profit.

Key figures · 2024

Revenue
NOK 918,000
Operating profit
NOK 369,000
Equity
NOK 18.2m
Est. value
NOK 13.2m

Financial health · 2024

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

Who owns LIGO EIENDOM AS?

JELSACO AS
LIGO EIENDOM AS
NOK 918,000 rev. · NOK 369,000 profit

LIGO EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LIGO EIENDOM AS own?

LIGO EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Group structure

LIGO EIENDOM AS er morselskap for 1 datterselskap:

Frequently asked questions about LIGO EIENDOM AS

Who owns LIGO EIENDOM AS?

JELSACO AS is the largest registered owner, with 100.0%.

What is the revenue of LIGO EIENDOM AS?

LIGO EIENDOM AS had revenue of NOK 918,000 in 2024.

Where is LIGO EIENDOM AS based?

LIGO EIENDOM AS has its business address in Sandnes.

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.