BIZTRAC BETA
Rental and operating of own or leased real estate

GPO HOLDING AS

Org. no. 989206990 Limited company (AS) Øygarden Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 2.2m
Operating profit NOK 1.9m
Equity NOK 35.5m
Incorporated 2005
Share capital NOK 100,000

GPO HOLDING AS is registered as a limited company in Øygarden, Vestland with organisation number 989206990. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Selskapets formål er eierskap i andre selskaper og herunder bistå, organisere og delta i tiltak for drift av slike selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.2m in revenue and NOK 1.9m in operating profit.

Key figures · 2025

Revenue
NOK 2.2m
Operating profit
NOK 1.9m
Equity
NOK 35.5m
Est. value
NOK 29.4m

Financial health · 2025

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

Who owns GPO HOLDING AS?

GLENN PETER ONA
GPO HOLDING AS
NOK 2.2m rev. · NOK 1.9m profit

GPO HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does GPO HOLDING AS own?

GPO HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about GPO HOLDING AS

Who owns GPO HOLDING AS?

GLENN PETER ONA is the largest registered owner, with 100.0%.

What is the revenue of GPO HOLDING AS?

GPO HOLDING AS had revenue of NOK 2.2m in 2025.

Who is the general manager of GPO HOLDING AS?

Glenn Peter Ona is registered as general manager of GPO HOLDING AS.

Where is GPO HOLDING AS based?

GPO HOLDING AS has its business address in Kolltveit.

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.