BIZTRAC BETA
Rental and operating of own or leased real estate

GJESTEGÅRDEN SELSKAPSLOKALER AS

Org. no. 926045296 Limited company (AS) Aurskog-Høland Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 860,000
Operating profit NOK 369,000
Equity NOK 130,000
Incorporated 2020
Share capital NOK 30,000

GJESTEGÅRDEN SELSKAPSLOKALER AS is registered as a limited company in Aurskog-Høland, Akershus with organisation number 926045296. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Utleie av egen og leid fast eiendom samt drift av selskapslokaler, matservering og gatekjøkken.”. The most recent filed accounts, for the 2025 financial year, show NOK 860,000 in revenue and NOK 369,000 in operating profit.

Key figures · 2025

Revenue
NOK 860,000
Operating profit
NOK 369,000
Equity
NOK 130,000
Est. value
NOK 721,000

Financial health · 2025

Liquidity
0.05
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
2.2%
Not satisfactory
Equity as a share of total capital

Who owns GJESTEGÅRDEN SELSKAPSLOKALER AS?

QASIM OMARI OMARGOL OMARI
GJESTEGÅRDEN SELSKAPSLOKALER AS
NOK 860,000 rev. · NOK 369,000 profit

GJESTEGÅRDEN SELSKAPSLOKALER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GJESTEGÅRDEN SELSKAPSLOKALER AS

Who owns GJESTEGÅRDEN SELSKAPSLOKALER AS?

QASIM OMARI OMARGOL OMARI is the largest registered owner, with 100.0%.

What is the revenue of GJESTEGÅRDEN SELSKAPSLOKALER AS?

GJESTEGÅRDEN SELSKAPSLOKALER AS had revenue of NOK 860,000 in 2025.

Where is GJESTEGÅRDEN SELSKAPSLOKALER AS based?

GJESTEGÅRDEN SELSKAPSLOKALER AS has its business address in Aurskog.

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.