BIZTRAC BETA
Temporary employment agency activities and other human resource provisions

PRÅ EIENDOM AS

Org. no. 992779209 Limited company (AS) Kragerø Incorporated 2008 Active
Ownership graph ↗
Revenue 2025 NOK 280,000
Operating profit NOK −834,000
Equity NOK 103,000
Incorporated 2008
Share capital NOK 30,000

Signals

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

PRÅ EIENDOM AS is registered as a limited company in Kragerø, Telemark with organisation number 992779209. The business is classified under temporary employment agency activities and other human resource provisions (NACE 78.200). The company was incorporated in 2008. Registered share capital is NOK 30,000, divided into 400 shares. The company's stated purpose is: “Investere i finans- og realobjekter samt å drive med utleie av arbeidskraft.”. The most recent filed accounts, for the 2025 financial year, show NOK 280,000 in revenue and NOK −834,000 in operating profit.

Key figures · 2025

Revenue
NOK 280,000
Operating profit
NOK −834,000
Equity
NOK 103,000
Est. value
NOK 148,000

Financial health · 2025

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

Who owns PRÅ EIENDOM AS?

PE - HOLDING AS
PRÅ EIENDOM AS
NOK 280,000 rev. · NOK −834,000 profit

PRÅ EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PRÅ EIENDOM AS

Who owns PRÅ EIENDOM AS?

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

What is the revenue of PRÅ EIENDOM AS?

PRÅ EIENDOM AS had revenue of NOK 280,000 in 2025.

Who is the general manager of PRÅ EIENDOM AS?

Pål Brekka is registered as general manager of PRÅ EIENDOM AS.

Where is PRÅ EIENDOM AS based?

PRÅ EIENDOM AS has its business address in Kragerø.

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.