BIZTRAC BETA
Buying and selling of own real estate

ARW EIENDOM AS

Org. no. 935908582 Limited company (AS) Trondheim Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −9,000
Equity NOK 15,000
Incorporated 2025
Share capital NOK 30,000

Signals

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

ARW EIENDOM AS is registered as a limited company in Trondheim, Trøndelag with organisation number 935908582. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Drive kjøp og salg av egen fast eiendom, inkludert investering, utvikling, forvaltning og salg av bolig- og næringseiendommer.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −9,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −9,000
Equity
NOK 15,000
Est. value
NOK 13,000

Financial health · 2025

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

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

Who owns ARW EIENDOM AS?

ARW HOLDING AS
ARW EIENDOM AS
NOK 0 rev. · NOK −9,000 profit

ARW EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ARW EIENDOM AS own?

ARW EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ARW EIENDOM AS

Who owns ARW EIENDOM AS?

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

What is the revenue of ARW EIENDOM AS?

ARW EIENDOM AS had revenue of NOK 0 in 2025.

Where is ARW EIENDOM AS based?

ARW EIENDOM AS has its business address in Trondheim.

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.