BIZTRAC BETA
Rental and operating of own or leased real estate

GA EIENDOM AS

Org. no. 824710902 Limited company (AS) Drammen Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −22,000
Equity NOK 2.2m
Incorporated 2020
Share capital NOK 2.5m

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−22k kr).

GA EIENDOM AS is registered as a limited company in Drammen, Buskerud with organisation number 824710902. 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 2.5m, divided into 2500 shares. The company's stated purpose is: “Eie aksjer, eie og forvalte eiendom og leie ut eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −22,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −22,000
Equity
NOK 2.2m
Est. value
NOK 2.8m

Financial health · 2025

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

Who owns GA EIENDOM AS?

JOSTEIN FOLKEDAL HOLDING AS
GA EIENDOM AS
NOK 0 rev. · NOK −22,000 profit

GA EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Which companies does GA EIENDOM AS own?

GA EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about GA EIENDOM AS

Who owns GA EIENDOM AS?

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

What is the revenue of GA EIENDOM AS?

GA EIENDOM AS had revenue of NOK 0 in 2025.

Who is the general manager of GA EIENDOM AS?

Øyvind Nilsen is registered as general manager of GA EIENDOM AS.

Where is GA EIENDOM AS based?

GA EIENDOM AS has its business address in Solbergelva.

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.