BIZTRAC BETA
Site preparation

SIGURD FURULUND HOLDING AS

Org. no. 888975012 Limited company (AS) Ullensaker Incorporated 2005 Active
Ownership graph ↗
Operating profit NOK −132,000
Equity NOK 167.1m
Incorporated 2005
Share capital NOK 2.6m

Signals

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

SIGURD FURULUND HOLDING AS is registered as a limited company in Ullensaker, Akershus with organisation number 888975012. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2005. Registered share capital is NOK 2.6m, divided into 130 shares. The company's stated purpose is: “Investeringsvirksomhet av enhver art, herunder deltagelse i andre virksomheter. ”.

Key figures · 2024

Operating profit
NOK −132,000
Equity
NOK 167.1m
Est. value
NOK 865.7m

Financial health · 2024

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

Who owns SIGURD FURULUND HOLDING AS?

SIGURD FURULUND
SIGURD FURULUND HOLDING AS
· NOK −132,000 profit

SIGURD FURULUND HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SIGURD FURULUND HOLDING AS own?

SIGURD FURULUND HOLDING AS holds stakes in 15 companies:

See the full ownership structure →

Frequently asked questions about SIGURD FURULUND HOLDING AS

Who owns SIGURD FURULUND HOLDING AS?

SIGURD FURULUND is the largest registered owner, with 100.0%.

Who is the general manager of SIGURD FURULUND HOLDING AS?

Sigurd Furulund is registered as general manager of SIGURD FURULUND HOLDING AS.

Where is SIGURD FURULUND HOLDING AS based?

SIGURD FURULUND HOLDING AS has its business address in Jessheim.

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.