BIZTRAC BETA
Rental and operating of own or leased real estate

HALDORGÅRDEN AS

Org. no. 820759362 Limited company (AS) Orkland Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 1.7m
Operating profit NOK 315,000
Equity NOK 3.3m
Incorporated 2018
Share capital NOK 1.0m

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

HALDORGÅRDEN AS is registered as a limited company in Orkland, Trøndelag with organisation number 820759362. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2018. Registered share capital is NOK 1.0m, divided into 1000 shares. The company's stated purpose is: “Utvikling av bolig- og næringseiendom, samt annen virksomhet i denne forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.7m in revenue and NOK 315,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.7m
Operating profit
NOK 315,000
Equity
NOK 3.3m
Est. value
NOK 2.9m

Financial health · 2024

Liquidity
0.01
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
22.8%
Good
Equity as a share of total capital

Who owns HALDORGÅRDEN AS?

SALVESEN & THAMS EIENDOM AS
HALDORGÅRDEN AS
NOK 1.7m rev. · NOK 315,000 profit

HALDORGÅRDEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HALDORGÅRDEN AS

Who owns HALDORGÅRDEN AS?

SALVESEN & THAMS EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of HALDORGÅRDEN AS?

HALDORGÅRDEN AS had revenue of NOK 1.7m in 2024.

Who is the general manager of HALDORGÅRDEN AS?

Yngve Bakken is registered as general manager of HALDORGÅRDEN AS.

Where is HALDORGÅRDEN AS based?

HALDORGÅRDEN AS has its business address in Orkanger.

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.