BIZTRAC BETA
Development of building projects

HCM EIENDOM AS

Org. no. 921694334 Limited company (AS) Kongsvinger Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 685,000
Operating profit NOK 49,000
Equity NOK 418,000
Incorporated 2018
Share capital NOK 100,000

HCM EIENDOM AS is registered as a limited company in Kongsvinger, Innlandet with organisation number 921694334. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2018. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Utvikling, bygging og utleie av eiendom med tilhørende aktiviteter. Selskapet kan drive annen forretningsmessig virksomhet som naturlig hører under dette, selskapet kan eie aksjer og andeler i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 685,000 in revenue and NOK 49,000 in operating profit.

Key figures · 2025

Revenue
NOK 685,000
Operating profit
NOK 49,000
Equity
NOK 418,000
Est. value
NOK 403,000

Financial health · 2025

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

Who owns HCM EIENDOM AS?

KA MASKIN OG JERNBANESERVICE AS
HCM EIENDOM AS
NOK 685,000 rev. · NOK 49,000 profit

HCM EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HCM EIENDOM AS

Who owns HCM EIENDOM AS?

KA MASKIN OG JERNBANESERVICE AS is the largest registered owner, with 100.0%.

What is the revenue of HCM EIENDOM AS?

HCM EIENDOM AS had revenue of NOK 685,000 in 2025.

Who is the general manager of HCM EIENDOM AS?

Kim Anders Kolsrud Nyhus is registered as general manager of HCM EIENDOM AS.

Where is HCM EIENDOM AS based?

HCM EIENDOM AS has its business address in Kongsvinger.

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.