BIZTRAC BETA
Development of building projects

OREPA AS

Org. no. 913229746 Limited company (AS) Bærum Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 329,000
Operating profit NOK −805,000
Equity NOK 59.3m
Incorporated 2014
Share capital NOK 30.7m

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−805k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

OREPA AS is registered as a limited company in Bærum, Akershus with organisation number 913229746. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2014. Registered share capital is NOK 30.7m, divided into 30748571 shares. The company's stated purpose is: “Eie, utvikle og investere i fast eiendom, samt det som står i naturlig forbindelse med dette, herunder drift og utleie av fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 329,000 in revenue and NOK −805,000 in operating profit.

Key figures · 2025

Revenue
NOK 329,000
Operating profit
NOK −805,000
Equity
NOK 59.3m
Est. value
NOK 41.1m

Financial health · 2025

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

Who owns OREPA AS?

ORECO AS
OREPA AS
NOK 329,000 rev. · NOK −805,000 profit

OREPA AS has 15 registered shareholders:

All shareholders and roles →

Which companies does OREPA AS own?

OREPA AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about OREPA AS

Who owns OREPA AS?

ORECO AS is the largest registered owner, with 15.3%.

What is the revenue of OREPA AS?

OREPA AS had revenue of NOK 329,000 in 2025.

Where is OREPA AS based?

OREPA AS has its business address in Bekkestua.

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.