BIZTRAC BETA
Rental and operating of own or leased real estate

HECHLA ÅRENGA AS

Org. no. 812049712 Limited company (AS) Bærum Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 3.4m
Operating profit NOK 1.8m
Equity NOK 3.0m
Incorporated 2013
Share capital NOK 500,000

Signals

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

HECHLA ÅRENGA AS is registered as a limited company in Bærum, Akershus with organisation number 812049712. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2013. Registered share capital is NOK 500,000, divided into 100 shares. The company's stated purpose is: “Investering i fast eiendom og drive utleie av fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.4m in revenue and NOK 1.8m in operating profit.

Key figures · 2024

Revenue
NOK 3.4m
Operating profit
NOK 1.8m
Equity
NOK 3.0m
Est. value
NOK 3.8m

Financial health · 2024

Liquidity
0.25
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
10.5%
Satisfactory
Equity as a share of total capital

Who owns HECHLA ÅRENGA AS?

HECHLA HOLDING AS
HECHLA ÅRENGA AS
NOK 3.4m rev. · NOK 1.8m profit

HECHLA ÅRENGA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HECHLA ÅRENGA AS

Who owns HECHLA ÅRENGA AS?

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

What is the revenue of HECHLA ÅRENGA AS?

HECHLA ÅRENGA AS had revenue of NOK 3.4m in 2024.

Who is the general manager of HECHLA ÅRENGA AS?

Lars Horn Johannessen is registered as general manager of HECHLA ÅRENGA AS.

Where is HECHLA ÅRENGA AS based?

HECHLA ÅRENGA AS has its business address in Vøyenenga.

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.