biztrac. BETA
COMPANY REGISTER PROFILE
971307374 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Activities of religious organisations

VISJON BIBEL CENTER STI

Org. no. 971307374 Foundation (STI) Øvre Eiker Incorporated 1995 Active
Ownership graph ↗
Revenue 2025 NOK 5.5m
Operating profit NOK −106,000
Equity NOK 7.7m
Incorporated 1995
Share capital NOK 100,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−106k kr).
  • Nylig endring 2026-05-06 Adresseendring registrert 2026-05-06.

VISJON BIBEL CENTER STI is registered as a foundation in Øvre Eiker, Buskerud with organisation number 971307374. The business is classified under activities of religious organisations (NACE 94.910). The company was incorporated in 1995. Registered share capital is NOK 100,000. The most recent filed accounts, for the 2025 financial year, show NOK 5.5m in revenue and NOK −106,000 in operating profit.

Former names: VISION BIBEL CENTER

Key figures · 2025

Revenue
NOK 5.5m
▼ −19 %
Operating profit
NOK −106,000
▼ −150 %
Equity
NOK 7.7m
▼ −1 %
Est. value
NOK 7.6m

Financial health · 2025

Liquidity
1.59
Good
Current assets ÷ current liabilities
Profitability
-0.7%
Not satisfactory
Return on total assets
Solidity
83.2%
Very good
Equity as a share of total capital

Who owns VISJON BIBEL CENTER STI?

No shareholders are registered for VISJON BIBEL CENTER STI in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about VISJON BIBEL CENTER STI

What is the revenue of VISJON BIBEL CENTER STI?

VISJON BIBEL CENTER STI had revenue of NOK 5.5m in 2025.

Who is the general manager of VISJON BIBEL CENTER STI?

Leif Inge Sandnes is registered as general manager of VISJON BIBEL CENTER STI.

Where is VISJON BIBEL CENTER STI based?

VISJON BIBEL CENTER STI has its business address in Hokksund.

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.