BIZTRAC BETA
Wholesale of other food

YIPS HOLDING AS

Org. no. 924498838 Limited company (AS) Sandnes Incorporated 2020 Active
Ownership graph ↗
Operating profit NOK −67,000
Equity NOK 685,000
Incorporated 2020
Share capital NOK 100,000

Signals

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

YIPS HOLDING AS is registered as a limited company in Sandnes, Rogaland with organisation number 924498838. The business is classified under wholesale of other food (NACE 46.380). The company was incorporated in 2020. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Foreta/Forvalte investeringer i verdipapirer, handels- & industrivirksomhet, tjenesteytende virksomhet, fast eiendom samt hva hermed står i forbindelse, herunder å delta i selskaper med lignende eller annen virksomhet, enten direkte eller via datterselskap, gjennom eierskap, lån, garantistillelser eller annen måte.”.

Key figures · 2024

Operating profit
NOK −67,000
Equity
NOK 685,000
Est. value
NOK 679,000

Financial health · 2024

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

Who owns YIPS HOLDING AS?

PIZZABAKEREN HOLDING AS
YIPS HOLDING AS
· NOK −67,000 profit

YIPS HOLDING AS has 4 registered shareholders:

All shareholders and roles →

Which companies does YIPS HOLDING AS own?

YIPS HOLDING AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about YIPS HOLDING AS

Who owns YIPS HOLDING AS?

PIZZABAKEREN HOLDING AS is the largest registered owner, with 50.4%.

Where is YIPS HOLDING AS based?

YIPS HOLDING AS has its business address in Sandnes.

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.