biztrac. BETA
COMPANY REGISTER PROFILE
929151763 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

PECUNIA EIENDOMSPARTNER AS

Org. no. 929151763 Limited company (AS) Oslo Incorporated 2022 Active
Ownership graph ↗
Operating profit NOK −459,000
Equity NOK 83.8m
Incorporated 2022
Share capital NOK 30,000

Signals

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

PECUNIA EIENDOMSPARTNER AS is registered as a limited company in Oslo, Oslo with organisation number 929151763. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Eiendomsutvikling, eiendomsforvaltning og investeringsvirksomhet i egne regi eller gjennom deltagelse i andre selskaper samt annen virksomhet i tilknytning til dette.”.

Former names: TREKK 2205 AS

Key figures · 2025

Operating profit
NOK −459,000
▼ −111 %
Equity
NOK 83.8m
▲ +2763 %
Est. value
NOK 76.4m

Financial health · 2025

Liquidity
0.58
Weak
Current assets ÷ current liabilities
Profitability
1.5%
Weak
Return on total assets
Solidity
35.0%
Good
Equity as a share of total capital

Who owns PECUNIA EIENDOMSPARTNER AS?

PECUNIA EIENDOMSPARTNER AS
· NOK −459,000 profit

PECUNIA EIENDOMSPARTNER AS has 1 registered shareholder:

All shareholders and roles →

Which companies does PECUNIA EIENDOMSPARTNER AS own?

PECUNIA EIENDOMSPARTNER AS holds stakes in 8 companies:

See the full ownership structure →

Frequently asked questions about PECUNIA EIENDOMSPARTNER AS

Who owns PECUNIA EIENDOMSPARTNER AS?

PECUNIA EIENDOM AS is the largest registered owner, with 100.0%.

Where is PECUNIA EIENDOMSPARTNER AS based?

PECUNIA EIENDOMSPARTNER AS has its business address in Oslo.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.