BIZTRAC BETA
Rental and operating of own or leased real estate

DYRHOFF EIENDOM AS

Org. no. 968466747 Limited company (AS) Elverum Incorporated 1994 Active
Ownership graph ↗
Revenue 2024 NOK 2.4m
Operating profit NOK −630,000
Equity NOK 780,000
Incorporated 1994
Share capital NOK 105,000

Signals

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

DYRHOFF EIENDOM AS is registered as a limited company in Elverum, Innlandet with organisation number 968466747. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1994. Registered share capital is NOK 105,000, divided into 7000 shares. The company's stated purpose is: “Investering, eie fast eiendom, utleie og annen virksomhet som naturlig hører inn under det samme.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.4m in revenue and NOK −630,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.4m
Operating profit
NOK −630,000
Equity
NOK 780,000
Est. value
NOK 4.2m

Financial health · 2024

Liquidity
0.41
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
19.0%
Good
Equity as a share of total capital

Who owns DYRHOFF EIENDOM AS?

DYRHOFF AS
DYRHOFF EIENDOM AS
NOK 2.4m rev. · NOK −630,000 profit

DYRHOFF EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about DYRHOFF EIENDOM AS

Who owns DYRHOFF EIENDOM AS?

DYRHOFF AS is the largest registered owner, with 100.0%.

What is the revenue of DYRHOFF EIENDOM AS?

DYRHOFF EIENDOM AS had revenue of NOK 2.4m in 2024.

Who is the general manager of DYRHOFF EIENDOM AS?

Gunnar Ståle Dyrhoff is registered as general manager of DYRHOFF EIENDOM AS.

Where is DYRHOFF EIENDOM AS based?

DYRHOFF EIENDOM AS has its business address in Elverum.

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.