BIZTRAC BETA
Web search portal activities

GIVY AS

Org. no. 819745862 Limited company (AS) Stavanger Incorporated 2017 Active
Ownership graph ↗
Operating profit NOK −192,000
Equity NOK −843,000
Incorporated 2017
Share capital NOK 35,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−843k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−192k kr).

GIVY AS is registered as a limited company in Stavanger, Rogaland with organisation number 819745862. The business is classified under web search portal activities (NACE 63.910). The company was incorporated in 2017. Registered share capital is NOK 35,000, divided into 1175000 shares. The company's stated purpose is: “Å styrke finansieringen av bærekraftsmålene ved å stimulere til økt privat giverglede og dermed redusere forskjellene mellom fattig og rik, globalt. Selskapet kan motta gaver, donasjoner og tilskudd fra private og juridiske enheter for å videreformidle disse til tiltak som støtter bærekraftsmålene.”.

Key figures · 2024

Operating profit
NOK −192,000
Equity
NOK −843,000

Financial health · 2024

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

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

Who owns GIVY AS?

KJERSTI ØRITSLAND
GIVY AS
· NOK −192,000 profit

GIVY AS has 20+ registered shareholders:

All shareholders and roles →

Which companies does GIVY AS own?

GIVY AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about GIVY AS

Who owns GIVY AS?

KJERSTI ØRITSLAND is the largest registered owner, with 37.0%.

Who is the general manager of GIVY AS?

Knut Øritsland is registered as general manager of GIVY AS.

Where is GIVY AS based?

GIVY AS has its business address in Stavanger.

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.