BIZTRAC BETA
Rental and operating of own or leased real estate

H-CONS AS

Org. no. 988938912 Limited company (AS) Vestby Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 161,000
Operating profit NOK −196,000
Equity NOK 6.6m
Incorporated 2005
Share capital NOK 200,000

Signals

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

H-CONS AS is registered as a limited company in Vestby, Akershus with organisation number 988938912. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2005. Registered share capital is NOK 200,000, divided into 100 shares. The company's stated purpose is: “Selv, gjennom hel- eller deleide selskaper eller ved samarbeide med andre virksomheter å forestå handels-, agentur-, konsulent-, eksport-, import-, investerings- og næringsvirksomhet av enhver art, herunder investering i fast eiendom, verdipapirer og utlån, samt deltakelse i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 161,000 in revenue and NOK −196,000 in operating profit.

Key figures · 2025

Revenue
NOK 161,000
Operating profit
NOK −196,000
Equity
NOK 6.6m
Est. value
NOK 4.8m

Financial health · 2025

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

Who owns H-CONS AS?

HÅKON OLA RØNNING
H-CONS AS
NOK 161,000 rev. · NOK −196,000 profit

H-CONS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about H-CONS AS

Who owns H-CONS AS?

HÅKON OLA RØNNING is the largest registered owner, with 100.0%.

What is the revenue of H-CONS AS?

H-CONS AS had revenue of NOK 161,000 in 2025.

Where is H-CONS AS based?

H-CONS AS has its business address in Son.

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.