BIZTRAC BETA
Rental and operating of own or leased real estate

PG EIENDOM AS

Org. no. 998886465 Limited company (AS) Klepp Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 2.3m
Operating profit NOK 1.9m
Equity NOK 2.7m
Incorporated 2012
Share capital NOK 100,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

PG EIENDOM AS is registered as a limited company in Klepp, Rogaland with organisation number 998886465. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2012. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Kjøp, salg, drift, utleie og drift av fast eigedom og hva hermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.3m in revenue and NOK 1.9m in operating profit.

Key figures · 2024

Revenue
NOK 2.3m
Operating profit
NOK 1.9m
Equity
NOK 2.7m
Est. value
NOK 5.0m

Financial health · 2024

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

Who owns PG EIENDOM AS?

GRUDE & KLINGSHEIM EIENDOM AS
PG EIENDOM AS
NOK 2.3m rev. · NOK 1.9m profit

PG EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PG EIENDOM AS

Who owns PG EIENDOM AS?

GRUDE & KLINGSHEIM EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of PG EIENDOM AS?

PG EIENDOM AS had revenue of NOK 2.3m in 2024.

Who is the general manager of PG EIENDOM AS?

Per Klingsheim is registered as general manager of PG EIENDOM AS.

Where is PG EIENDOM AS based?

PG EIENDOM AS has its business address in Klepp Stasjon.

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.