BIZTRAC BETA
Rental and operating of own or leased real estate

OPSAHLVEIEN 3 AS

Org. no. 923536337 Limited company (AS) Indre Østfold Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 688,000
Operating profit NOK 346,000
Equity NOK 524,000
Incorporated 2019
Share capital NOK 100,000

OPSAHLVEIEN 3 AS is registered as a limited company in Indre Østfold, Østfold with organisation number 923536337. 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 100,000, divided into 1 shares. The company's stated purpose is: “Selv, gjennom hel- eller deleide selskaper eller ved samarbeid med andre virksomheter å forestå investeringsvirksomhet, eiendomsforvaltning, forretningsførsel og annen virksomhet beslektet med denne.”. The most recent filed accounts, for the 2025 financial year, show NOK 688,000 in revenue and NOK 346,000 in operating profit.

Key figures · 2025

Revenue
NOK 688,000
Operating profit
NOK 346,000
Equity
NOK 524,000
Est. value
NOK 1.2m

Financial health · 2025

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

Who owns OPSAHLVEIEN 3 AS?

MYSEN EIENDOMSUTVIKLING HOLDING AS
OPSAHLVEIEN 3 AS
NOK 688,000 rev. · NOK 346,000 profit

OPSAHLVEIEN 3 AS has 1 registered shareholder:

All shareholders and roles →

Group structure

OPSAHLVEIEN 3 AS er morselskap for 3 datterselskaper:

Frequently asked questions about OPSAHLVEIEN 3 AS

Who owns OPSAHLVEIEN 3 AS?

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

What is the revenue of OPSAHLVEIEN 3 AS?

OPSAHLVEIEN 3 AS had revenue of NOK 688,000 in 2025.

Where is OPSAHLVEIEN 3 AS based?

OPSAHLVEIEN 3 AS has its business address in Mysen.

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.