BIZTRAC BETA
Rental and operating of own or leased real estate

HALO PROPERTY AS

Org. no. 916945663 Limited company (AS) Fredrikstad Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 675,000
Operating profit NOK 78,000
Equity NOK 1.8m
Incorporated 2016
Share capital NOK 75,000

HALO PROPERTY AS is registered as a limited company in Fredrikstad, Østfold with organisation number 916945663. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2016. Registered share capital is NOK 75,000, divided into 750 shares. The company's stated purpose is: “Investering i andre selskaper, samt alt som naturlig har tilknytning til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 675,000 in revenue and NOK 78,000 in operating profit.

Key figures · 2024

Revenue
NOK 675,000
Operating profit
NOK 78,000
Equity
NOK 1.8m
Est. value
NOK 1.3m

Financial health · 2024

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

Who owns HALO PROPERTY AS?

WIC HOLDING AS
HALO PROPERTY AS
NOK 675,000 rev. · NOK 78,000 profit

HALO PROPERTY AS has 4 registered shareholders:

All shareholders and roles →

Which companies does HALO PROPERTY AS own?

HALO PROPERTY AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about HALO PROPERTY AS

Who owns HALO PROPERTY AS?

WIC HOLDING AS is the largest registered owner, with 25.1%.

What is the revenue of HALO PROPERTY AS?

HALO PROPERTY AS had revenue of NOK 675,000 in 2024.

Who is the general manager of HALO PROPERTY AS?

Christian Winther is registered as general manager of HALO PROPERTY AS.

Where is HALO PROPERTY AS based?

HALO PROPERTY AS has its business address in Rolvsøy.

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.