BIZTRAC BETA
Development of building projects

SINCLAIR EIENDOM AS

Org. no. 985806713 Limited company (AS) Vågå Incorporated 2003 Active
Ownership graph ↗
Revenue 2024 NOK 7.7m
Operating profit NOK 3.9m
Equity NOK 9.2m
Incorporated 2003
Share capital NOK 3.1m

SINCLAIR EIENDOM AS is registered as a limited company in Vågå, Innlandet with organisation number 985806713. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2003. Registered share capital is NOK 3.1m, divided into 3120 shares. The company's stated purpose is: “Eie, utleie og drift av fast eiendom og virksomhet forbundet med dette. Utvikling, oppføring og salg av fast eiendom. Salg av tjenester til andre selskaper. Ved aksjetegning eller på annen måte gjøre seg interessert i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 7.7m in revenue and NOK 3.9m in operating profit.

Key figures · 2024

Revenue
NOK 7.7m
Operating profit
NOK 3.9m
Equity
NOK 9.2m
Est. value
NOK 13.1m

Financial health · 2024

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

Who owns SINCLAIR EIENDOM AS?

SMED-EIENDOM AS
SINCLAIR EIENDOM AS
NOK 7.7m rev. · NOK 3.9m profit

SINCLAIR EIENDOM AS has 5 registered shareholders:

All shareholders and roles →

Which companies does SINCLAIR EIENDOM AS own?

SINCLAIR EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SINCLAIR EIENDOM AS

Who owns SINCLAIR EIENDOM AS?

SMED-EIENDOM AS is the largest registered owner, with 25.6%.

What is the revenue of SINCLAIR EIENDOM AS?

SINCLAIR EIENDOM AS had revenue of NOK 7.7m in 2024.

Where is SINCLAIR EIENDOM AS based?

SINCLAIR EIENDOM AS has its business address in Lalm.

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.