BIZTRAC BETA
Other real estate activities on a fee or contract basis

HELL BYGG AS

Org. no. 913130030 Limited company (AS) Stjørdal Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −16,000
Equity NOK −246,000
Incorporated 2014
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−246k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−16k kr).

HELL BYGG AS is registered as a limited company in Stjørdal, Trøndelag with organisation number 913130030. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Ervere, eie, utvikle og forvalte eiendom, og alt hva dermed står i forbindelse.Selskapet kan med aksjeinnskudd eller på annen måte delta i virksomhet med tilsvarende formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −16,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −16,000
Equity
NOK −246,000

Financial health · 2025

Liquidity
1.76
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-11.2%
Weak
Equity as a share of total capital

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

Who owns HELL BYGG AS?

BALSTAD EIENDOM AS
HELL BYGG AS
NOK 0 rev. · NOK −16,000 profit

HELL BYGG AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about HELL BYGG AS

Who owns HELL BYGG AS?

BALSTAD EIENDOM AS is the largest registered owner, with 66.7%.

What is the revenue of HELL BYGG AS?

HELL BYGG AS had revenue of NOK 0 in 2025.

Where is HELL BYGG AS based?

HELL BYGG 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.