BIZTRAC BETA
Rental and operating of own or leased real estate

GR EIENDOM ØSTERHUS AS

Org. no. 911818779 Limited company (AS) Grimstad Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 960,000
Operating profit NOK 311,000
Equity NOK 2.9m
Incorporated 2013
Share capital NOK 1.0m

GR EIENDOM ØSTERHUS AS is registered as a limited company in Grimstad, Agder with organisation number 911818779. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2013. Registered share capital is NOK 1.0m, divided into 1000 shares. The company's stated purpose is: “Kjøp, utleie og drift av fast eienom og annet som naturlig hører sammen med dette, herunder å delta i andre selskap med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 960,000 in revenue and NOK 311,000 in operating profit.

Key figures · 2024

Revenue
NOK 960,000
Operating profit
NOK 311,000
Equity
NOK 2.9m
Est. value
NOK 2.5m

Financial health · 2024

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

Who owns GR EIENDOM ØSTERHUS AS?

EVENCO HOLDING AS
GR EIENDOM ØSTERHUS AS
NOK 960,000 rev. · NOK 311,000 profit

GR EIENDOM ØSTERHUS AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about GR EIENDOM ØSTERHUS AS

Who owns GR EIENDOM ØSTERHUS AS?

EVENCO HOLDING AS is the largest registered owner, with 50.0%.

What is the revenue of GR EIENDOM ØSTERHUS AS?

GR EIENDOM ØSTERHUS AS had revenue of NOK 960,000 in 2024.

Who is the general manager of GR EIENDOM ØSTERHUS AS?

Magnus Evenstad is registered as general manager of GR EIENDOM ØSTERHUS AS.

Where is GR EIENDOM ØSTERHUS AS based?

GR EIENDOM ØSTERHUS AS has its business address in Grimstad.

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.