BIZTRAC BETA
Event catering activities

SILLONGEN HOLDING AS

Org. no. 889059362 Limited company (AS) Vestre Toten Incorporated 2005 Active
Ownership graph ↗
Operating profit NOK −17,000
Equity NOK 3.8m
Incorporated 2005
Share capital NOK 3.3m

Signals

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

SILLONGEN HOLDING AS is registered as a limited company in Vestre Toten, Innlandet with organisation number 889059362. The business is classified under event catering activities (NACE 56.210). The company was incorporated in 2005. Registered share capital is NOK 3.3m, divided into 1900 shares. The company's stated purpose is: “Investeringsvirksomhet samt alt som står i forbindelse med dette, herunder å delta i andre selskaper med lignende virksomhet.”.

Key figures · 2024

Operating profit
NOK −17,000
Equity
NOK 3.8m
Est. value
NOK 5.0m

Financial health · 2024

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

Who owns SILLONGEN HOLDING AS?

ARVE SØRBO
SILLONGEN HOLDING AS
· NOK −17,000 profit

SILLONGEN HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does SILLONGEN HOLDING AS own?

SILLONGEN HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SILLONGEN HOLDING AS

Who owns SILLONGEN HOLDING AS?

ARVE SØRBO is the largest registered owner, with 66.6%.

Who is the general manager of SILLONGEN HOLDING AS?

Arve Sørbo is registered as general manager of SILLONGEN HOLDING AS.

Where is SILLONGEN HOLDING AS based?

SILLONGEN HOLDING AS has its business address in Bøverbru.

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.