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

PROGIT EIENDOM AS

Org. no. 923749500 Limited company (AS) Oslo Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 554,000
Operating profit NOK 178,000
Equity NOK 4.9m
Incorporated 2019
Share capital NOK 4.9m

PROGIT EIENDOM AS is registered as a limited company in Oslo, Oslo with organisation number 923749500. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2019. Registered share capital is NOK 4.9m, divided into 30000 shares. The company's stated purpose is: “Kjøp, salg, utleie og utvikling av fast eiendom, samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 554,000 in revenue and NOK 178,000 in operating profit.

Key figures · 2025

Revenue
NOK 554,000
▲ +24 %
Operating profit
NOK 178,000
▲ +151 %
Equity
NOK 4.9m
▼ −1 %
Est. value
NOK 3.6m

Financial health · 2025

Liquidity
0.26
Not satisfactory
Current assets ÷ current liabilities
Profitability
1.6%
Weak
Return on total assets
Solidity
44.8%
Very good
Equity as a share of total capital

Who owns PROGIT EIENDOM AS?

PROGIT EIENDOM AS
NOK 554,000 rev. · NOK 178,000 profit

PROGIT EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PROGIT EIENDOM AS

Who owns PROGIT EIENDOM AS?

PROGIT HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of PROGIT EIENDOM AS?

PROGIT EIENDOM AS had revenue of NOK 554,000 in 2025.

Who is the general manager of PROGIT EIENDOM AS?

Patrick Stormo Hjerpseth is registered as general manager of PROGIT EIENDOM AS.

Where is PROGIT EIENDOM AS based?

PROGIT EIENDOM 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.