BIZTRAC BETA
Rental and operating of own or leased real estate

GPA EIENDOM AS

Org. no. 997102940 Limited company (AS) Gol Incorporated 2011 Active
Ownership graph ↗
Revenue 2025 NOK 723,000
Operating profit NOK 511,000
Equity NOK 5.3m
Incorporated 2011
Share capital NOK 175,000

GPA EIENDOM AS is registered as a limited company in Gol, Buskerud with organisation number 997102940. 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 175,000, divided into 100 shares. The company's stated purpose is: “Kjøp, utleie og salg av fast eiendom samt naturlig tilhørende virksomhet, herunder investeringer i andre virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 723,000 in revenue and NOK 511,000 in operating profit.

Key figures · 2025

Revenue
NOK 723,000
Operating profit
NOK 511,000
Equity
NOK 5.3m
Est. value
NOK 5.0m

Financial health · 2025

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

Who owns GPA EIENDOM AS?

PER ANDERS BRØTO
GPA EIENDOM AS
NOK 723,000 rev. · NOK 511,000 profit

GPA EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Which companies does GPA EIENDOM AS own?

GPA EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about GPA EIENDOM AS

Who owns GPA EIENDOM AS?

PER ANDERS BRØTO is the largest registered owner, with 50.0%.

What is the revenue of GPA EIENDOM AS?

GPA EIENDOM AS had revenue of NOK 723,000 in 2025.

Who is the general manager of GPA EIENDOM AS?

Geir Brøto is registered as general manager of GPA EIENDOM AS.

Where is GPA EIENDOM AS based?

GPA EIENDOM AS has its business address in Gol.

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.