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

O.A. GJELDTS STIFTELSE

Org. no. 877114082 Foundation (STI) Ringsaker Incorporated 1889 Active
Revenue 2025 NOK 110,000
Operating profit NOK −658,000
Equity NOK 23.0m
Incorporated 1889
Share capital NOK 500,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−658k kr).

O.A. GJELDTS STIFTELSE is registered as a foundation in Ringsaker, Innlandet with organisation number 877114082. The business is classified under activities of charities which distribute means themselves (NACE 94.991). The company was incorporated in 1889. Registered share capital is NOK 500,000. The most recent filed accounts, for the 2025 financial year, show NOK 110,000 in revenue and NOK −658,000 in operating profit.

Former names: O A GJELDTS LEGATFOND, O.A. GJELDTS LEGAT, O.A. GJELDTS LEGAT STI

Key figures · 2025

Revenue
NOK 110,000
▼ −99 %
Operating profit
NOK −658,000
▼ −104 %
Equity
NOK 23.0m
▲ +13 %
Est. value
NOK 28.9m

Financial health · 2025

Liquidity
37.90
Very good
Current assets ÷ current liabilities
Profitability
11.0%
Good
Return on total assets
Solidity
90.3%
Very good
Equity as a share of total capital

Who owns O.A. GJELDTS STIFTELSE?

No shareholders are registered for O.A. GJELDTS STIFTELSE in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Which companies does O.A. GJELDTS STIFTELSE own?

O.A. GJELDTS STIFTELSE holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about O.A. GJELDTS STIFTELSE

What is the revenue of O.A. GJELDTS STIFTELSE?

O.A. GJELDTS STIFTELSE had revenue of NOK 110,000 in 2025.

Where is O.A. GJELDTS STIFTELSE based?

O.A. GJELDTS STIFTELSE has its business address in Brumunddal.

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.