BIZTRAC BETA
COMPANY REGISTER PROFILE
925109223 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Development of building projects

PPA EIENDOM AS

Org. no. 925109223 Limited company (AS) Ringsaker Incorporated 2020 Active
Ownership graph ↗
Operating profit NOK −127,000
Equity NOK −5.4m
Incorporated 2020
Share capital NOK 35,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−5,4 mill kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−127k kr).

PPA EIENDOM AS is registered as a limited company in Ringsaker, Innlandet with organisation number 925109223. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2020. Registered share capital is NOK 35,000, divided into 354 shares. The company's stated purpose is: “Investering i, og forvaltning, prosjektering og utvikling av fast eiendom, herunder deltagelse i andre selskaper og alt som står i forbindelse med det.”.

Former names: HERKULES INVEST 331 AS

Key figures · 2025

Operating profit
NOK −127,000
▲ +90 %
Equity
NOK −5.4m
▲ +41 %

Financial health · 2025

Liquidity
3.07
Very good
Current assets ÷ current liabilities
Profitability
0.1%
Not satisfactory
Return on total assets
Solidity
-8.1%
Weak
Equity as a share of total capital

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

Who owns PPA EIENDOM AS?

PPA EIENDOM AS has 3 registered shareholders:

All shareholders and roles →

Which companies does PPA EIENDOM AS own?

PPA EIENDOM AS holds stakes in 13 companies:

See the full ownership structure →

Group structure

PPA EIENDOM AS er morselskap for 7 datterselskaper:

Frequently asked questions about PPA EIENDOM AS

Who owns PPA EIENDOM AS?

TYREN HOLDING AS is the largest registered owner, with 46.6%.

Where is PPA EIENDOM AS based?

PPA EIENDOM AS has its business address in Brumunddal.

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

Report a problem

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