BIZTRAC BETA
Electrical installation

PSO EIGEDOM AS

Org. no. 847520272 Limited company (AS) Gloppen Incorporated 1987 Active
Ownership graph ↗
Revenue 2025 NOK 323,000
Operating profit NOK −42,000
Equity NOK 3.0m
Incorporated 1987
Share capital NOK 130,000

Signals

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

PSO EIGEDOM AS is registered as a limited company in Gloppen, Vestland with organisation number 847520272. The business is classified under electrical installation (NACE 43.210). The company was incorporated in 1987. Registered share capital is NOK 130,000, divided into 100 shares. The company's stated purpose is: “Investering i, eie og forvalte fast eiendom, samt alt som naturlig hører inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 323,000 in revenue and NOK −42,000 in operating profit.

Key figures · 2025

Revenue
NOK 323,000
Operating profit
NOK −42,000
Equity
NOK 3.0m
Est. value
NOK 2.3m

Financial health · 2025

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

Who owns PSO EIGEDOM AS?

OLAV LOTE
PSO EIGEDOM AS
NOK 323,000 rev. · NOK −42,000 profit

PSO EIGEDOM AS has 2 registered shareholders:

All shareholders and roles →

Which companies does PSO EIGEDOM AS own?

PSO EIGEDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about PSO EIGEDOM AS

Who owns PSO EIGEDOM AS?

OLAV LOTE is the largest registered owner, with 70.0%.

What is the revenue of PSO EIGEDOM AS?

PSO EIGEDOM AS had revenue of NOK 323,000 in 2025.

Who is the general manager of PSO EIGEDOM AS?

Olav Lote is registered as general manager of PSO EIGEDOM AS.

Where is PSO EIGEDOM AS based?

PSO EIGEDOM AS has its business address in Sandane.

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.