BIZTRAC BETA
Rental and operating of own or leased real estate

GARCON EIENDOM AS

Org. no. 923834303 Limited company (AS) Lillestrøm Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 1.3m
Operating profit NOK 756,000
Equity NOK −1.4m
Incorporated 2019
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−1,4 mill kr).

GARCON EIENDOM AS is registered as a limited company in Lillestrøm, Akershus with organisation number 923834303. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Kjøp, salg og utleie av eiendom i egen regi samt utvikling av tomter og eiendommer for bolig og næring samt deltagelse i virksomheter med tilsvarende formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.3m in revenue and NOK 756,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.3m
Operating profit
NOK 756,000
Equity
NOK −1.4m
Est. value
NOK 5.8m

Financial health · 2025

Liquidity
3.06
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-15.4%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns GARCON EIENDOM AS?

GARCON HOLDING AS
GARCON EIENDOM AS
NOK 1.3m rev. · NOK 756,000 profit

GARCON EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GARCON EIENDOM AS

Who owns GARCON EIENDOM AS?

GARCON HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of GARCON EIENDOM AS?

GARCON EIENDOM AS had revenue of NOK 1.3m in 2025.

Where is GARCON EIENDOM AS based?

GARCON EIENDOM AS has its business address in Lillestrøm.

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.