BIZTRAC BETA
Rental and operating of own or leased real estate

DHG EIENDOM AS

Org. no. 923871705 Limited company (AS) Nordre Follo Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 342,000
Operating profit NOK 252,000
Equity NOK 481,000
Incorporated 2019
Share capital NOK 33,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

DHG EIENDOM AS is registered as a limited company in Nordre Follo, Akershus with organisation number 923871705. 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 33,000, divided into 1000 shares. The company's stated purpose is: “Selskapets virksomhet er investering i og utleie av eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 342,000 in revenue and NOK 252,000 in operating profit.

Key figures · 2025

Revenue
NOK 342,000
Operating profit
NOK 252,000
Equity
NOK 481,000
Est. value
NOK 828,000

Financial health · 2025

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

Who owns DHG EIENDOM AS?

DHG HOLDING AS
DHG EIENDOM AS
NOK 342,000 rev. · NOK 252,000 profit

DHG EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about DHG EIENDOM AS

Who owns DHG EIENDOM AS?

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

What is the revenue of DHG EIENDOM AS?

DHG EIENDOM AS had revenue of NOK 342,000 in 2025.

Who is the general manager of DHG EIENDOM AS?

Dag Henrik Granly is registered as general manager of DHG EIENDOM AS.

Where is DHG EIENDOM AS based?

DHG EIENDOM AS has its business address in Sofiemyr.

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.