BIZTRAC BETA
Site preparation

HEFFALOMPEN HOLDING AS

Org. no. 990384886 Limited company (AS) Asker Incorporated 2006 Active
Ownership graph ↗
Operating profit NOK −163,000
Equity NOK 273,000
Incorporated 2006
Share capital NOK 100,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−163k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

HEFFALOMPEN HOLDING AS is registered as a limited company in Asker, Akershus with organisation number 990384886. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2006. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Investering og deltagelse i andre virksomheter samt andre forhold som faller naturlig under dette. ”.

Key figures · 2024

Operating profit
NOK −163,000
Equity
NOK 273,000
Est. value
NOK 280,000

Financial health · 2024

Liquidity
0.00
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
9.3%
Weak
Equity as a share of total capital

Who owns HEFFALOMPEN HOLDING AS?

LASSE IVAR JØRGENSEN
HEFFALOMPEN HOLDING AS
· NOK −163,000 profit

HEFFALOMPEN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does HEFFALOMPEN HOLDING AS own?

HEFFALOMPEN HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about HEFFALOMPEN HOLDING AS

Who owns HEFFALOMPEN HOLDING AS?

LASSE IVAR JØRGENSEN is the largest registered owner, with 100.0%.

Who is the general manager of HEFFALOMPEN HOLDING AS?

Lasse Ivar Jørgensen is registered as general manager of HEFFALOMPEN HOLDING AS.

Where is HEFFALOMPEN HOLDING AS based?

HEFFALOMPEN HOLDING AS has its business address in Klokkarstua.

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.