BIZTRAC BETA
Rental and operating of own or leased real estate

PECO EIENDOM AS

Org. no. 989225383 Limited company (AS) Tromsø Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −16,000
Equity NOK 1.0m
Incorporated 2005
Share capital NOK 100,000

Signals

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

PECO EIENDOM AS is registered as a limited company in Tromsø, Troms with organisation number 989225383. 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 100 shares. The company's stated purpose is: “Investering i aksjer og deltagelse i andre virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −16,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −16,000
Equity
NOK 1.0m
Est. value
NOK 935,000

Financial health · 2025

Liquidity
Not available
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
24.9%
Good
Equity as a share of total capital

Who owns PECO EIENDOM AS?

PER MARTIN SAUR
PECO EIENDOM AS
NOK 0 rev. · NOK −16,000 profit

PECO EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does PECO EIENDOM AS own?

PECO EIENDOM AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about PECO EIENDOM AS

Who owns PECO EIENDOM AS?

PER MARTIN SAUR is the largest registered owner, with 100.0%.

What is the revenue of PECO EIENDOM AS?

PECO EIENDOM AS had revenue of NOK 0 in 2025.

Who is the general manager of PECO EIENDOM AS?

Per Martin Saur is registered as general manager of PECO EIENDOM AS.

Where is PECO EIENDOM AS based?

PECO EIENDOM AS has its business address in Tromsø.

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.