BIZTRAC BETA
Rental and operating of own or leased real estate

HERØY EIENDOM AS

Org. no. 994813102 Limited company (AS) Trondheim Incorporated 2009 Active
Ownership graph ↗
Revenue 2025 NOK 1.2m
Operating profit NOK −398,000
Equity NOK 2.6m
Incorporated 2009
Share capital NOK 1.0m

Signals

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

HERØY EIENDOM AS is registered as a limited company in Trondheim, Trøndelag with organisation number 994813102. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2009. Registered share capital is NOK 1.0m, divided into 1000 shares. The company's stated purpose is: “Eie og drive uteleie av gnr. 5 bnr. 577 i Herøy Kommune (Kommune nr 1818) og annen virksomhet som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.2m in revenue and NOK −398,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.2m
Operating profit
NOK −398,000
Equity
NOK 2.6m
Est. value
NOK 2.4m

Financial health · 2025

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

Who owns HERØY EIENDOM AS?

J.B.J. HOLDING AS
HERØY EIENDOM AS
NOK 1.2m rev. · NOK −398,000 profit

HERØY EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HERØY EIENDOM AS

Who owns HERØY EIENDOM AS?

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

What is the revenue of HERØY EIENDOM AS?

HERØY EIENDOM AS had revenue of NOK 1.2m in 2025.

Who is the general manager of HERØY EIENDOM AS?

Jon Botn-Jørgensen is registered as general manager of HERØY EIENDOM AS.

Where is HERØY EIENDOM AS based?

HERØY EIENDOM AS has its business address in Trondheim.

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.