BIZTRAC BETA
Retail sale of clothing

IDLAND 1869 AS

Org. no. 994501666 Limited company (AS) Sandnes Incorporated 2009 Active
Ownership graph ↗
Revenue 2025 NOK 12.7m
Operating profit NOK 2.2m
Equity NOK 4.4m
Incorporated 2009
Employees 8
Share capital NOK 500,000

IDLAND 1869 AS is registered as a limited company in Sandnes, Rogaland with organisation number 994501666. The business is classified under retail sale of clothing (NACE 47.710). The company was incorporated in 2009 and has 8 registered employees. Registered share capital is NOK 500,000, divided into 500 shares. The company's stated purpose is: “Butikkdrift med salg av klær, samt hva hermed står i forbindelse, herunder å delta i andre selskap med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 12.7m in revenue and NOK 2.2m in operating profit.

Key figures · 2025

Revenue
NOK 12.7m
Operating profit
NOK 2.2m
Equity
NOK 4.4m
Est. value
NOK 9.6m

Financial health · 2025

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

Who owns IDLAND 1869 AS?

EIDSVOLL EIENDOM AS
IDLAND 1869 AS
NOK 12.7m rev. · NOK 2.2m profit

IDLAND 1869 AS has 2 registered shareholders:

All shareholders and roles →

Which companies does IDLAND 1869 AS own?

IDLAND 1869 AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about IDLAND 1869 AS

Who owns IDLAND 1869 AS?

EIDSVOLL EIENDOM AS is the largest registered owner, with 60.0%.

What is the revenue of IDLAND 1869 AS?

IDLAND 1869 AS had revenue of NOK 12.7m in 2025.

Who is the general manager of IDLAND 1869 AS?

Reidun Sæland Bøe is registered as general manager of IDLAND 1869 AS.

Where is IDLAND 1869 AS based?

IDLAND 1869 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.