BIZTRAC BETA
Rental and operating of own or leased real estate

ØRJESENTERET AS

Org. no. 957106420 Limited company (AS) Marker Incorporated 1989 Active
Ownership graph ↗
Revenue 2024 NOK 509,000
Operating profit NOK 206,000
Equity NOK −522,000
Incorporated 1989
Share capital NOK 197,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−522k kr).

ØRJESENTERET AS is registered as a limited company in Marker, Østfold with organisation number 957106420. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1989. Registered share capital is NOK 197,000, divided into 197 shares. The company's stated purpose is: “Utleie av egen eiendom med tilknyttet virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 509,000 in revenue and NOK 206,000 in operating profit.

Key figures · 2024

Revenue
NOK 509,000
Operating profit
NOK 206,000
Equity
NOK −522,000
Est. value
NOK 844,000

Financial health · 2025

Liquidity
3.94
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-17.1%
Weak
Equity as a share of total capital

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

Who owns ØRJESENTERET AS?

SIV RENATE FAGERÅS
ØRJESENTERET AS
NOK 509,000 rev. · NOK 206,000 profit

ØRJESENTERET AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ØRJESENTERET AS

Who owns ØRJESENTERET AS?

SIV RENATE FAGERÅS is the largest registered owner, with 79.7%.

What is the revenue of ØRJESENTERET AS?

ØRJESENTERET AS had revenue of NOK 509,000 in 2024.

Who is the general manager of ØRJESENTERET AS?

Siv Renate Fagerås is registered as general manager of ØRJESENTERET AS.

Where is ØRJESENTERET AS based?

ØRJESENTERET AS has its business address in Ørje.

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.