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

PER P OG LOUISE SÆTRES LEGAT TIL BESTE FOR TRYSILUNGDOM UNDER UTDANNING STI

Org. no. 977116430 Foundation (STI) Incorporated 1990 Active
Revenue 2025 NOK 0
Operating profit NOK −23,000
Equity NOK 1.2m
Incorporated 1990
Share capital NOK 1.1m

Signals

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

PER P OG LOUISE SÆTRES LEGAT TIL BESTE FOR TRYSILUNGDOM UNDER UTDANNING STI is registered as a foundation with organisation number 977116430. The business is classified under activities of charities which distribute means themselves (NACE 94.991). The company was incorporated in 1990. Registered share capital is NOK 1.1m. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −23,000 in operating profit.

Former names: PER P OG LOUISE SÆTRES LEGAT

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −23,000
▼ −57 %
Equity
NOK 1.2m
▲ +3 %
Est. value
NOK 828,000

Financial health · 2025

Liquidity
901.98
Very good
Current assets ÷ current liabilities
Profitability
2.5%
Weak
Return on total assets
Solidity
99.9%
Very good
Equity as a share of total capital

Who owns PER P OG LOUISE SÆTRES LEGAT TIL BESTE FOR TRYSILUNGDOM UNDER UTDANNING STI?

No shareholders are registered for PER P OG LOUISE SÆTRES LEGAT TIL BESTE FOR TRYSILUNGDOM UNDER UTDANNING STI in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about PER P OG LOUISE SÆTRES LEGAT TIL BESTE FOR TRYSILUNGDOM UNDER UTDANNING STI

What is the revenue of PER P OG LOUISE SÆTRES LEGAT TIL BESTE FOR TRYSILUNGDOM UNDER UTDANNING STI?

PER P OG LOUISE SÆTRES LEGAT TIL BESTE FOR TRYSILUNGDOM UNDER UTDANNING STI had revenue of NOK 0 in 2025.

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.