BIZTRAC BETA
COMPANY REGISTER PROFILE
925638242 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Other real estate activities on a fee or contract basis

YSTRØM EIENDOM AS

Org. no. 925638242 Limited company (AS) Halden Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −6,000
Equity NOK 1.1m
Incorporated 2020
Share capital NOK 30,000

Signals

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

YSTRØM EIENDOM AS is registered as a limited company in Halden, Østfold with organisation number 925638242. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Eiendomsrelatert virksomhet”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −6,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −6,000
Equity
NOK 1.1m
Est. value
NOK 861,000

Financial health · 2024

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

Who owns YSTRØM EIENDOM AS?

SIMEN AMANDUS YSTRØM
YSTRØM EIENDOM AS
NOK 0 rev. · NOK −6,000 profit

YSTRØM EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about YSTRØM EIENDOM AS

Who owns YSTRØM EIENDOM AS?

SIMEN AMANDUS YSTRØM is the largest registered owner, with 100.0%.

What is the revenue of YSTRØM EIENDOM AS?

YSTRØM EIENDOM AS had revenue of NOK 0 in 2025.

Who is the general manager of YSTRØM EIENDOM AS?

Simen Amandus Ystrøm is registered as general manager of YSTRØM EIENDOM AS.

Where is YSTRØM EIENDOM AS based?

YSTRØM EIENDOM AS has its business address in Halden.

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.