biztrac. BETA
COMPANY REGISTER PROFILE
999262015 ORG. NO. 2021 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Activities of charities which distribute means themselves

STIFTELSEN DYRENES HUS STAVANGER

Org. no. 999262015 Foundation (STI) Stavanger Incorporated 2012 Active
Revenue 2021 NOK 224,000
Operating profit NOK 212,000
Equity NOK 118,000
Incorporated 2012
Share capital NOK 100,000

STIFTELSEN DYRENES HUS STAVANGER is registered as a foundation in Stavanger, Rogaland with organisation number 999262015. The business is classified under activities of charities which distribute means themselves (NACE 94.991). The company was incorporated in 2012. Registered share capital is NOK 100,000. The most recent filed accounts, for the 2021 financial year, show NOK 224,000 in revenue and NOK 212,000 in operating profit.

Former names: DYREVERNSTIFTELSEN KARI MILLS

Key figures · 2021

Revenue
NOK 224,000
▲ +180 %
Operating profit
NOK 212,000
▲ +216 %
Equity
NOK 118,000
▲ +469 %
Est. value
NOK 546,000

Financial health · 2021

Liquidity
67.61
Very good
Current assets ÷ current liabilities
Profitability
4.6%
Weak
Return on total assets
Solidity
2.5%
Not satisfactory
Equity as a share of total capital

Who owns STIFTELSEN DYRENES HUS STAVANGER?

No shareholders are registered for STIFTELSEN DYRENES HUS STAVANGER in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about STIFTELSEN DYRENES HUS STAVANGER

What is the revenue of STIFTELSEN DYRENES HUS STAVANGER?

STIFTELSEN DYRENES HUS STAVANGER had revenue of NOK 224,000 in 2021.

Who is the general manager of STIFTELSEN DYRENES HUS STAVANGER?

Synnøve Elise Thorvaldsen is registered as general manager of STIFTELSEN DYRENES HUS STAVANGER.

Where is STIFTELSEN DYRENES HUS STAVANGER based?

STIFTELSEN DYRENES HUS STAVANGER has its business address in Stavanger.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.