BIZTRAC BETA
Rental and operating of own or leased real estate

OPES SARPSBORG AS

Org. no. 817725392 Limited company (AS) Fredrikstad Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 1,000
Operating profit NOK −412,000
Equity NOK 313,000
Incorporated 2016
Share capital NOK 61,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−412k kr).

OPES SARPSBORG AS is registered as a limited company in Fredrikstad, Østfold with organisation number 817725392. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2016. Registered share capital is NOK 61,000, divided into 61000 shares. The company's stated purpose is: “Eie og drive faste eiendommer og verdipapirer samt delta i andre virksomheter.”. The most recent filed accounts, for the 2024 financial year, show NOK 1,000 in revenue and NOK −412,000 in operating profit.

Key figures · 2024

Revenue
NOK 1,000
Operating profit
NOK −412,000
Equity
NOK 313,000
Est. value
NOK 286,000

Financial health · 2024

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

Who owns OPES SARPSBORG AS?

FREDRIKSTAD REGNSKAP AS
OPES SARPSBORG AS
NOK 1,000 rev. · NOK −412,000 profit

OPES SARPSBORG AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about OPES SARPSBORG AS

Who owns OPES SARPSBORG AS?

FREDRIKSTAD REGNSKAP AS is the largest registered owner, with 50.0%.

What is the revenue of OPES SARPSBORG AS?

OPES SARPSBORG AS had revenue of NOK 1,000 in 2024.

Who is the general manager of OPES SARPSBORG AS?

Trond Roger Flatøy is registered as general manager of OPES SARPSBORG AS.

Where is OPES SARPSBORG AS based?

OPES SARPSBORG AS has its business address in Engelsviken.

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.