BIZTRAC BETA
Rental and operating of own or leased real estate

P G EIENDOM AS

Org. no. 989933647 Limited company (AS) Gjerstad Incorporated 2006 Active
Ownership graph ↗
Revenue 2025 NOK 481,000
Operating profit NOK 224,000
Equity NOK −22,000
Incorporated 2006
Share capital NOK 100,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−22k kr).

P G EIENDOM AS is registered as a limited company in Gjerstad, Agder with organisation number 989933647. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2006. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Å eie og leie ut fast eiendom, samt investere og delta i andre virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 481,000 in revenue and NOK 224,000 in operating profit.

Key figures · 2025

Revenue
NOK 481,000
Operating profit
NOK 224,000
Equity
NOK −22,000
Est. value
NOK 1.7m

Financial health · 2025

Liquidity
0.46
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-1.0%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns P G EIENDOM AS?

PER GUNVALD HAUGEN
P G EIENDOM AS
NOK 481,000 rev. · NOK 224,000 profit

P G EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about P G EIENDOM AS

Who owns P G EIENDOM AS?

PER GUNVALD HAUGEN is the largest registered owner, with 50.0%.

What is the revenue of P G EIENDOM AS?

P G EIENDOM AS had revenue of NOK 481,000 in 2025.

Who is the general manager of P G EIENDOM AS?

Per Gunvald Haugen is registered as general manager of P G EIENDOM AS.

Where is P G EIENDOM AS based?

P G EIENDOM AS has its business address in Sundebru.

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.