BIZTRAC BETA
Activities of agents involved in non-specialised wholesale

HEIJON AS

Org. no. 827020222 Limited company (AS) Øvre Eiker Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −16,000
Equity NOK −15,000
Incorporated 2021
Share capital NOK 30,000

Signals

3 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−15k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−16k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

HEIJON AS is registered as a limited company in Øvre Eiker, Buskerud with organisation number 827020222. The business is classified under activities of agents involved in non-specialised wholesale (NACE 46.190). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Investeringer i fast eiendom. Eiendomsutvikling og deltakelse i andre selskaper.”. 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 −15,000

Financial health · 2025

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

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

Who owns HEIJON AS?

HALGRIM AS
HEIJON AS
NOK 0 rev. · NOK −16,000 profit

HEIJON AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HEIJON AS

Who owns HEIJON AS?

HALGRIM AS is the largest registered owner, with 100.0%.

What is the revenue of HEIJON AS?

HEIJON AS had revenue of NOK 0 in 2025.

Where is HEIJON AS based?

HEIJON AS has its business address in Fiskum.

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.