BIZTRAC BETA
Development of building projects

HJELSENG EIENDOM AS

Org. no. 989828347 Limited company (AS) Stjørdal Incorporated 2006 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −8,000
Equity NOK 835,000
Incorporated 2006
Share capital NOK 100,000

Signals

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

HJELSENG EIENDOM AS is registered as a limited company in Stjørdal, Trøndelag with organisation number 989828347. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2006. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Utvikling, kjøp og salg av fast eiendom og hva hermed står i forbindelse, herunder å delta i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −8,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −8,000
Equity
NOK 835,000
Est. value
NOK 762,000

Financial health · 2025

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

Who owns HJELSENG EIENDOM AS?

OLA HJELSENG
HJELSENG EIENDOM AS
NOK 0 rev. · NOK −8,000 profit

HJELSENG EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about HJELSENG EIENDOM AS

Who owns HJELSENG EIENDOM AS?

OLA HJELSENG is the largest registered owner, with 50.0%.

What is the revenue of HJELSENG EIENDOM AS?

HJELSENG EIENDOM AS had revenue of NOK 0 in 2025.

Who is the general manager of HJELSENG EIENDOM AS?

Ola Hjelseng is registered as general manager of HJELSENG EIENDOM AS.

Where is HJELSENG EIENDOM AS based?

HJELSENG EIENDOM AS has its business address in Stjørdal.

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.