BIZTRAC BETA
Industrial product and fashion design activities

KARI SCHIBEVAAG AS

Org. no. 999216331 Limited company (AS) Stavanger Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 910,000
Operating profit NOK 16,000
Equity NOK 224,000
Incorporated 2012
Share capital NOK 30,000

KARI SCHIBEVAAG AS is registered as a limited company in Stavanger, Rogaland with organisation number 999216331. The business is classified under industrial product and fashion design activities (NACE 74.110). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Salg av varer og tjenester, herunder å delta i andre selskaper med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2024 financial year, show NOK 910,000 in revenue and NOK 16,000 in operating profit.

Key figures · 2024

Revenue
NOK 910,000
Operating profit
NOK 16,000
Equity
NOK 224,000
Est. value
NOK 159,000

Financial health · 2024

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

Who owns KARI SCHIBEVAAG AS?

KARI SCHIBEVAAG
KARI SCHIBEVAAG AS
NOK 910,000 rev. · NOK 16,000 profit

KARI SCHIBEVAAG AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KARI SCHIBEVAAG AS own?

KARI SCHIBEVAAG AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about KARI SCHIBEVAAG AS

Who owns KARI SCHIBEVAAG AS?

KARI SCHIBEVAAG is the largest registered owner, with 100.0%.

What is the revenue of KARI SCHIBEVAAG AS?

KARI SCHIBEVAAG AS had revenue of NOK 910,000 in 2024.

Where is KARI SCHIBEVAAG AS based?

KARI SCHIBEVAAG AS has its business address in Hafrsfjord.

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.