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

LUBAVITCH FOND NORGE STI

Org. no. 911727595 Foundation (STI) Øvre Eiker Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 10.4m
Operating profit NOK −1.9m
Equity NOK 2.9m
Incorporated 2012
Share capital NOK 100,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1,9 mill kr).
  • Nylig endring 2026-06-02 Adresseendring registrert 2026-06-02.

LUBAVITCH FOND NORGE STI is registered as a foundation in Øvre Eiker, Buskerud with organisation number 911727595. 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 2024 financial year, show NOK 10.4m in revenue and NOK −1.9m in operating profit.

Key figures · 2024

Revenue
NOK 10.4m
▲ +58 %
Operating profit
NOK −1.9m
▲ +41 %
Equity
NOK 2.9m
▼ −52 %
Est. value
NOK 3.8m

Financial health · 2024

Liquidity
0.14
Not satisfactory
Current assets ÷ current liabilities
Profitability
-6.2%
Not satisfactory
Return on total assets
Solidity
9.4%
Weak
Equity as a share of total capital

Who owns LUBAVITCH FOND NORGE STI?

No shareholders are registered for LUBAVITCH FOND NORGE STI in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about LUBAVITCH FOND NORGE STI

What is the revenue of LUBAVITCH FOND NORGE STI?

LUBAVITCH FOND NORGE STI had revenue of NOK 10.4m in 2024.

Who is the general manager of LUBAVITCH FOND NORGE STI?

Shaul Wilhelm is registered as general manager of LUBAVITCH FOND NORGE STI.

Where is LUBAVITCH FOND NORGE STI based?

LUBAVITCH FOND NORGE STI has its business address in Vestfossen.

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.