BIZTRAC BETA
Rental and operating of own or leased real estate

GJ EIENDOM AS

Org. no. 997717759 Limited company (AS) Tvedestrand Incorporated 2011 Active
Ownership graph ↗
Revenue 2024 NOK 750,000
Operating profit NOK 309,000
Equity NOK 6.9m
Incorporated 2011
Share capital NOK 123,000

GJ EIENDOM AS is registered as a limited company in Tvedestrand, Agder with organisation number 997717759. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2011. Registered share capital is NOK 123,000, divided into 123320 shares. The company's stated purpose is: “Eiendomsdrift og alt som naturlig hører sammen med dette, samt investering i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 750,000 in revenue and NOK 309,000 in operating profit.

Key figures · 2024

Revenue
NOK 750,000
Operating profit
NOK 309,000
Equity
NOK 6.9m
Est. value
NOK 5.3m

Financial health · 2024

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

Who owns GJ EIENDOM AS?

EINERSVIKA UTVIKLING AS
GJ EIENDOM AS
NOK 750,000 rev. · NOK 309,000 profit

GJ EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does GJ EIENDOM AS own?

GJ EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about GJ EIENDOM AS

Who owns GJ EIENDOM AS?

EINERSVIKA UTVIKLING AS is the largest registered owner, with 100.0%.

What is the revenue of GJ EIENDOM AS?

GJ EIENDOM AS had revenue of NOK 750,000 in 2024.

Who is the general manager of GJ EIENDOM AS?

Jan Marcussen is registered as general manager of GJ EIENDOM AS.

Where is GJ EIENDOM AS based?

GJ EIENDOM AS has its business address in Gjeving.

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.