biztrac. BETA
COMPANY REGISTER PROFILE
916229135 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Organisation of conventions and trade shows

HJELSENG GÅRD AS

Org. no. 916229135 Limited company (AS) Stjørdal Incorporated 2015 Active
Revenue 2025 NOK 121,000
Operating profit NOK −252,000
Equity NOK −345,000
Incorporated 2015
Share capital NOK 1.3m

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−345k kr).

HJELSENG GÅRD AS is registered as a limited company in Stjørdal, Trøndelag with organisation number 916229135. The business is classified under organisation of conventions and trade shows (NACE 82.300). The company was incorporated in 2015. Registered share capital is NOK 1.3m, divided into 1280 shares. The company's stated purpose is: “Arrangement av kurs, konferanser, selskap og andre tilstellinger som faller naturlig sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 121,000 in revenue and NOK −252,000 in operating profit.

Key figures · 2025

Revenue
NOK 121,000
▼ −95 %
Operating profit
NOK −252,000
▼ −249 %
Equity
NOK −345,000
▼ −275 %

Financial health · 2025

Liquidity
-0.05
Not satisfactory
Current assets ÷ current liabilities
Profitability
-156.4%
Not satisfactory
Return on total assets
Solidity
2664.6%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns HJELSENG GÅRD AS?

HJELSENG GÅRD AS
NOK 121,000 rev. · NOK −252,000 profit

HJELSENG GÅRD AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HJELSENG GÅRD AS

Who owns HJELSENG GÅRD AS?

Ola Hjelseng is the largest registered owner, with 100.0%.

What is the revenue of HJELSENG GÅRD AS?

HJELSENG GÅRD AS had revenue of NOK 121,000 in 2025.

Where is HJELSENG GÅRD AS based?

HJELSENG GÅRD 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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.