BIZTRAC BETA
Rental and operating of own or leased real estate

HEITUR EIENDOM AS

Org. no. 912041875 Limited company (AS) Levanger Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 238,000
Operating profit NOK 224,000
Equity NOK −130,000
Incorporated 2013
Share capital NOK 100,000

Signals

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

HEITUR EIENDOM AS is registered as a limited company in Levanger, Trøndelag with organisation number 912041875. 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 100,000, divided into 100 shares. The company's stated purpose is: “Eiendomsforvaltning, herunder å delta i andre selskap med lignende virksomhet, samt kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 238,000 in revenue and NOK 224,000 in operating profit.

Key figures · 2025

Revenue
NOK 238,000
Operating profit
NOK 224,000
Equity
NOK −130,000
Est. value
NOK 1.3m

Financial health · 2025

Liquidity
5.55
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-8.4%
Weak
Equity as a share of total capital

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

Who owns HEITUR EIENDOM AS?

TROND OVE TANGEN
HEITUR EIENDOM AS
NOK 238,000 rev. · NOK 224,000 profit

HEITUR EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about HEITUR EIENDOM AS

Who owns HEITUR EIENDOM AS?

TROND OVE TANGEN is the largest registered owner, with 50.0%.

What is the revenue of HEITUR EIENDOM AS?

HEITUR EIENDOM AS had revenue of NOK 238,000 in 2025.

Where is HEITUR EIENDOM AS based?

HEITUR EIENDOM AS has its business address in Åsen.

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.